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

[lilypond]

Comment #2 on issue 903 by Carl.D.Sorensen: Enhancement: a more  
user-friendly way to specify notename languages
http://code.google.com/p/lilypond/issues/detail?id=903

In keeping with LilyPond style we should use

\language "italiano" or
\noteLanguage italiano

We should not use

\lang

because we don't use abbreviations, contractions, or other shortened words.

Of course we will need a convert-ly rule, even if it's a NotSmart rule  
(don't know if my capitalization is
correct).

Block scoping would probably be nice, but I expect it to require a major  
change, because right now LilyPond
does not have block scoping, IIUC.

If block scoping is implemented, there should probably be both block  
scoping constructs and state changing
constructs, IMO.

e.g. \setNoteLanguage "italiano" would change the state to italian for the  
parser, without any block
limitations, while \useNoteLanguage "italiano" {block} would parse block  
with italian as the input note
language.

But I think the best way to approach this (like all enhancements) is to  
work on a patch, and post it for review,
and then get feedback.

Thanks,

Carl

--
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