RE: 2.6.0: translate not working with mark

[Fairchild]

Does/will convert-ly properly handle the "" - " " vacillation?

There was a time when both were null, but "~" worked because the tilde was a
non-printing character.  This too vacillates.

Maybe the need can be eliminated?

                           - Bruce

-----Original Message-----
From: address@hidden
[mailto:address@hidden On Behalf Of
Mats Bengtsson
Sent: Thursday, June 30, 2005 9:12 AM
To: Colin Wilding
Cc: address@hidden
Subject: Re: 2.6.0: translate not working with mark


See the mailing list archives. If I remember correctly, an empty string is
now considered non-existing, but if you use " " instead of "", then it
should work.

    /Mats

Colin Wilding wrote:
> Using 2.6.0 (Windows)
> 
> There seems to be a problem with \translate in markup used with \mark
> 
> If you run the fragment below in version 2.4.3 (Cygwin) the markup 
> text text "here" appears above the fourth note. If you run it in 2.6.0 
> (Windows) it appears above the clef, i.e. untranslated.
> 
> \paper { raggedright = ##t }
> \score{ \relative c''{
> \mark \markup { "" \translate #(cons 30 0) here. }
> c4 d e f } }
> 
> --Colin Wilding
> 
> 
> _______________________________________________
> bug-lilypond mailing list
> address@hidden 
> http://lists.gnu.org/mailman/listinfo/bug-lilypond

-- 
=============================================
        Mats Bengtsson
        Signal Processing
        Signals, Sensors and Systems
        Royal Institute of Technology
        SE-100 44  STOCKHOLM
        Sweden
        Phone: (+46) 8 790 8463                         
         Fax:   (+46) 8 790 7260
        Email: address@hidden
        WWW: http://www.s3.kth.se/~mabe
=============================================


_______________________________________________
bug-lilypond mailing list
address@hidden http://lists.gnu.org/mailman/listinfo/bug-lilypond