Re: es means ees???

[Hans Aberg]

> On 7 Oct 2014, at 09:33, Richard Shann <address@hidden> wrote:
> 
> On Tue, 2014-10-07 at 11:04 +0900, Graham Percival wrote:
>> On Mon, Oct 06, 2014 at 01:41:30PM +0200, David Kastrup wrote:
>>> Richard Shann <address@hidden> writes:
>>> 
>>>> Here, instead of ees, is written es.
>>> 
>>> I read
>>> 
>>>    In Dutch, aes is contracted to as, but both forms are accepted in
>>>    LilyPond. Similarly, both es and ees are accepted. This also applies
>>>    to aeses / ases and eeses / eses. Sometimes only these contracted
>>>    names are defined in the corresponding language files.
>> 
>> Yes.  In case anybody was wondering, I deliberately moved the "as"
>> and "es" contractions from the tutorial into the NR ages ago.  For
>> people unfamiliar with that notation, it's easier to remember
>> "letter name plus -es or -is" rather than introducing all the
>> contractions.
> 
> That was a good idea I think. What is unfortunate is that the default
> includes these contractions, with hindsight it might have been better to
> have the default be the simplest set of names with those that wanted to
> use the contractions including a language specific file (e.g.
> nederlands).

The convention is same in Swedish, that is, “gess” and “ess”, so it is natural 
to use the default “ges” and “es".

> But this is a very minor thing, perhaps as a matter of
> style the ly directory code should avoid the contractions?

However, I found it convenient to switch to the English conventions, so I have 
mixture.

> This has a connection with the other thread about using the sharp and
> flat symbols - they should be in a language neutral file.

Another topic is to add postfix operators. Right now, each note, with 
accidental or not, must be given a new LilyPond name. With operators, that is 
not necessary. Especially when adding microtonal accidentals, the combinations 
multiply so heavily it is no longer practical to write them out as note names.