lilypond-auto
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Lilypond-auto] Issue 2916 in lilypond: Doc : NR Document \hide comm


From: lilypond
Subject: Re: [Lilypond-auto] Issue 2916 in lilypond: Doc : NR Document \hide command
Date: Sat, 20 Oct 2012 07:59:37 +0000

Updates:
        Cc: address@hidden

Comment #1 on issue 2916 by address@hidden: Doc : NR Document \hide command
http://code.google.com/p/lilypond/issues/detail?id=2916

I think this is issue 2870, and the referenced message thread is about an outdated proposal where there were still both \hide and \hidden proposed. Documenting \hide should likely take the effects of issue 2883 into account which will allow also writing \hide Staff.TimeSignature when needed.

The same part of the change allowing for this syntax, however, will also require changing \footnote and \tweak syntax (as they can't use optional symbols before strings any more or vice versa). Because of the change of footnote syntax will only leave compilable documentation if the German translation has been merged, this depends on the post-2.16.1 translation branch merge into master.

Huh. I'd try breaking this increasingly awkward dependency chain by cherry-picking the German translations into staging ahead of time, but the required convert-ly run would likely complicate the merge. Unless one runs convert-ly on the translation branch before merging. But then both merge parents will be different from the common ancestor, and so there will be no automatic merge conflict resolution.

It is really probably best if we can get the translation branch moved to 2.17 soon.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]