lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: MEI


From: Kevin Tough
Subject: Re: MEI
Date: Sat, 11 Jan 2014 07:40:19 +0100

>From a Fringe Coder,

I like Vim (text editor). I like to code with minimal but descriptive
syntax(ie. Visual Basic). XML code for web-applications I find bloated
and working with it is ugly. If MusicXML is guided by the right people
and does become/is a definitive standard that can support the keywords
and other particulars of lilypond code, then this might be a great
opportunity for the lilypond community.

>From a very satisfied lilypond user, go lilypond go!

Namaste,
Kevin Tough 

On Fri, 2014-01-10 at 10:46 +0100, Urs Liska wrote:
> I think this is important also for us:
> http://www.sibeliusblog.com/news/mei-plug-in-released-for-sibelius/
> 
> MEI is an important initiative for standardizing the encoding of
> music, with particular interest in encoding every aspect of a
> composition and its sources. I think this will be an important
> foundation for future music editing, and if even Sibelius starts to
> support it, we should keep this in our view.
> 
> I think if we're continuing our way for ly2musicxml this will become
> feasible.
> I would _love_ to see LilyPond as an engraving tool for MEI based
> workflows, and this will only be possible with true 2way conversion.
> 
> Actually I just got a message that someone at Edirom (www.edirom.de)
> has plans to create a MEI-to-LilyPond converter one day, and I told
> him about our current state of affairs (just started MusicXML export),
> and strongly encouranged him to get in touch with us instead of trying
> alone.
> This is to say that there is potential to interest academic
> institutions in this, which would be a wonderful thing.
> 
> Best
> Urs
> 
> -- 
> Urs Liska
> www.openlilylib.org
> _______________________________________________
> lilypond-user mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/lilypond-user





reply via email to

[Prev in Thread] Current Thread [Next in Thread]