Could someone clarify: while hel-arabic.ly has this line that includes arabic.ly , what are they getting out of this? Some more key signatures and keyAlterationOrder?
Should all key signatures for the various maqams simply go only into arabic.ly ? Adam On Thu, Jan 12, 2023 at 4:11 AM Mats Bengtsson <matsboxergr...@gmail.com> wrote: > Please note that the proposed new version of hel-arabic.ly internally > contain a line that includes arabic.ly, which means that the end user > only has to do > > \include "hel-arabic.ly" > > just as before. Hopefully this resolves your concern. > > /Mats > > On 2023-01-11 16:02, Werner LEMBERG wrote: > > > >> The other modifications are useless, they simply make hel-arabic > >> dependent on arabic.ly. But hel-arabic.ly is supposed to be an > >> independent file from other ly files. > > This doesn't make sense. `hel-arabic.ly` is part of the LilyPond core > > files. If someone uses a recent version of LilyPond, both > > `hel-arabic.ly` and `arabic.ly` are *always* present. *Of course* it > > should share the code with `arabic.ly`! Our goal is to improve > > maintainability, and avoiding duplicated code is definitely such an > > improvement. > > > > > > Werner > > > > > >
