[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: tetex 2.5 and lilypond 2.0
From: |
Erik Sandberg |
Subject: |
Re: tetex 2.5 and lilypond 2.0 |
Date: |
Tue, 11 Jul 2006 23:16:43 +0200 |
User-agent: |
KMail/1.9.1 |
On Tuesday 11 July 2006 17:13, Laura Conrad wrote:
> >>>>> "Erik" == Erik Sandberg <address@hidden> writes:
>
> Erik> On 7/11/06, Laura Conrad <address@hidden> wrote:
> >> >>>>> "Erik" == Erik Sandberg <address@hidden> writes:
>
> Erik> By the way, there are plans to drop the old-lyric-combine
> Erik> compatibility altogether, so in order to upgrade to the next
> Erik> stable version, you'll have to rewrite all your old-style
> Erik> \addlyrics expressions manually.
>
> >> I'm not sure how this differs from what I have to do now. Do
> >> you mean that in addition to breaking multi-verse upgrading,
> >> you're also planning to break single-verse upgrading?
>
> Erik> I think so. The command that used to be \addlyrics, and
> Erik> which now is known as \oldaddlyrics, will be
> Erik> removed. \lyricsto (and hte new \addlyrics) will be the only
> Erik> ways to align lyrics.
>
> I suppose I should be reading the fine manual more, but I've never
> figured out the difference between \oldaddlyrics and \addlyrics. In
> any case, my manual conversions use \addlyrics.
\addlyrics will still be supported, only \oldaddlyrics will be junked. So
according to what you say below, abc2ly will still work fine.
> I've never seen why convert-ly wouldn't be able to write that from the
> old output of abc2ly, but instead it writes:
The reason why convert-ly can't handle oldaddlyrics, is that it is based on
regexps, which makes it very difficult to move stuff far distances (such as
across a \context Staff ... expression).
--
Erik
Re: tetex 2.5 and lilypond 2.0, Mats Bengtsson, 2006/07/19