Hi,

2013/7/28 David Kastrup <d...@gnu.org>

> Nick Payne <nick.pa...@internode.on.net> writes:
>
> > On 28/07/13 11:47, MarcM wrote:
> >> 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
>

+1 for adding this to documentation.


> >>
> >> % 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.
>
> Actually, MarcM committed copy&paste error here.  What I wrote was
>
> %    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.
>
> And look-and-behold, LilyPond does _not_ agree with me here in that
> _only_ the fourth line sticks out.  So \huge does not appear to scale
> LilyPond's idea of word space, but the fourth line still looks different
> because when you use literal spaces, it is Pango's idea of the space
> width that is getting used, not LilyPond's, and Pango's idea scales.
>
> It turns out that \huge ... is defined equivalent to
> \override #'(font-size . 2) ...
> whereas
> \fontsize #2
> would be equivalent to
>
> \override #'(font-size . 2) \override #`(word-space . ,(magstep 2))
>   \override #`(baseline-skip . ,...)
>
> Actually, things are even more complex since \fontsize accumulates
> while \huge doesn't.
>

This is indeed quite inconsistent...

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

Reply via email to