>> Too bad that `makam.ly` is essentially undocumented...
>
> From what I can see, makam.ly is the original faulty file, only
> there for backwards compatibility, which might be removed if there
> is no need for that.
We could make it become deprecated in the next release, to be
completely remo
Here is the current countdown report.
The next countdown will begin on January 16th.
A list of all merge requests can be found here:
https://gitlab.com/lilypond/lilypond/-/merge_requests?sort=label_priority
Push:
!1809 Let Paper_book use \layout rather than \paper for global markups -
D
> On 13 Jan 2023, at 19:03, Werner LEMBERG wrote:
>
>> [...] a possible future change could be, say,
>>
>> \include "arabic.ly"
>> \language "arabic-hel"
>>
>> but I don't see much benefit for that.
>
> Hmm, probably it *is* the way to go – this is exactly what is done in
> `makam.ly` and
> [...] a possible future change could be, say,
>
> \include "arabic.ly"
> \language "arabic-hel"
>
> but I don't see much benefit for that.
Hmm, probably it *is* the way to go – this is exactly what is done in
`makam.ly` and `turkish-makam.ly`. Too bad that `makam.ly` is
essentially undoc
> Now, obviously renaming it will break scores, [...]
It won't. Such a renaming could be done easily with `convert-ly`. I
just don't see a reason for doing that – and especially, I don't see a
alternative name for `hel-arabic.ly` that is really superior.
Werner
> The same holds for Arabic: As described in the documentation changes
> of MR !1783 you should say
>
> \include "arabic.ly"
>
> if you want Italian-based note names for inputting Arabic music, and
>
> \include "hel-arabic.ly"
>
> if you want English-based note names with customized, Ital
> But what is the point of this high-level interface? Surely,
> arabic.ly should be the obvious entry point.
It's similar to note name language support in LilyPond: We don't say
\include "language.ly"
Instead, we rather have
\include "deutsch.ly"
or
\include "italiano.ly"
The same ho
Le 10/01/2023 à 22:17, Jean Abou Samra a écrit :
In order to increase the bus factor, I would like to
nominate one or two other regulars as admins. If you
feel like it, please let me know.
Thanks to Mark Knoop for accepting this task. He is now a co-admin.
Best,
Jean
OpenPGP_signature
Des
On 2023-01-13 1:44 am, Werner LEMBERG wrote:
it seems like we could easily find a better name for this file, more
descriptive of its purpose and less related to the original author.
While this might be true, I don't think there is a pressing reason to
change the name of a high-level interface j
On Fri, Jan 13, 2023 at 10:44 AM Werner LEMBERG wrote:
> `hel-arabic.ly` exists since more
> than five years, and nobody has ever complained about the name, as far
> as I can remember.
>
Well yes. but.
Out of the users of that file, how many
a) would have noticed,
b) would be aware of our naming
> it seems like we could easily find a better name for this file, more
> descriptive of its purpose and less related to the original author.
While this might be true, I don't think there is a pressing reason to
change the name of a high-level interface just because three letters
of the name refe
On Fri, Jan 13, 2023 at 10:11 AM Aaron Hill
wrote:
> I have no idea what "hel" is supposed to be referring to
>
If I remember right, in a previous post Hassan had indicated "hel" to be a
shorthand for his name _H_assan _El_ Fatihi.
FWIW, I would have found it more natural to shorten the name as
Hello
I just answered the questions
I have no problem with including arabic.ly in hel-arabic.ly.
For me the subject can be closed
Best regard
Hassan EL FATIHI
Hassan,
> Question: Should all key signatures for the various maqams simply go
> only into arabic.ly ?
> Answer: All key signatures for the various maqams simply go only
> into hel-arabic.ly (if not modified, as recently proposed)
You are missing the point. Whether the signat
On 2023-01-13 12:23 am, Luca Fascione wrote:
Hassan,
it would help us enormously if you could share with us the reasoning
behind
these choices.
For example, you stated "All key signatures for maqams go in
hel-arabic.ly":
could you explain to us
why this is the better place for them, compared
Hassan,
it would help us enormously if you could share with us the reasoning behind
these choices.
For example, you stated "All key signatures for maqams go in hel-arabic.ly":
could you explain to us
why this is the better place for them, compared to arabic.ly?
This will provide some intuition to a
Hello
Answers to questions
Question : while hel-arabic.ly has this line that
includes arabic.ly , what are they getting out of this? Some more
key signatures and keyAlterationOrder?
answer: normally hel-arabic.ly doesn't need arabic.ly (if not modified, as
recently proposed)
Question: Shou
17 matches
Mail list logo
