On Tue, Jan 21, 2020 at 7:04 AM Urs Liska <li...@openlilylib.org> wrote: > > Am Dienstag, den 21.01.2020, 07:03 -0600 schrieb David Nalesnik: > > On Tue, Jan 21, 2020 at 3:17 AM Urs Liska <li...@openlilylib.org> > > wrote: > > > Am Dienstag, den 21.01.2020, 10:09 +0100 schrieb Jacques Menu: > > > > Hello folks, > > > > > > > > MEI has been mentionned at the Salzburg conference as more and > > > > more > > > > used in the academic circles. > > > > > > > > Jan-Peter said that an MEI to Lily translator would be useful, > > > > and > > > > RISM’s Laurent Pugin presented Verovio ( > > > > https://www.verovio.org/index.xhtml), which features an XSL/XSLT > > > > such > > > > translator named MEIler (MEI Lilypond Engraving Refinement, > > > > https://github.com/rettinghaus/meiler). > > > > > > > > > > MEIler is independent from Verovio, and developed by Klaus > > > Rettinghaus > > > privately. > > > > > > > My questions are: do you feel the need for a MEI to LilyPond > > > > translator, and has anyone experience with MEIler? > > > > > > a) > > > There is a *strong* need for a reliable and fast translator from > > > MEI to > > > LilyPond (and vice versa) to make LilyPond an acceptable tool in > > > the > > > digital edition community. > > > > You can of course take a more circuitous route with MusicXML as an > > intermediary. For MusicXML to MEI there exist packages like this: > > https://github.com/gburlet/musicxml-mei-conversion > > But the issue right now is *from* MEI *to* LilyPond. > > Urs >
Should have written "MEI to MusicXML to LilyPond". Of course, just a temporary step. (And, BTW, that package I linked to is bi-directional but looks horribly out-of-date...) David
