bug-lilypond
[Top][All Lists]
Advanced

[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: Wed, 20 Oct 2010 16:08:54 +0000

Updates:
        Status: Started
        Labels: Patch

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

Attached is a patch that suggests a much simpler solution than what has been discussed above.

This commit adds a new file, lang-init.ly, that
introduces new shortcut commands for notenames
language selection: instead of using \include "italiano.ly",
just use \langItaliano, and so on.

Standalone shortcuts have been defined for all available
languages.  A different syntax has been considered, such as

  \lang "italiano"

However, since the only way to pass arguments is currently
through a music-functions, and since you can't have toplevel
LilyPond definitions inside a music function, this would
require to modify either the parser (a rather heavy change)
either the italiano.ly&co files, which would break compatibility
with existing code.  The way I chose was the lightest, safest
and the most straightforward.

For now, full compatibility with the old syntax is preserved.  Once
people get used to the new syntax, we may consider a slightly different
implementation (or not).  For instance, if we were to implement the
\lang "italiano" solution, then introducing it would only be a matter
of changing lang-init accordingly:
langItaliano = \lang "italiano"

If this proposal is accepted, of course I'll take care of updating the docs,
and I'll open a new issue to gracefully deprecate the old syntax (writing
convert-ly rules, etc.) -- for which the GLISS process would be an appropriate
time.

Attachments:
        0001-Fix-903-Add-shortcuts-for-note-names-languages.patch  4.1 KB




reply via email to

[Prev in Thread] Current Thread [Next in Thread]