Noeck <[email protected]> writes: > Having different *input* syntax for different people according to their > taste is more complicated and it's doubtable that this is a good aim for > LilyPond. Exchanging code gets more complicated and small snippets are > not necessarily self-consistent. You always would have to specify the > definitions. One example where it is possible is the input language of > notes (e.g. \language english): In my German (\language deutsch) code <c > e g b> is a C7 chord not a Cmaj7. For note names I like that. > What I am trying to say: Adjustable input syntax also makes life more > complicated in other circumstances.
\language is usually a closed set, so editors like Frescobaldi can be taught to convert from one to another. Conversions of freely user-defined syntaxes is something entirely else, though. -- David Kastrup _______________________________________________ lilypond-user mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-user
