Re: Issue 903 in lilypond: Enhancement: a more user-friendly way to specify notename languages

[lilypond]

Comment #15 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

> there will be no syntax changes within stable numbers (i.e. 2.12.x,  
> 2.14.y).

Sorry, what do you mean? According to the download page, currently 2.12.2  
is stable,
and 2.13.x is not. Does it mean that we can have a syntax change in  
2.13.x+1, but not
in a potential 2.12.3?
I just think that postponing this change for 12-18 months is not backed up  
by our
risk analysis so far. Also, not knowing anything about 3.0, I don't  
understand why
the \language syntax would need to change again in that version.

> As for "client programs", I'm thinking of things like lilywizardtemplate
> (or whatever it's called).  If we change the format of  
> \include "language.ly", then
> this tool will break.

OK, I need to understand this better. Could you please give me a link that  
explains
what this tool does? How is it going to break exactly? Again, sorry to  
insist on this
point, but please note that we are not really _changing_ the format of  
\include
"language.ly", we are just _extending_ the syntax a new, better way of  
doing it.
The worst that I can imagine happen so far is that an IDE fails to  
highlight the new
syntax if the user upgrades the back-end but not the front-end; or if the  
front-end
development is not quick enough to pick up the back-end change.
I think that's a risk worth taking, since the upside is to have a \language  
construct
that works in safe mode, apart from other cosmetic considerations.

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