Re: ly: updates to hel-arabic.ly (issue 349810043 by pkxgnugi...@runbox.com)
Hassan, I'm having a little bit of difficulty following the thread because I can't seem to find the hel-arabic.ly file you're working on. Could you please point me to the file so I can play with it? Thank you in advance Adam Good On Mon, Dec 17, 2018 at 12:38 PM Hans Åberg wrote: > > > > On 17 Dec 2018, at 15:35, pkxgnugi...@runbox.com wrote: > > > >> FYI, Adam Good expressed interest updating the Arabic and Persian > > files for > >> LilyPond [1]. I have sent him a file with maqam from the site [2]. > > > >> 1. > > https://lists.gnu.org/archive/html/lilypond-devel/2018-11/msg00105.html > >> 2. https://www.maqamworld.com/en/ > > > > Turkish/Persian Maqams and are very different to Arabic Maqams so cannot > > - according to Hassan - be compared. > > Note the difference in spelling: Turkish makam and Arabic maqam. And > Persian dastgah. The site [2] above is of the Arabic maqam. I made a file > for that in E53 with two commas for the microtones, using Graham Breed > regular.ly, and Helmholtz-Ellis accidentals, cf. [3]. The Arabic maqam > simply use a different set of accidental glyphs, two missing in the > traditional system, the ones with arrows at [2]. > > It would be good if you listen to the microtonal pitches of the MIDI at > [3], telling if they sound fine. > > 3. https://lists.gnu.org/archive/html/lilypond-user/2016-02/msg00607.html > > > > ___ > lilypond-devel mailing list > lilypond-devel@gnu.org > https://lists.gnu.org/mailman/listinfo/lilypond-devel > ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: ly: updates to hel-arabic.ly (issue 349810043 by pkxgnugi...@runbox.com)
> On 17 Dec 2018, at 15:35, pkxgnugi...@runbox.com wrote: > >> FYI, Adam Good expressed interest updating the Arabic and Persian > files for >> LilyPond [1]. I have sent him a file with maqam from the site [2]. > >> 1. > https://lists.gnu.org/archive/html/lilypond-devel/2018-11/msg00105.html >> 2. https://www.maqamworld.com/en/ > > Turkish/Persian Maqams and are very different to Arabic Maqams so cannot > - according to Hassan - be compared. Note the difference in spelling: Turkish makam and Arabic maqam. And Persian dastgah. The site [2] above is of the Arabic maqam. I made a file for that in E53 with two commas for the microtones, using Graham Breed regular.ly, and Helmholtz-Ellis accidentals, cf. [3]. The Arabic maqam simply use a different set of accidental glyphs, two missing in the traditional system, the ones with arrows at [2]. It would be good if you listen to the microtonal pitches of the MIDI at [3], telling if they sound fine. 3. https://lists.gnu.org/archive/html/lilypond-user/2016-02/msg00607.html ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: ly: updates to hel-arabic.ly (issue 349810043 by pkxgnugi...@runbox.com)
On 2018/12/13 17:28:50, haberg-1_telia.com wrote: > On 12 Dec 2018, at 09:55, mailto:lilyp...@maltemeyn.de wrote: > > I don’t know anything about arabic music but there are some changes that > look strange to me. FYI, Adam Good expressed interest updating the Arabic and Persian files for LilyPond [1]. I have sent him a file with maqam from the site [2]. 1. https://lists.gnu.org/archive/html/lilypond-devel/2018-11/msg00105.html 2. https://www.maqamworld.com/en/ Turkish/Persian Maqams and are very different to Arabic Maqams so cannot - according to Hassan - be compared. James https://codereview.appspot.com/349810043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GUB lilypond build fails
Werner LEMBERG writes: >> So it would be really _urgent_ to get GUB advanced to a recent >> version of Python 2 in all supported platforms > > Yes. > >> (and I think we can delist the PPC platform support by now): > > What's exactly the reason for this? Considerable resources in compilation and maintenance time without an obvious user? >> But at least PPC seems reasonably safe to retire, and possibly >> FreeBSD if it helps. > > AFAIK, it doesn't help since the requirements are the same. Whoever does the human GUB work (in this case moving Python to newer versions) gets to decide this I guess. Whoever does it is in my book free to decide to drop it after looking at it as thoroughly or casually as they consider fit. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GUB lilypond build fails
> So it would be really _urgent_ to get GUB advanced to a recent > version of Python 2 in all supported platforms Yes. > (and I think we can delist the PPC platform support by now): What's exactly the reason for this? > But at least PPC seems reasonably safe to retire, and possibly > FreeBSD if it helps. AFAIK, it doesn't help since the requirements are the same. Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GUB lilypond build fails
Andrew Bernard writes: > Hi All, > > I am new to lilypond dev. work. My intention may be naive, but I am wanting > to do the work to uplift gub and lilypond to python 3. Am I premature, or > foolish, or misguided? I did have some encouraging email about this > previously, but I just wanted to check before I dive in and spend large > amounts of time, especially re GUB. I have yesterday asked Masamichi-san to take a look at our current GUB problems but it would appear that Werner found and fixed the source of the current roadblock. Now it sounded like Masamichi-san was currently rather short of time for this, so it would make sense that now, since the immediate problem appears to be solved, you take a look at this instead with a perspective of a Python 3 migration eventually. So I did some "git blame" searching and it would appear that the Python 2.5 "ism" was introduced with commit commit 7b07440da921d979ab492fd284b6198152a8020c Author: Alexander Myltsev AuthorDate: Thu Jun 2 11:19:07 2016 +0300 Commit: James Lowe CommitDate: Sat Jun 16 10:59:08 2018 +0100 musicxml2ly: handle hidden time signatures. Now I don't really feel that we can indeed pass any blame for not being aware of having to use syntax for an ancient rather than an antique version of Python. And we apparently don't have the manpower in place to figure out what went wrong: this put our release process to a halt for almost half a year. So it would be really _urgent_ to get GUB advanced to a recent version of Python 2 in all supported platforms (and I think we can delist the PPC platform support by now): the current Python 2 requirement is obvious, the Python 2.4 requirement not. Moving to a current Python 2 version should be doable without changing the LilyPond source code: that's a pure GUB job, though one that might be bothersome on some platforms. Decommissioning the PPC platforms would likely make this easier, and I don't think we really have active users there. Masamichi-san also suggested stopping FreeBSD support (I don't know if there is much of an indication the binary installation from us is used rather than compiling themselves, and supposedly they can run Linux binaries though the runtime environment may be troublesome) and Windows 32-bit support. I am not sure whether there aren't people running 32-bit Windows binaries in VMs though. But at least PPC seems reasonably safe to retire, and possibly FreeBSD if it helps. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
