-
Notifications
You must be signed in to change notification settings - Fork 44
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
hyphens in margins #845
Comments
It looks to me like that hyphen is protruding exactly as it should according to the page you linked. Also, do you have the gabc file that you used to produce the score from which that image was cut? |
The thing is the protrusion here is a bug, not a feature that was intended, and protrusion should be optional anyway (not all people like the mechanism). You can reproduce it with
although here this is a limit case that might be hard to fix... |
I think it's possible to trick this by adding some kind of space (the size of an hyphen) after the text, this space being removed if not at end of line... might not be easy but that should be the best solution |
See the example of this message for a realistic case. |
See #945 |
Hyphens should not be allowed to go far from the right limit of the staff lines. Example of undesired behavior:
In a first step, the behavior should be the same as when there is no hyphen, in a second step we would differenciate the case where the syllable ends by an hyphen (automatic or not), and allow it to come closer to the lines (a kind of character protrusion).
I'm affraid this is no easy fix, as the hyphen that poses problems is added in lua after the paragraph breaking algorithm, so even in a two-pass system, this wouldn't be easy: the first pass would tell the second to add an hyphen, and in some cases, the second would pass the syllable on the line after (because it would have become too big to stay on the line it was on), and thus we would have an instable system... Maybe the best way to deal with this is with a discretionary?
The text was updated successfully, but these errors were encountered: