1,458 reputation
211
bio website
location
age
visits member for 1 year, 7 months
seen Apr 15 at 18:09

Mar
27
comment Smaller roofs for forest
Couldn't one define a new primitive similar to triangle but with other properties. Or a version of triangle that one can pass a string to which can be used to determine the size? I would prefer this over editing trees and putting separation commands in as in the solution by Gonzalo Medina. We want to use these macros also for unexperienced users and having them chose distances might be problematic.
Mar
27
comment Specifying the distance between levels in forest
Thanks. The text before the example explains that it is an answer to my question, but it is not the best way to display this answer. This example is highly complex. Is the answer to shift all the nodes you want to be lowered manually? Hm.
Mar
27
comment Smaller roofs for forest
Sorry this is just an N with overline. Replaced it by the typewriter version N'.
Mar
26
comment Align leaves of a tree
This is the second answer that points me to forrest'. I guess I have to switch. The manual looks highly complex ... Do you have an easy way to center all leave items? "Frau" looks strange since "woman" is wider. tikz-qtree` does this in the same way. So this would have been my next question for tikz-qtree.
Mar
2
comment Having nodes at the baseline and in mid-air with tikz-qtree
Thanks. My installation asks me to include ` \usetikzlibrary{calc}`. But then it works.
Mar
2
comment Drawing arrows to nodes in trees
Thanks! Is there a way to get the left-most V right below the V it points to? The middle and right ones are OK. I will connect to the complete node (v-in) without shifting. The scope and shift solution seems to be problematic if the font size changes because of the absolute positioning. I would stick to the three separate tikzpictures. In fact these are three pictures logically. They are compared in this figure. Does it make sense to have separate tikzpictures?
Mar
1
comment Drawing arrows to nodes in trees
Thanks! But the Vs in the bottom line should not be connected to each other but to special Vs in the representations above them. The leftmost to the only verb that is there, the middle one to the lowest verb and the right-most V to the right V in the tree. But the \node[below ] and the xshift hint was already very helpful!
Mar
1
comment Drawing arrows to nodes in trees
Yes, correct! (did you know that comments must be at least 15 characters in length?) Some people need a lot of words to say yes.
Jan
25
comment Arrow disappearing
This is what the node was in the original example, I simplified the stuff in the tree but left it in the node labels. Linguistically this tree does not make sense ...
Jan
25
comment Arrow disappearing
Well, yes in principle your suggestion looks better, but the idea is to connect the NPs. I asked in another question about a way to do this, but this seems to be impossible with tikz-qtree.
Dec
17
comment Mysterious problem with ps2pdf in texlive 2013
Well yes. This slide was a complex slide with a lot of stuff in the figure and a lot of text below it. I will add the full slide and I hope it does make some sense =:-).
Dec
17
comment Mysterious problem with ps2pdf in texlive 2013
Sorry, I tried to make the example more minimal before submitting it and it actually did not cause a problem any longer. I added back in [shrink] and this may be the cause for the problem.
Dec
15
comment Automatic connection of text points in tikz-qtree
OK. Thanks! The line going from V to V1 should end under the V following the // and the lines going downward from S/V to V'V and from V'V to V/V should end over the Vs. Is this possible? Insisting on this seems to be snobbish, but the picture is about information being shared and it is just this V behind the // that is shared and I want this to be reflected in the picture.
Dec
15
comment Automatic connection of text points in tikz-qtree
Thanks, it does look better than what I had, but it is not exactly what I was looking for. What should be connected with arrows are the Vs behind the //. In the leftmost branch you connected the S in the mother node with the V in the daughter. The V in S//V is connected to the S to the right, rather than to the V, following the S. To fix this, I would have to shift the node by hand, right? And this would involve manual labor and be font dependent, wouldn't it?
Dec
13
comment bidi and hyperref change hyphenation
Thanks a lot! ()
Dec
11
comment No room for a new \dimen despite of loading etex
OK. Thanks. This worked. I read this, but thought it does not apply, since I did not load the packages that were mentioned.
Dec
6
comment Is there a way to suppress the black boxes in the margin only?
Thanks! Did not realize that one can put arbitrary stuff into \indexproofstyle.
Dec
6
comment Is there a way to suppress the black boxes in the margin only?
Yes, I know. But there is no problem in terms of overfull boxes that I have to be alerted of as far as the margin notes are concerned, since they will be gone in the finalversion as well. I want to be in draft mode and see the black boxes for normal text, but not in the margins. Actually the boxes are not in the margins but cover the main text. This is the reason why I want to get rid of them.
Nov
15
comment Minimal bidi for typesetting RL text
@VafaKhalighi:Thanks! This is what we try to do: github.com/langsci/latex We had a main class file (langsci.cls) and loaded the Komascript classes. In langsci.cls we redefined the title page and I was suprised to see that this did not work. I found out that this was due to loading bidi. We now found a way around the problem by delaying the redefinition of the title page. I asked for help here since these classes shall work for thousands of linguists. If it were just me there would not be a problem, since it works now. But I am afraid of side effects in other areas of the LaTeX world.
Nov
14
comment Minimal bidi for typesetting RL text
@VafaKhalighi: Thanks for this hint. I did not know about the issue tracker but will use it in the future. I sent you an email in another issue to the address that was given in the manual. But this address seems to be dead. Anyway, one side effect is that you change the typesetting of the title which basically kills all modifications that have been done before. For the normal bidi user this is not a bug but for our purposes it is not nice. So this is not an issue for the issue tracker, I guess. I apologize for the claim about hyperref and bidi interaction in the other post.