Re: Remove arabic.ly from common note name languages. (issue2755041)

[Valentin Villenave]

On Wed, Oct 27, 2010 at 5:10 PM, Ian Hulin <address@hidden> wrote:
> I like what you've done for ease of setting LilyPond's  expectations as
> to what it sees to name the notes of a scale (\language "catalan") or
> whatever.

Uh... Thanks?
(I had to re-read your sentence a few times to understand it, but
maybe I'm just tired :-)

> By splitting out arabic.ly from the valid list for language scale names,
> you open up the possibility of another similar function
> \octaveSteps, with a default of "cpp" to specify twelve divisions of the
> octave with eight notes used as the most significant.  The
> initialization code could have the setting cpp as its default value, and
> you could have
> \octaveSteps "arabic"
> \octaveSteps "maqam"
> \octaveSteps "kalyaniraga"  etc.
>
> or possibly call it \octaveDivisions.

Very interesting. From what I understand, this meets what I was trying
to do when renaming "Non-Western note names and accidentals" into
"Non-Western notations and tunings"; or doesn't it?

> Although this may not be possible in time for 2.14, you may want to
> think about organizing the docs to allow for this in the future.

I'm not sure that we currently have enough material to elaborate on
non-CPP stuff just yet. (And for the same reason, I'm not sure that we
should refer to "standard" note names as CPP note names, as Hans
suggested. At least, I'm not sure how to do that in a way that
wouldn't be potentially confusing to users.)
However, on a long-term perspective, it most certainly will become
quite interesting.

Cheers,
Valentin.