Re: Issue 2026 in lilypond: Make markup utility definitions available via new (scm markup-utility-defs) scheme module

[lilypond]

Comment #35 on issue 2026 by address@hidden: Make markup utility  
definitions available via new (scm markup-utility-defs) scheme module
http://code.google.com/p/lilypond/issues/detail?id=2026

From bug-lilypond, reported by Robin Bannister
http://lists.gnu.org/archive/html/bug-lilypond/2012-02/msg00029.html
In http://code.google.com/p/lilypond/issues/detail?id=2026#c32 Ian Hulin  
wrote:

    This is fixed if we move the definition of the \null markup to the  
before the empty-markup declaration and change empty-markup to

    (define-public (empty-markup)
       make-null-markup))
    ...

    It's built the docs successfully and run reg-tests OK.


OK, the docs say \null markup is an "empty markup", merely a single point,  
but it has _position_, which empty-markup does not. The following snippet  
demonstrates this difference: %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

offset = \markup \translate #'(9 . 9) "offset"

\markup \line { "concat with empty-markup:" \box \concat { \empty-markup  
\offset } " concat with null markup: "\box \concat { \null \offset }

}
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%



Cheers, Robin