downgrade a file using convert-ly

[Federico Bruni]

Hi

how can I downgrade an input file using convert-ly?
I've tried:

convert-ly -e --from=2.17.20 --to=2.16.2 file.ly

but it doesn't seem to work.
I'm missing something?

Thanks
Federico
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: downgrade a file using convert-ly

[David Kastrup]

Federico Bruni  writes:

> Hi
>
> how can I downgrade an input file using convert-ly?
> I've tried:
>
> convert-ly -e --from=2.17.20 --to=2.16.2 file.ly
>
> but it doesn't seem to work.
> I'm missing something?

convert-ly has no knowledge of the various LilyPond formats, it just
uses programs based on Python pattern matching and replacement.

Those fragments only work in one direction.  convert-ly _only_ upgrades.
You have to downgrade manually.

-- 
David Kastrup


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: downgrade a file using convert-ly

[Federico Bruni]

2013/7/27 David Kastrup 

> convert-ly has no knowledge of the various LilyPond formats, it just
> uses programs based on Python pattern matching and replacement.
>
> Those fragments only work in one direction.  convert-ly _only_ upgrades.
> You have to downgrade manually.
>

ok, I suspected this
IMO this should be added to chapter 2 of Usage, I've added an issue:
https://code.google.com/p/lilypond/issues/detail?id=3477
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: \slashedGrace positioning problem

[Wim van Dommelen]

On 27 Jul 2013, at 05:05 , Nick Payne wrote:


On 27/07/13 07:52, Wim van Dommelen wrote:

Hi,

I've a piece starting with a \slashedGrace. See attached .png and .ly
for an example of what happens. I remember but cannot find back the
positioning at the beginning of a measure has been a problem before.

Any suggestions for a solution?


Just add \grace { s8 } immediately before the first note in VoiceII...

Thanks, I didn't think of that. But it is logical once seen..

Regards,
Wim.




Nick


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: 17th century English kbd ornaments

[Phil Holmes]

- Original Message - 
From: "DavidGriffel" 

To: 
Sent: Thursday, July 25, 2013 10:40 AM
Subject: 17th century English kbd ornaments



I've looked in the lilypond documentation for ornaments like these



The images are from the explanations of ornaments in Purcell's "A Choice
Collection of Lessons", 1696 (on imslp.org).  There are a few others that
are common in Purcell et al, and the shake // (and a similar ornament with
only one line) is very common in Byrd and the other virginalist composers.

If they're not in lilypond, would be good to have them.  I can't offer any
lilypond expertise, but could sponsor them if the sponsorship system is
still in place.

David



It would certainly be possible and fairly simple to create glyphs like this. 
We would need to be careful about naming, since a shake is generally 
something else.  However, you may be able to create what you want yourself. 
Have you looked at 
http://lilypond.org/doc/v2.17/Documentation/notation/graphic ?


--
Phil Holmes 



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: 17th century English kbd ornaments

[DavidGriffel]

Thank you very much Phil.  I hadn't noticed this bit of the markup
documentation, and it should do the trick.
David Griffel


On Sat, Jul 27, 2013 at 4:43 PM, Phil Holmes-2 [via Lilypond] <
ml-node+s1069038n148474...@n5.nabble.com> wrote:

> - Original Message -
> From: "DavidGriffel" <[hidden 
> email]>
>
> To: <[hidden email] >
>
> Sent: Thursday, July 25, 2013 10:40 AM
> Subject: 17th century English kbd ornaments
>
>
> > I've looked in the lilypond documentation for ornaments like these
> > 
> > 
> >
> > The images are from the explanations of ornaments in Purcell's "A Choice
> > Collection of Lessons", 1696 (on imslp.org).  There are a few others
> that
> > are common in Purcell et al, and the shake // (and a similar ornament
> with
> > only one line) is very common in Byrd and the other virginalist
> composers.
> >
> > If they're not in lilypond, would be good to have them.  I can't offer
> any
> > lilypond expertise, but could sponsor them if the sponsorship system is
> > still in place.
> >
> > David
>
>
> It would certainly be possible and fairly simple to create glyphs like
> this.
> We would need to be careful about naming, since a shake is generally
> something else.  However, you may be able to create what you want
> yourself.
> Have you looked at
> http://lilypond.org/doc/v2.17/Documentation/notation/graphic ?
>
> --
> Phil Holmes
>
>
> ___
> lilypond-user mailing list
> [hidden email] 
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
>
> --
>  If you reply to this email, your message will be added to the discussion
> below:
>
> http://lilypond.1069038.n5.nabble.com/17th-century-English-kbd-ornaments-tp148407p148474.html
>  To unsubscribe from 17th century English kbd ornaments, click 
> here
> .
> NAML
>




--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/17th-century-English-kbd-ornaments-tp148407p148475.html
Sent from the User mailing list archive at Nabble.com.___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Writing "Mouvt" abbreviation of "Mouvement"

[MarcM]

I'm trying to write "Mouvt" the abbreviation of the french word "Mouvement"
For some reason a whitespace is inserted between the 'v' and the 't'
MouvtRubato.ly
  
MouvtRubato.pdf
  

\version "2.17.22" 

MouvtRubatoA = \markup{ Mouv\raise #0.5 {\small t} (Rubato)} 
MouvtRubatoB = \markup{ Mouv\super{t} (Rubato)} 

{ \relative c'{ 
c^\MouvtRubatoA 
}} 
{ \relative c'{ 
c^\MouvtRubatoB 
}}




--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Writing-Mouvt-abbreviation-of-Mouvement-tp148476.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Finale bug from Lilypond "Essay" found in commercial score

[Michael Rivers]

I'm typesetting Earl Wild's piano transcription of Rachmaninoff's "In the
Silent Night" in Lilypond for my own use. The original is set using Finale
from around 1990 (the copyright date). In bar 31, there's a B sharp in the
second voice in the right hand, and later in the bar, an octave B natural in
the first voice. However, the engraver has forgotten to draw a natural sign
in front of one of the B's in the first voice. I confirmed that the natural
is intended by listening to Wild's own recording. This is the exact same
Finale bug mentioned in the Bach Fugue example from the "Essay on Automated
Music Engraving" on the Lilypond site! It just goes to show that even good
typesetters can't catch all of Finale's mistakes.



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Finale-bug-from-Lilypond-Essay-found-in-commercial-score-tp148477.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Writing "Mouvt" abbreviation of "Mouvement"

[Rachael Thomas Carlson]

Hello Marc:

On Sat, 2013-07-27 at 10:11 -0700, MarcM wrote:
> I'm trying to write "Mouvt" the abbreviation of the french word "Mouvement"
> For some reason a whitespace is inserted between the 'v' and the 't'
> MouvtRubato.ly
>   
> MouvtRubato.pdf
>   
> 
> \version "2.17.22" 
> 
> MouvtRubatoA = \markup{ Mouv\raise #0.5 {\small t} (Rubato)} 
\version "2.17.22" 

try: 

MouvtRubatoB = \markup { \concat { Mouv\raise #0.5 {\small t} "
" (Rubato)}}

Concatenation works on my version 2.16.2.  I think that it still works
in 2.17.22, I may be wrong though.

Rachael 

> MouvtRubatoB = \markup{ Mouv\super{t} (Rubato)} 
> 
> { \relative c'{ 
> c^\MouvtRubatoA 
> }} 
> { \relative c'{ 
> c^\MouvtRubatoB 
> }}
> 
> 
> 
> 
> --
> View this message in context: 
> http://lilypond.1069038.n5.nabble.com/Writing-Mouvt-abbreviation-of-Mouvement-tp148476.html
> Sent from the User mailing list archive at Nabble.com.
> 
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user



___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: 17th century English kbd ornaments

[David Rogers]

"Phil Holmes"  writes:

> It would certainly be possible and fairly simple to create glyphs like
> this. We would need to be careful about naming, since a shake is
> generally something else.

There are indeed two quite different things both normally called
"shake", one more recent (stereotypically expected in a jazz-band
trumpet part) and the other less recent (a trill-like keyboard
ornament). People who aren't particularly jazz/pop oriented could
legitimately say that the jazz players were the ones who ought to have
been careful about naming, but that's "water under the bridge", as they
say. :) I guess both names "trill" and "shake" are already used for
signs in lilypond, so the keyboard ornament shake (if permanently added)
will need a special name. Hopefully something clear in meaning and not
too hard to type can be found... "keyboardshake" seems a bit long.

-- 
David R

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Writing "Mouvt" abbreviation of "Mouvement"

[David Kastrup]

MarcM  writes:

> I'm trying to write "Mouvt" the abbreviation of the french word "Mouvement"
> For some reason a whitespace is inserted between the 'v' and the 't'
> MouvtRubato.ly
>   

Why wouldn't it?  Separate expressions in a \line (which is what a
top-level markup is implicitly wrapped in) are separated by word space.
That's totally normal.  If you want to join some elements, use \concat,
like with
\concat { Mouv \raise #0.5 \small t }
or \concat { Mouv \super t }

Things may become clearer if you realize that
\markup { fee fie foe fum }
does not contain a single space, but rather four separate markup expressions.

Distinguish that from
\markup { "fee fie foe fum" }
which contains a single markup expression containing spaces.

So if you write
\markup { \huge { fee fie foe fum } }
this is the same as
\markup { \huge fee \huge fie \huge foe \huge fum }
or even
\markup { \huge fee\huge fie\huge foe\huge fum }
and will separate the expressions with _normal_ size spaces whereas
\markup { \huge "fee fie foe fum" }
or
\markup { \huge \line { fee fie foe fum } }
will use _huge_ spaces between words.

If you can't avoid having separate expressions (like when the second
expression starts with \raise), then you need to use something other
than the implicit \line, like \concat.

> \version "2.17.22" 
>
> MouvtRubatoA = \markup{ Mouv\raise #0.5 {\small t} (Rubato)} 
> MouvtRubatoB = \markup{ Mouv\super{t} (Rubato)} 
>
> { \relative c'{ 
> c^\MouvtRubatoA 
> }} 
> { \relative c'{ 
> c^\MouvtRubatoB 
> }}

The formatting leaves something to be desired.

-- 
David Kastrup


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: change the key signature

[David Rogers]

Givaldo de Cidra  writes:

> Could you help me with a code in lilypond?
>
> I have a musical example it was necessary to change the key signature.
> I made the change with the code below:
>
> \ set Staff.keySignature '= # (((1. 0.), SHARP) ((1. 3.), natural))
>
> Placing a hash in C and makes the natural inf F
>
> Solved for a moment, but now I think it would be better that instead
> of NATURAL was one natural sign of caution ...
>
> I would take into the key signature a C sharp and natural sign in
> brackets.
> Is this possible?


I just want to make sure I understand your question: Are you only
looking for a way to get brackets around the natural, in the key
signature you already have?


-- 
David R

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Writing "Mouvt" abbreviation of "Mouvement"

[Pierre Perol-Schneider]

2013/7/27 MarcM 

MouvtRubatoA = \markup{ Mouv\raise #0.5 {\small t} (Rubato)}
> MouvtRubatoB = \markup{ Mouv\super{t} (Rubato)}
>

MouvtRubatoA = \markup\concat { Mouv\raise #0.5 { \small t} " (Rubato)" }
MouvtRubatoB = \markup\concat  { Mouv \super {t} " (Rubato)" }

should do what you're looking for.
Cheers,
Pierre
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: 17th century English kbd ornaments

[David Griffel]

On Sat, Jul 27, 2013 at 8:29 PM, David Rogers
wrote:

> "Phil Holmes"  writes:
>
> > It would certainly be possible and fairly simple to create glyphs like
> > this. We would need to be careful about naming, since a shake is
> > generally something else.
>
> ...



> I guess both names "trill" and "shake" are already used for
> signs in lilypond, so the keyboard ornament shake (if permanently added)
> will need a special name. Hopefully something clear in meaning and not
> too hard to type can be found... "keyboardshake" seems a bit long.
>
> Yes, this is rather a minefield.  The // sign has different meanings at
different periods.  It's a trill for Purcell, and also Buxtehude (I think)
but in early 17th cent. English kbd music there is // and /, often written
across the stem, and their meanings are not 100% clear. A + over a note can
mean a trill in 17th century Germany, but in lilypond it's called \stopped.

Anyway, I can't think of a good clear name for the // ornament.  I'll just
concentrate on learning the graphic markup commands that Phill point to.
David G
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: change the key signature

[Givaldo de Cidra]

2013/7/27 David Rogers 

> Givaldo de Cidra  writes:
>
> > Could you help me with a code in lilypond?
> >
> > I have a musical example it was necessary to change the key signature.
> > I made the change with the code below:
> >
> > \ set Staff.keySignature '= # (((1. 0.), SHARP) ((1. 3.), natural))
> >
> > Placing a hash in C and makes the natural inf F
> >
> > Solved for a moment, but now I think it would be better that instead
> > of NATURAL was one natural sign of caution ...
> >
> > I would take into the key signature a C sharp and natural sign in
> > brackets.
> > Is this possible?
>
>
> I just want to make sure I understand your question: Are you only
> looking for a way to get brackets around the natural, in the key
> signature you already have?
>

Yes, just it.

\set Staff.keySignature '= # (((1. 0.), SHARP) ((1. 3.), natural))

I want the key signature have a natural sign of caution.

Is it possible?

Thanks

-- 
Givaldo de Cidra
"Ser e Pensar Sempre no Objetivo é o Caminho para Alcançar o Sucesso"
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Writing "Mouvt" abbreviation of "Mouvement"

[MarcM]

thanks for the explanation.

> Why wouldn't it?  Separate expressions in a \line (which is what a
> top-level markup is implicitly wrapped in) are separated by word space.
> That's totally normal.  If you want to join some elements, use \concat,
> like with ...

You explanation and example were helpful. I suggest to add them to
this page: 
http://www.lilypond.org/doc/v2.17/Documentation/notation/formatting-text

% this
 \markup { \huge \line { fee fie foe fum } }
% or that will separate the expressions with _normal_ size spaces
 \markup { \huge  { fee fie foe fum } }
% or
\markup { \huge fee\huge fie\huge foe\huge fum }
% whereas this will use _huge_ spaces between words.
\markup { \huge "fee fie foe fum" }

On Sat, Jul 27, 2013 at 4:27 PM, David Kastrup [via Lilypond]
 wrote:
> MarcM <[hidden email]> writes:
>
>> I'm trying to write "Mouvt" the abbreviation of the french word
>> "Mouvement"
>> For some reason a whitespace is inserted between the 'v' and the 't'
>> MouvtRubato.ly
>> 
>
> Why wouldn't it?  Separate expressions in a \line (which is what a
> top-level markup is implicitly wrapped in) are separated by word space.
> That's totally normal.  If you want to join some elements, use \concat,
> like with
> \concat { Mouv \raise #0.5 \small t }
> or \concat { Mouv \super t }
>
> Things may become clearer if you realize that
> \markup { fee fie foe fum }
> does not contain a single space, but rather four separate markup
> expressions.
>
> Distinguish that from
> \markup { "fee fie foe fum" }
> which contains a single markup expression containing spaces.
>
> So if you write
> \markup { \huge { fee fie foe fum } }
> this is the same as
> \markup { \huge fee \huge fie \huge foe \huge fum }
> or even
> \markup { \huge fee\huge fie\huge foe\huge fum }
> and will separate the expressions with _normal_ size spaces whereas
> \markup { \huge "fee fie foe fum" }
> or
> \markup { \huge \line { fee fie foe fum } }
> will use _huge_ spaces between words.
>
> If you can't avoid having separate expressions (like when the second
> expression starts with \raise), then you need to use something other
> than the implicit \line, like \concat.
>
>> \version "2.17.22"
>>
>> MouvtRubatoA = \markup{ Mouv\raise #0.5 {\small t} (Rubato)}
>> MouvtRubatoB = \markup{ Mouv\super{t} (Rubato)}
>>
>> { \relative c'{
>> c^\MouvtRubatoA
>> }}
>> { \relative c'{
>> c^\MouvtRubatoB
>> }}
>
> The formatting leaves something to be desired.
>
> --
> David Kastrup
>
>
> ___
> lilypond-user mailing list
> [hidden email]
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
>
> 
> If you reply to this email, your message will be added to the discussion
> below:
> http://lilypond.1069038.n5.nabble.com/Writing-Mouvt-abbreviation-of-Mouvement-tp148476p148480.html
> To unsubscribe from Writing "Mouvt" abbreviation of "Mouvement", click here.
> NAML



-- 
Marc Mouries
571-428-6771




--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Writing-Mouvt-abbreviation-of-Mouvement-tp148476p148487.html
Sent from the User mailing list archive at Nabble.com.___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Writing "Mouvt" abbreviation of "Mouvement"

[Nick Payne]

On 28/07/13 11:47, MarcM wrote:

thanks for the explanation.

 > Why wouldn't it?  Separate expressions in a \line (which is what a
 > top-level markup is implicitly wrapped in) are separated by word space.
 > That's totally normal.  If you want to join some elements, use \concat,
 > like with ...

You explanation and example were helpful. I suggest to add them to
this page:
http://www.lilypond.org/doc/v2.17/Documentation/notation/formatting-text

% this
  \markup { \huge \line { fee fie foe fum } }
% or that will separate the expressions with _normal_ size spaces
  \markup { \huge  { fee fie foe fum } }
% or
\markup { \huge fee\huge fie\huge foe\huge fum }
% whereas this will use _huge_ spaces between words.
\markup { \huge "fee fie foe fum" }



That suggestion doesn't make sense to me. Those four markup commands 
will all produce identical markup with identical spacing.


The use of \concat to eliminate spaces that would otherwise be inserted 
is covered in 
http://www.lilypond.org/doc/v2.17/Documentation/notation/formatting-text#selecting-font-and-font-size 
- though to me it would make more sense to have it in the section 
dealing with text alignment.


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Writing "Mouvt" abbreviation of "Mouvement"

[MarcM]

as described int the comments, the first 3 markup produce the same
spacing while the last one does not. See attachment.


On Sat, Jul 27, 2013 at 10:20 PM, Nick Payne-3 [via Lilypond]
 wrote:
> On 28/07/13 11:47, MarcM wrote:
>
>> thanks for the explanation.
>>
>>  > Why wouldn't it?  Separate expressions in a \line (which is what a
>>  > top-level markup is implicitly wrapped in) are separated by word space.
>>  > That's totally normal.  If you want to join some elements, use \concat,
>>  > like with ...
>>
>> You explanation and example were helpful. I suggest to add them to
>> this page:
>> http://www.lilypond.org/doc/v2.17/Documentation/notation/formatting-text
>>
>> % this
>>   \markup { \huge \line { fee fie foe fum } }
>> % or that will separate the expressions with _normal_ size spaces
>>   \markup { \huge  { fee fie foe fum } }
>> % or
>> \markup { \huge fee\huge fie\huge foe\huge fum }
>> % whereas this will use _huge_ spaces between words.
>> \markup { \huge "fee fie foe fum" }
>>
>
> That suggestion doesn't make sense to me. Those four markup commands
> will all produce identical markup with identical spacing.
>
> The use of \concat to eliminate spaces that would otherwise be inserted
> is covered in
> http://www.lilypond.org/doc/v2.17/Documentation/notation/formatting-text#selecting-font-and-font-size
> - though to me it would make more sense to have it in the section
> dealing with text alignment.
>
> ___
> lilypond-user mailing list
> [hidden email]
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
>
> 
> If you reply to this email, your message will be added to the discussion
> below:
> http://lilypond.1069038.n5.nabble.com/Writing-Mouvt-abbreviation-of-Mouvement-tp148476p148488.html
> To unsubscribe from Writing "Mouvt" abbreviation of "Mouvement", click here.
> NAML



-- 
Marc Mouries
571-428-6771


MouvtRubato.pdf (27K) 





--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Writing-Mouvt-abbreviation-of-Mouvement-tp148476p148489.html
Sent from the User mailing list archive at Nabble.com.___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Slurs end point need to be different when going up & down

[MarcM]

If we compare slurs in original scores. We can see that when the second note
included in the slur is going up, the end point of the slur ends on a south
west point. 

 

When the interval goes down, the end point of the slur ends on a south east
point of the note.

 

Slurs in lilypond are pretty close when the internal is going up. However
when the interval is going down, the end point is such that the slur appears
to miss the note:
  

I was initially going to tweak the slur but we should not have to do that
for every slur going down.
 



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/Slurs-end-point-need-to-be-different-when-going-up-down-tp148490.html
Sent from the User mailing list archive at Nabble.com.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Writing "Mouvt" abbreviation of "Mouvement"

[David Kastrup]

Nick Payne  writes:

> On 28/07/13 11:47, MarcM wrote:
>> thanks for the explanation.
>>
>>  > Why wouldn't it?  Separate expressions in a \line (which is what a
>>  > top-level markup is implicitly wrapped in) are separated by word space.
>>  > That's totally normal.  If you want to join some elements, use \concat,
>>  > like with ...
>>
>> You explanation and example were helpful. I suggest to add them to
>> this page:
>> http://www.lilypond.org/doc/v2.17/Documentation/notation/formatting-text
>>
>> % this
>>   \markup { \huge \line { fee fie foe fum } }
>> % or that will separate the expressions with _normal_ size spaces
>>   \markup { \huge  { fee fie foe fum } }
>> % or
>> \markup { \huge fee\huge fie\huge foe\huge fum }
>> % whereas this will use _huge_ spaces between words.
>> \markup { \huge "fee fie foe fum" }
>>
>
> That suggestion doesn't make sense to me. Those four markup commands
> will all produce identical markup with identical spacing.

I disagree.  And so does LilyPond.

<>
Sometimes I actually know what I am talking about.

-- 
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user