Re: allowing \f and \F

[Graham Percival]

On Sat, Sep 15, 2012 at 10:25:17PM +0200, David Kastrup wrote:
> Graham Percival <address@hidden> writes:
> 
> > For example, what about my hated idea of splitting namespaces of
> > music fuctions and identifiers?  I'm not fond of perl, but
> > something like this is unambiguous:
> >
> >   $F = \markup { "Horn in F" }
> >   {
> >     c$F
> >   }
> 
> I don't want to differentiate between predefined and user-defined
> commands.

That's certainly a consistent view to take, but it might be worth
discussing that further at some point.  If there's a separate
namespace then I can't see any technical problems, and some users
may appreciate being able to define short strings like $a or $f
without any conflict with existing commands and keywords.

> > The remaining
> > question is whether to make $names case-sensitive or not -- or,
> > for that matter, whether to allow only ascii characters in $names
> > or whether to allow any utf-8 character.  Maybe non-native English
> > speakers would appreciate being able to name their music in their
> > native language.
> 
> You are aware that LilyPond allows _any_ utf-8 character outside of the
> ASCII page in strings, identifiers and note names already?

Obviously not.  I wonder how many non-English speakers are aware
of this -- do we have an example of this in the Learning or
Notation manuals?

- Graham