Re: Force Lilypond to preserve vertical order of TextScripts?

2018-02-19 9:35 GMT+01:00 David Kastrup : > Saul Tobin writes: > >> I probably will write such a function to deal with my immediate needs, but >> I raise the issue because this is a case where Lilypond has well defined >> behavior MOST of the time, and

Re: Force Lilypond to preserve vertical order of TextScripts?

Saul Tobin writes: > I probably will write such a function to deal with my immediate needs, but > I raise the issue because this is a case where Lilypond has well defined > behavior MOST of the time, and then sometimes violates it. No, it doesn't. Short of other

Re: Force Lilypond to preserve vertical order of TextScripts?

Is that the same scenario? By "encountered first" is the doc referring to the parser or to the moment in musical time? I can attempt turning off skylines, but I suspect the score will just explode. I haven't had time to construct a controlled example of the squished spacing. Seems hard to make it

Re: Force Lilypond to preserve vertical order of TextScripts?

Hi Saul, > I'm actually surprised that ordering behavior isn't documented. It's so > consistent 99% of the time I just assumed it was officially defined behavior. Well, says “If two objects have the same

Re: Force Lilypond to preserve vertical order of TextScripts?

I'm actually surprised that ordering behavior isn't documented. It's so consistent 99% of the time I just assumed it was officially defined behavior. On Sun, Feb 18, 2018 at 6:30 PM, Kieren MacMillan < kieren_macmil...@sympatico.ca> wrote: > Hi Saul, > > > I probably will write such a function >

Re: Force Lilypond to preserve vertical order of TextScripts?

Hi Saul, > I probably will write such a function Excellent! Be sure to share it with the list. > when you write ^"one"^"two" you expect "two" to be displayed above "one." I've actually never had that expectation! (Perhaps I should have? I guess I just assumed it works like every other

Re: Force Lilypond to preserve vertical order of TextScripts?

I probably will write such a function to deal with my immediate needs, but I raise the issue because this is a case where Lilypond has well defined behavior MOST of the time, and then sometimes violates it. Normally, when you write ^"one"^"two" you expect "two" to be displayed above "one." It

Re: Force Lilypond to preserve vertical order of TextScripts?

This is exactly my point. All of the suggested solutions to maintain consistent vertical ordering require using a case-by-case override or markup function. There is no way to create a global setting to force Lilypond to respect text vertical ordering. MOST of the time, Lilypond respects the order

Re: Force Lilypond to preserve vertical order of TextScripts?

On 02/18, Saul Tobin wrote: > This is exactly the sort of situation I'm talking about. You're correct > that the order doesn't change the meaning, just as changing the vertical > order of instruments in the score doesn't change the scoring. But there is > a strong convention of how to order

Re: Force Lilypond to preserve vertical order of TextScripts?

Hi Torsten, > Sometimes, the order of stacks /is/ important and you even can't always put > them together into a \markup column I didn’t refute that. I simply pointed out there is nothing in Lilypond to distinguish between when script order is important and when it's not — so she does what she

Re: Force Lilypond to preserve vertical order of TextScripts?

Hi Kieren, Sometimes, the order of stacks /is/ important and you even can't always put them together into a \markup column: Fingering, for example, uses script-priority, too. This time, it does not depend on any input order, but the script-priority is calculated from the Y-position of the

Re: Force Lilypond to preserve vertical order of TextScripts?

Hi Saul, > However, the vertical order of expressions is part of content, not a purely > graphical layout issue. Hmmm… I'm not sold on that. If I write versus , is the order part of the content? All three notes appear at the same musical moment, and will appear vertically

Re: Force Lilypond to preserve vertical order of TextScripts?

Indeed. However, the vertical order of expressions is part of content, not a purely graphical layout issue. On Sun, Feb 18, 2018 at 1:08 PM, David Kastrup wrote: > Saul Tobin writes: > > > It seems very un-Lilypond-like for the output to be so

Re: Force Lilypond to preserve vertical order of TextScripts?

Saul Tobin writes: > It seems very un-Lilypond-like for the output to be so unpredictable, No. It is the job of LilyPond to arrange elements in the best possible manner representing the input, and that is what it does. LilyPond is not a music typewriter, but a

Re: Force Lilypond to preserve vertical order of TextScripts?

Hi Saul, > It seems very un-Lilypond-like for the output to be so unpredictable, given > that the order is well defined most of the time. It is hard to predict from > the code when Lilypond will violate the specified order, so the only real > solution is to combine expressions into a single

Re: Force Lilypond to preserve vertical order of TextScripts?

Hi Joram, TextScript.script-priority has a default value of 200. Each concurrent TextScript will be counted up (starting with 200+0 = 200, 200+1 = 201, 200+2 = 202, etc.) by default. The smaller the number, the closer to the notehead. So, by default, LilyPond will keep the order of TextScripts

Re: Force Lilypond to preserve vertical order of TextScripts?

It seems very un-Lilypond-like for the output to be so unpredictable, given that the order is well defined most of the time. It is hard to predict from the code when Lilypond will violate the specified order, so the only real solution is to combine expressions into a single markup 100% of the

Re: Force Lilypond to preserve vertical order of TextScripts?

Hi, Am 18.02.2018 um 14:16 schrieb Torsten Hämmerle: > How about script-priority? That seems to work: { a-\tweak script-priority #201 -"p=201" -"p default" a a a a-\tweak script-priority #202 -"p=202" -"p default" a a a } According to this example the default priority seems to be

Re: Force Lilypond to preserve vertical order of TextScripts?

How about script-priority? I always thought that concurrent (Text)Scripts will be internally numbered by counting up script-priority in the order given and the first (Text)Scripts will be printed closest to the noteheads (depending on whether the scripts are above or below the stave). So, even

Re: Force Lilypond to preserve vertical order of TextScripts?

Saul Tobin writes: > That's a reasonable workaround, but it's not semantic. A single column > markup is appropriate for one expression split across lines IMO. If it's > multiple expressions communicating distinct things, it makes sense to keep > them separate,

Re: Force Lilypond to preserve vertical order of TextScripts?

That's a reasonable workaround, but it's not semantic. A single column markup is appropriate for one expression split across lines IMO. If it's multiple expressions communicating distinct things, it makes sense to keep them separate, particularly if one or more of them are predefined markups. On

Re: Force Lilypond to preserve vertical order of TextScripts?

On 18.02.2018 01:19, Saul Tobin wrote: Is there a way to force Lilypond to respect the specified vertical order of TextScripts? Ideally, not as a one time override or tweak but throughout an entire score. The solution that comes to mind is assigning different values of

Re: Force Lilypond to preserve vertical order of TextScripts?

Saul Tobin writes: > Hi all, > > I've noticed that under certain circumstances (I think if the page spacing > needs to be compressed?) Lilypond will disregard the vertical order of > TextScripts. So something like: > > \relative c'' { > f4^"long long long"^"short"

Force Lilypond to preserve vertical order of TextScripts?

Hi all, I've noticed that under certain circumstances (I think if the page spacing needs to be compressed?) Lilypond will disregard the vertical order of TextScripts. So something like: \relative c'' { f4^"long long long"^"short" e'2. } By itself, this correctly displays the short indication