You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Perhaps related to #1029, but perhaps not. At the very least this needs to play well with that issue.
A tag might needed which allows at least discritionary-like behavior in gabc. In this fashion one could specify different behavior for when a syllable occurs at the end of the line versus in the middle of it.
The original context of this request was placing verse numbers, barred letters, or other informational text below bar lines. In some instances this text corresponds to the next verse and should not end a line, but the bar line above it can (and really should, since we don't want to start a line with a bar line). For examples, 2.(::) should effectively be (::z) 2.() when it occurs at the end of the line (represented by the z), but is just fine as it is when it occurs in the middle of the line.
This cannot be automatic for all bar lines because there are times when the text below the bar line shouldn't advance to the next line automatically. For instance, in bis.(::) the bis. refers to what just came before it (not what follows) and thus should stay with its bar line at the end of the line.
It also occurs to me that in some instances the word hyphenation could benefit from this. For instance in German syllable ending in ß is hyphenated as s-s. Thus when a syllable ending in ß occurs at the end of a line, it should be treated as s-(...) s() (where the empty syllable will get combined with the following one due to the new syllable rewriting code). (Technically, this splitting should occur whenever the hyphen is inserted, even in the middle of a line, but I assume that if the hyphen is getting inserted in the middle of the line, then it's because the notes above the syllable ending in ß are long enough to require it all the time and thus there is no problem with the user explicitly splitting the syllable themselves.)
The syntax of this feature is kind of complicated because it is inherently a 3-parter: end-of-line, beginning-of-line, no-line-break. I would propose something like:
Original request on user list.
Perhaps related to #1029, but perhaps not. At the very least this needs to play well with that issue.
A tag might needed which allows at least discritionary-like behavior in gabc. In this fashion one could specify different behavior for when a syllable occurs at the end of the line versus in the middle of it.
The original context of this request was placing verse numbers, barred letters, or other informational text below bar lines. In some instances this text corresponds to the next verse and should not end a line, but the bar line above it can (and really should, since we don't want to start a line with a bar line). For examples,
2.(::)
should effectively be(::z) 2.()
when it occurs at the end of the line (represented by thez
), but is just fine as it is when it occurs in the middle of the line.This cannot be automatic for all bar lines because there are times when the text below the bar line shouldn't advance to the next line automatically. For instance, in
bis.(::)
thebis.
refers to what just came before it (not what follows) and thus should stay with its bar line at the end of the line.It also occurs to me that in some instances the word hyphenation could benefit from this. For instance in German syllable ending in
ß
is hyphenated ass-s
. Thus when a syllable ending inß
occurs at the end of a line, it should be treated ass-(...) s()
(where the empty syllable will get combined with the following one due to the new syllable rewriting code). (Technically, this splitting should occur whenever the hyphen is inserted, even in the middle of a line, but I assume that if the hyphen is getting inserted in the middle of the line, then it's because the notes above the syllable ending inß
are long enough to require it all the time and thus there is no problem with the user explicitly splitting the syllable themselves.)The syntax of this feature is kind of complicated because it is inherently a 3-parter: end-of-line, beginning-of-line, no-line-break. I would propose something like:
However, if anyone has proposals for a more intuitive or simply syntax, I'm all ears.
The text was updated successfully, but these errors were encountered: