# Tag Info

## New answers tagged linguistics

1

The vowel package does produce very pixelated diagrams, and as far as I know there's no way to use the package and avoid this. To illustrate this, I zoomed in on the diagram on p. 1 of the documentation: Instead of using vowel, I recommend using tikz, a powerful graphics package with extensive documentation and a supportive community of users on this site. ...

1

I was able to get the proper behavior by editing \ex@c and \glw@begingl@a. In both cases I was able to figure out some alternate code appropriate to the RTL context. My modifications to \ex@c: % \llap{\hbox to\leftskip{\unhbox\numbox \hss}}% \if@RTL \hbox to\leftskip{\unhbox\numbox \hss}% \else \llap{\hbox to\leftskip{\unhbox\numbox ...

4

Branches in the tree are just bracketed constituents in the bracketed structure. As a linguist you should be able to read bracketed structures as easily as trees, since since they are both used in the the field. Each pair of brackets is a constituent in the tree. One way to make the debugging of complex trees much easier is to format them in your source ...

4

Or you could use forest... \documentclass[12pt,tikz,border=10pt]{standalone} \usepackage{forest} \begin{document} \begin{forest} for tree={child anchor=north, parent anchor=south} [S [DP [E] [NP [PRO] [NP [$\lambda_1$] [NP [S] [S [DP [D [the]] [N [pictures]]] [VP [V [display]] [DP [D [the]] [N [man] [S]]]]]]]]] [VP [V] [DP]]] \end{forest} ...

5

.style is an unintended way to specify defaults, and therefore has its shortcomings. (The next version of the package will contain key default preamble.) It works because an empty key is called at the end of every nodes keylist ... and since it's at the end, it's impossible to override. Workaround: redefine the empty style, as shown in the code. You can ...

5

1. With gb4e, cgloss, and tabular I think the simplest way to fix the vertical spacing issue is to load the cgloss package and switch to a tabular environment instead of tabbing. The cgloss package is not available on CTAN or in standard distributions; see Alan Munn's answer to Why is the gap between the translation and the last line of the gloss so wide ...

4


2

I can't explain the behavior, but taking out \vbox and \hbox from the definition of \CurlyBrackets gives the right result. \documentclass{article} \usepackage{gb4e} \noautomath \newcommand{\CurlyBrackets}[1]{% $\left\{\begin{tabular}{@{}l@{}}#1\end{tabular}\right\}$ }% \begin{document} \begin{exe} \ex[\#]{\CurlyBrackets{A cat\\Seven dogs\\Mary} ...

6

You could use the tikzmark library. Using \subnode{<name>}{<content>} you can place some marks around designated elements and then use those marks and the node anchors to easily place the arrows: \documentclass{article} \usepackage{forest} \usetikzlibrary{tikzmark} \begin{document} \begin{forest} for tree={s sep=20pt} [A t\subnode{endc}{e}st ...

2

This question is a really nice example of why minimal examples rather than code fragments are extremely helpful both in explaining a problem to others, and in finding the source of a problem by yourself. Errors and line numbers If I turn the fragment of code you supplied into a minimal example, it compiles without error: \documentclass{article} ...

3

You should use \~ within \textipa{} thus: \textipa{\~{@}} You should use the diacritic commands within "the IPA environment" (which is the generic term for the IPA groups and environment in the TIPA manual). All of your IPA stuff really belongs in the IPA environment. This will allow consistency of font and encoding, but it's also the only way a command ...

11

Just put the \~ inside the scope of the \textipa command: \textipa{\~@}

1

Personally, I once used linguex in conjunction with pst-jtree. That gives you all the power you need. Please excuse that I shortened the example somewhat. The \jtree command has to be called once in the document before the example for some reason. Also note that the document has to be compiled as .ps first. \documentclass[12pt]{article} \usepackage{linguex} ...

1

With forest you can generally do this quite nicely using the nice empty nodes style (page 52, example 81). However, sometimes it doesn't quite work that simply. Your tree is one such example. Nonetheless, it is possible to get the tree very nearly perfect to the point that I challenge anybody to know that the tree does not use the unadulterated form of nice ...

Top 50 recent answers are included