Re: Reasons why a LilyPond-to-MEI conversion should be developed

2015-10-24 Thread David Kastrup
Paul Morris writes: > I think the same considerations that apply for MusicXML also apply for > MEI. See the discussions about the Google summer of code project from > last spring. > > Namely, LilyPond’s internal scheme data structure is a good target for > import and export (better than LilyPond

Re: Feature Requests

2015-10-24 Thread David Kastrup
Simon Albrecht writes: > On 23.10.2015 20:31, Bernardo Barros wrote: >> Something I requested many years ago was the support for quarter-tone >> tablatures notation, which seems to work but is actually buggy at the >> moment, it generates wrong tablatures in strings with quarter-tones >> alterati

Re: Reasons why a LilyPond-to-MEI conversion should be developed

2015-10-24 Thread Richard Shann
On Sat, 2015-10-24 at 01:39 +0200, Simon Albrecht wrote: > e.g. if LilyPond should consume > > MEI > > Interesting thought. I should be surprised if MEI were to consent in > granting LilyPond this honour (as which I’d consider it). I think what was meant was "the lilypond executable should parse

Re: Reasons why a LilyPond-to-MEI conversion should be developed

2015-10-24 Thread Urs Liska
Am 24. Oktober 2015 10:05:55 MESZ, schrieb Richard Shann : >On Sat, 2015-10-24 at 01:39 +0200, Simon Albrecht wrote: >> e.g. if LilyPond should consume >> > MEI >> >> Interesting thought. I should be surprised if MEI were to consent in >> granting LilyPond this honour (as which I’d consider it

Re: Reasons why a LilyPond-to-MEI conversion should be developed

2015-10-24 Thread Urs Liska
Am 24.10.2015 um 08:04 schrieb Andrew Bernard: > While MEI may be ‘universal’ in intent, it is just an open source project. But a project backed by a very distributed, connected and publicly funded academic community. >Since lilypond is open source, it would make sense for the open source >comm

Re: Reasons why a LilyPond-to-MEI conversion should be developed

2015-10-24 Thread Urs Liska
Am 24.10.2015 um 03:18 schrieb Paul Morris: > I think the same considerations that apply for MusicXML also apply for MEI. > See the discussions about the Google summer of code project from last spring. > > > Namely, LilyPond’s internal scheme data structure is a good target for import > and

Re: My finances for working on LilyPond

2015-10-24 Thread Federico Bruni
Il giorno ven 23 ott 2015 alle 15:19, Federico Bruni ha scritto: I agree, but I think that we can easily improve the situation. A few simple ideas: 1) DOWNLOAD PAGE What's the most viewed page in the website (excluding the home)? Probably the download page: http://lilypond.org/website/downlo

Re: Reasons why a LilyPond-to-MEI conversion should be developed

2015-10-24 Thread Simon Albrecht
On 24.10.2015 03:18, Paul Morris wrote: LilyPond’s internal scheme data structure is a good target for import and export Or even more so the music stream internally used by LilyPond after Erik Sandberg’s work. IIUC there is some doubt as to how complete the features he describes in his master

Re: Reasons why a LilyPond-to-MEI conversion should be developed

2015-10-24 Thread David Kastrup
Simon Albrecht writes: > On 24.10.2015 03:18, Paul Morris wrote: >> LilyPond’s internal scheme data structure is a good target for >> import and export > > Or even more so the music stream internally used by LilyPond after > Erik Sandberg’s work. IIUC there is some doubt as to how complete the >

Re: Reasons why a LilyPond-to-MEI conversion should be developed

2015-10-24 Thread Noeck
Hi Urs, possible advantages could be: a larger user base and maybe contributions from more (academic/professional/knowledgeable) people to the engraving quality of LilyPond. Offering a high quality engraving solution for an already existing community. And other synergy effects and perhaps funding.

Re: Reasons why a LilyPond-to-MEI conversion should be developed

2015-10-24 Thread Simon Albrecht
On 24.10.2015 16:54, David Kastrup wrote: They are not in LilyPond. There is no tangible or recognizable thing like a "music stream" […] chances are rather slim that parts of the code could be usefully adapted to work with LilyPond these days. What a pity, it would have seemed a nice startin

Auto-generated code, (was Re: Reasons why a LilyPond-to-MEI conversion should be developed)

2015-10-24 Thread Richard Shann
On Sat, 2015-10-24 at 22:11 +0200, Noeck wrote: > I guess MEI is rather less readable > and auto-generated ly code likely, too (therefore I don't use > Denemo). Actually, you are not restricted to using Denemo's auto-generated code when using Denemo. Denemo is essentially a program to enable you

Re: Auto-generated code, (was Re: Reasons why a LilyPond-to-MEI conversion should be developed)

2015-10-24 Thread Noeck
Dear Richard, first I want to emphasize that this was not against you or Denemo, just a connection between my favoured workflows and the tools I use. I don't understand 'traverse the staffs' in your sentence: > It *does* provide a > default LilyPond output, but you can just as easily traverse th