On Sat, Jan 14, 2023 at 4:00 AM Hans Åberg <haber...@telia.com> wrote:
> > > On 14 Jan 2023, at 08:06, Werner LEMBERG <w...@gnu.org> wrote: > > > >>> 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 removed in the release after. > > If there are no compatibility issues, perhaps turkish-makam.ly < > http://turkish-makam.ly/> might be renamed makam.ly <http://makam.ly/>. > Adam Good might give his view. > Hans and Werner, For a couple reasons, I deliberately used the name turkish-makam.ly to make a distinction and clarity between the Arabic and Turkish varieties of (respectively) maqam and makam theory and notation systems. Also I do have ideas for another .ly file in the future turkish-usul.ly which will give defintions for rhythmic aspects of Turkish classical music. "Usul" is basically the rhythmic equivalent in study and theory to "makam". The two files would conveniently live right next to one another in the ly directory. And the usul file will be large enough that I'd much rather not use that material in the turkish-makam file. Though I'm forever grateful for the original makam.ly include file. I'd much prefer to use the name turkish-makam.ly and could easily see makam.ly simply disappear for the next release. turkish-makam is a huge upgrade. While we're on the topic of naming, and I should pick this up in the other thread, I find it's a great idea to make the names as descriptive and specific as possible. Ideas, for example: turkish-makam.ly arabic-maqam.ly persian-dastgah.ly arabic-rhythms.ly (I forget the Arabic term...iqa?) balkan-keysigs.ly balkan-rhythms.ly greek-byzantine.ly Adam
