On Sun, 2014-08-24 at 00:03 +0200, Janek Warchoł wrote:
> Btw, "bn" would also help people who have to switch between german and > dutch/english naming often (e.g. me). Janek makes a good point, but I'm not sure whether the problem to which he refers is caused by the existence of different national conventions in real life, or the existence of alternative syntaxes in lilypond source. If the latter, we might be about to compound the problem: We already have language-specific suffixes for sharp and flat (originally, -is and -es) so presumably a suffix for naturals would need that too. If we continue down that path, is there not a risk that, eventually, source code written in one localisation will become hard (harder?) to understand in another? And of course either the present syntax would need to be preserved as an option for compatibility, or convert-ly would need to impose the new syntax. <gentle irony>Perhaps we could have translate-ly to translate lilypond source between localisations? </gentle irony> This thread is making me a bit uneasy. Genesis 11:1-9 applies. _______________________________________________ bug-lilypond mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-lilypond
