RE: convert-ly 2.4.3 shortcomings

[Fairchild]

It's certainly reasonable not to expect too much from convert-ly, especially
since it is a somewhat temporary thing.

Might it be easy for such things to be spotted and comments made, e.g.:
"tilde found - if intended as non-printing character, change to blank" or
"use of \\\\ no longer supported in text strings"

Another option might be to provide a convenient compendium of shortcomings
somewhere.  Let users discover them, but scattered in the archives isn't
very convenient.

                                 - Bruce

-----Original Message-----
From: address@hidden
[mailto:address@hidden On Behalf Of
Mats Bengtsson
Sent: Friday, May 06, 2005 3:06 PM
To: address@hidden
Cc: address@hidden
Subject: Re: convert-ly 2.4.3 shortcomings


> > 6) Tilde is printed in 2.4.3.  Blank characters are accepted in 2.4.3.
> >     - Tilde "~" as blank in text strings => " ", blank now accepted, 
> > or ""
>
> I can't recall that this was something officially supported, are you 
> sure?

Standard TeX feature. You couldn't really expect convert-ly to be able to
handle any inline TeX code.

> > 7) Line breaks in header strings aren't converted.
> >     - \\\\  as line break in \header strings => \markup 
> > \center-align < "First Line" "Second Line" >

Same thing, in my opinion.

    /Mats


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