[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ET microtonal notation

From: Simon Albrecht
Subject: Re: ET microtonal notation
Date: Tue, 23 Feb 2016 23:15:31 +0100

On 23.02.2016 18:59, Hans Åberg wrote:

On 23 Feb 2016, at 18:43, Simon Albrecht <address@hidden> wrote:

On 23.02.2016 15:59, Hans Åberg wrote:
On 23 Feb 2016, at 15:11, David Kastrup <address@hidden> wrote:

Hans Åberg <address@hidden> writes:

It would be easy to make ET typesetting with correct MIDI, plus some,
if the LilyPond distribution included the files regular.ly,
definitions.ily, smufldata.ily plus the SMuFL font Bravura.
It was cc’ed Simon Albrecht, who on the LilyPond User list suggested that to 
post better suggestions on this list [1].
Please have a look at 
The current documentation would become obsolete. It would not be difficult to 
add a few files common ET’s.

The first file is mentioned here [2]. The others come from [3-4], also 
mentioned in that discussion.

1. http://lists.gnu.org/archive/html/lilypond-user/2016-02/msg00569.html
2. http://lists.gnu.org/archive/html/lilypond-user/2016-02/msg00627.html
3. http://www.openlilylib.org/
4. http://www.smufl.org/
Still, it’s up to anyone to guess this. And ‘regular.ly’ or ‘definitions.ily’ 
(really!) are quite commonplace filenames. I don’t know how many dozen files 
called ‘definitions.ily’ might be in OpenLilyLib.
I’ll send you them in private mail

There’s no point in that. Personally, I have no interest in Arabic music.

So I’m sorry, but speaking of a ‘rant’ is somewhat of an overstatement.
In the ly-user post of mine that you quoted I spoke of a ‘concise’ request. 
Perhaps you try and make one.
Just have the files and font included in the LilyPond distribution, as they 
seem to work.

‘They seem to work’ is not a criterion for inclusion in LilyPond. The question is if they meet standards of both notation and coding _and_ are of sufficiently general interest. And most importantly they will only be included in LilyPond if someone does the coding and documentation and uploads a patch, following the standard procedures. If no developer is interested in doing so, then it will not happen – that’s how LilyPond development works.

Best, Simon

reply via email to

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