Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The brackets for simple items like < S > sit too low and are too big #35

Open
stefan11 opened this issue Aug 10, 2020 · 4 comments
Open
Assignees

Comments

@stefan11
Copy link

The following code produces:
grafik

\avm{[arg-st & < S > \+ \2]}

But it should produce:
grafik

@stefan11 stefan11 added the bug Something isn't working label Aug 10, 2020
@kopeckyf kopeckyf removed the bug Something isn't working label Aug 11, 2020
@kopeckyf
Copy link
Contributor

This isn't a bug, everything is as it should be given current langsci-avm. The approach to solve this issue would be to introduce special treatment for singletons, i.e. for sub-structures that contain only one item. Introducing this special treatment is something we should do, but the optimal solution for it is as of yet unclear.

@stefan11
Copy link
Author

Ah. avm.sty had \q< \q> or something similar for this. I used \sliste{ S } so far but dreamed of something that does everything automatically.

@kopeckyf
Copy link
Contributor

There are several possibilities how the automatic solution could achieve special treatment. One of them is to set \arraystretch to 0. You can do this now, if you like, using

\avm[stretch=0]{[arg-st & < S > \+ \2]}

But beware that this will produce a very tight AVM as the outer [ ... ] are affected as well. One could also apply \def\arraystretch{0} to the innermost structure only, but I think this kind of "hack" is something one should always avoid.

@stefan11
Copy link
Author

stefan11 commented Aug 15, 2020

What I would like to have is that the package determines what it sees. If there is just an NP or an S in the brackets, it should do it right. Everything else does not solve the problem of proper typesetting since author will start to fiddle with stuff. This is not what we want. Experience tells us that this actually causes more work. (on both sides)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants