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

[lilypond]

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

The fact that it cannot be used in safe mode is only one manifestation of a  
more
fundamental issue. \include "italiano.ly" is semantically poor, because it  
uses a
catch-all construct that does not express what the user intention is. In  
other words,
it's a hack that should be promoted to a first-class construct.

I definitely support this and I'm happy to help with the implementation,  
although I
would not imagine it taking long to develop even by one person.

My take on design:

1. I would favour \lang "italiano", but I am not too fussed. Adding one  
command for
each language that we support now and in the future seems excessive and more
difficult to maintain.

2. I would prefer a block-scoped command, but we can start with a  
non-scoped command
if it's easier, and we can have both variations in the final version.

3. The current syntax is already self-deprecating. If your question is  
whether we
should explicitly error on \include "italiano" going forward, I think we  
should not.
It would be both cumbersome to implement and maintain, and it would break
backward-compatibility with precious little upside.
Of course the manual(s) will make it clear that going forward the new  
construct
should be used, and only mention the old construct as a historical note.

4. I think this change is simple, small and safe enough to start coding  
ASAP. Waiting
for a major release is not justified in my opinion.

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