[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Issue 903 in lilypond: Enhancement: a more user-friendly way to spec
From: |
lilypond |
Subject: |
Re: Issue 903 in lilypond: Enhancement: a more user-friendly way to specify notename languages |
Date: |
Tue, 24 Nov 2009 14:29:40 +0000 |
Comment #19 on issue 903 by veryfurryfur: Enhancement: a more user-friendly
way to specify notename languages
http://code.google.com/p/lilypond/issues/detail?id=903
LilyPondTool parses the input file to do syntax checking.
I see, ok this makes sense.
But still, is it really going to take 18 months for dependencies to pick up
a change
in syntax? How did LilyPondTool cope with previous changes? Is there a
protocol in
place? (E.g. we notify them in advance, they build the necessary changes in
preparation for our release, etc.)
It seems like we are going from one extreme (whenever) to the other (18
months)...
Safe mode note name changing can be achieved by other means.
I'm interested (as a work-around). Could you please let me know, perhaps in
private
communication (just add @gmail.com)? Thanks.
I don't like the idea of having a \language command *and* the old
\include method
Can you elaborate on your preference please? To me it seems like throwing
away
backwards compatibility for no particular benefit. I agree we should
deprecate, but
still support the old syntax, and get rid of it in the next major version.
Seems
standard procedure for this kind of things...
Thanks.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings