Fair enough.
I don't mean to sound impatient or ungrateful - Lilypond is the best
thing since sliced bread and I am eager to start using the new
features in 2.6. I am just just trying to avoid going to extra effort
converting old files as a result of my own ignorance of the process.
--Colin
On
Colin Wilding wrote:
This may turn out to be a bit of an inconvenience.
I use "" \translate a lot to position text precisely on a score,
because AFAIK it is the only way to do it, as \translate will not work
without something in front of it.
I can confirm that convert-ly does not change "" to " "
This may turn out to be a bit of an inconvenience.
I use "" \translate a lot to position text precisely on a score,
because AFAIK it is the only way to do it, as \translate will not work
without something in front of it.
I can confirm that convert-ly does not change "" to " ", as I noticed
the orig
On Thursday 30 June 2005 16.41, Fairchild wrote:
> 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?
AFAIK, the "" / "
Ooo, yes, so it does. Thank you.
--Colin
On 6/30/05, Mats Bengtsson <[EMAIL PROTECTED]> wrote:
> 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 wr
inal Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Mats Bengtsson
Sent: Thursday, June 30, 2005 9:12 AM
To: Colin Wilding
Cc: bug-lilypond@gnu.org
Subject: Re: 2.6.0: translate not working with mark
See the mailing list archives. If I remember correctly, an empt
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 t
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 { r
