Updates:
Status: Verified
Comment #8 on issue 1358 by percival.music.ca: run convert-ly on
translations
http://code.google.com/p/lilypond/issues/detail?id=1358
Looks fine.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu
Updates:
Status: Fixed
Labels: fixed_2_13_40
Comment #7 on issue 1358 by paconet.org: run convert-ly on translations
http://code.google.com/p/lilypond/issues/detail?id=1358
Now convert-ly runs on all docs without errors or warnings, in branch
lilypond/translation. Closing.
_
Updates:
Status: Started
Comment #6 on issue 1358 by paconet.org: run convert-ly on translations
http://code.google.com/p/lilypond/issues/detail?id=1358
As soon as that version string is updated, only a few warnings in Deutsch
still remain. Hopefully, that small edit together to a mer
Comment #5 on issue 1358 by percival.music.ca: run convert-ly on
translations
http://code.google.com/p/lilypond/issues/detail?id=1358
If the lilypond/translation de/fretted-strings has the correct
#default-fret-table thing, then the @c \version "2.13.x" should be at least
2.13.36. Please
Comment #4 on issue 1358 by paconet.org: run convert-ly on translations
http://code.google.com/p/lilypond/issues/detail?id=1358
I have run convert-ly on all docs and there are no new changes EXCEPT in
de/fretted-strings where it insists on adding a superfluous
#default-fret-table after \stor
Updates:
Labels: -Patch
Comment #3 on issue 1358 by paconet.org: run convert-ly on translations
http://code.google.com/p/lilypond/issues/detail?id=1358
Thanks for the patch. However, all changes are already applied. Till
Paala could still want to update version strings. Removing Pat
Updates:
Labels: Patch
Comment #2 on issue 1358 by percival.music.ca: run convert-ly on
translations
http://code.google.com/p/lilypond/issues/detail?id=1358
Patch here: http://codereview.appspot.com/3092041/
___
bug-lilypond mailing list
b
Status: Accepted
Owner: paconet.org
Labels: Type-Documentation Priority-Critical Maintainability
New issue 1358 by percival.music.ca: run convert-ly on translations
http://code.google.com/p/lilypond/issues/detail?id=1358
As describe in:
http://lilypond-translations.3384276.n2.nabble.com/Fwd-conv
Comment #1 on issue 1358 by percival.music.ca: run convert-ly on
translations
http://code.google.com/p/lilypond/issues/detail?id=1358
Please note that this update should use
convert-ly -e
*without* the newly-added -d option. The -d option will be required in the
policy fix for 1288, but
