Re: Issue 665 in lilypond: Request: MusicXML backend

2011-08-24 Thread lilypond
Comment #18 on issue 665 by fedel...@gmail.com: Request: MusicXML backend http://code.google.com/p/lilypond/issues/detail?id=665 A recent discussion about this feature request: http://lists.gnu.org/archive/html/lilypond-user/2011-08/msg00435.html I offer 50 euro

Re: Issue 665 in lilypond: Request: MusicXML backend

2011-07-21 Thread lilypond
Comment #17 on issue 665 by lilyli...@googlemail.com: Request: MusicXML backend http://code.google.com/p/lilypond/issues/detail?id=665 Does anybody know whether the old bounty offers are still valid? If yes, they would by now up sum up to $600 (counting everything mentioned in this issue

Re: Issue 665 in lilypond: Request: MusicXML backend

2011-06-04 Thread lilypond
Comment #16 on issue 665 by kie...@alumni.rice.edu: Request: MusicXML backend http://code.google.com/p/lilypond/issues/detail?id=665 $100 here. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 665 in lilypond: Request: MusicXML backend

2011-01-01 Thread lilypond
Comment #13 on issue 665 by rogerdpack: Request: MusicXML backend http://code.google.com/p/lilypond/issues/detail?id=665 $150 bounty from me. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Issue 665 in lilypond: Request: MusicXML backend

2010-11-27 Thread Reinhold Kainhofer
Am Freitag 26 November 2010, um 22:51:59 schrieb lilyp...@googlecode.com: Comment #12 on issue 665 by aleksandr.andreev: Request: MusicXML backend http://code.google.com/p/lilypond/issues/detail?id=665 I'm working on a script that takes the raw Lilypond source and converts it to XML. If

Re: Issue 665 in lilypond: Request: MusicXML backend

2010-11-26 Thread lilypond
Comment #12 on issue 665 by aleksandr.andreev: Request: MusicXML backend http://code.google.com/p/lilypond/issues/detail?id=665 I'm working on a script that takes the raw Lilypond source and converts it to XML. If anyone is interested in collaborating, shoot me an email.

Re: Issue 665 in lilypond: Request: MusicXML backend

2010-02-18 Thread lilypond
Comment #9 on issue 665 by brownian.box: Request: MusicXML backend http://code.google.com/p/lilypond/issues/detail?id=665 I'll happily make it 300, by the way. Here in Kyiv, Ukraine is preferable option though, but others are possible, i hope. -- You received this message because you are

Re: Issue 665 in lilypond: Request: MusicXML backend

2010-02-18 Thread lilypond
Comment #10 on issue 665 by reinhold.kainhofer: Request: MusicXML backend http://code.google.com/p/lilypond/issues/detail?id=665 There have been some discussions on lilypond-devel and lilypond-user. Here is a short excerpt from one of my mails, outlining how such a MusicXML backend

Re: Issue 665 in lilypond: Request: MusicXML backend

2010-02-18 Thread lilypond
Updates: Owner: --- Labels: -Priority-Postponed Priority-Low musicxml Comment #11 on issue 665 by v.villenave: Request: MusicXML backend http://code.google.com/p/lilypond/issues/detail?id=665 What about implementing the pure-music-stream export as a first step? Can't be (much)

Issue 665 in lilypond: Request: MusicXML backend

2009-04-10 Thread codesite-noreply
Comment #8 on issue 665 by hopkin...@ldschurch.org: Request: MusicXML backend http://code.google.com/p/lilypond/issues/detail?id=665 My organization is looking at possibly using LilyPond, especially for its nice music typesetting and Unicode text support. However, we would absolutely need

Issue 665 in lilypond: Request: MusicXML backend

2009-03-25 Thread codesite-noreply
Comment #7 on issue 665 by v.villenave: Request: MusicXML backend http://code.google.com/p/lilypond/issues/detail?id=665 Yet some unexpected news from Hu Haipeng: apparently, the professor who's in charge of BrailleMuse has gone missing lately, and since it's an online tool the source

Issue 665 in lilypond: Request: MusicXML backend

2009-03-02 Thread codesite-noreply
Comment #6 on issue 665 by v.villenave: Request: MusicXML backend http://code.google.com/p/lilypond/issues/detail?id=665 New comment from Hu Haipeng: The best way for you all is, to make a MusicXml backend. This feature has the following three advantages, two of which can't be approached by

Issue 665 in lilypond: Request: MusicXML backend

2008-11-22 Thread codesite-noreply
Comment #5 on issue 665 by v.villenave: Request: MusicXML backend http://code.google.com/p/lilypond/issues/detail?id=665 New comment from Ralph Little: http://lists.gnu.org/archive/html/lilypond-devel/2008-11/msg00293.html I have been approached by a programmer who is interested in helping me

Issue 665 in lilypond: Request: MusicXML backend

2008-11-20 Thread codesite-noreply
Issue 665: Request: MusicXML backend http://code.google.com/p/lilypond/issues/detail?id=665 Comment #3 by v.villenave: Jonathan Kulp has offered a $100 bounty on -devel. Issue attribute updates: Labels: Bounty -- You received this message because you are listed in the owner or CC

Issue 665 in lilypond: Request: MusicXML backend

2008-08-24 Thread codesite-noreply
Issue 665: Request: MusicXML backend http://code.google.com/p/lilypond/issues/detail?id=665 Comment #1 by v.villenave: Since we have more requests about it, I'm accepting it and slightly bumping the prio. Issue attribute updates: Status: Accepted Labels: -Priority-Postponed

Re: Issue 665 in lilypond: Request: MusicXML backend

2008-08-24 Thread Han-Wen Nienhuys
Hi, Priorities for these types of changes (oodles of work) does not change depending on user interest. We can un-postpone it if someone comes along to volunteer the necessary work. On Sun, Aug 24, 2008 at 8:18 PM, [EMAIL PROTECTED] wrote: Issue 665: Request: MusicXML backend

Issue 665 in lilypond: Request: MusicXML backend

2008-08-21 Thread codesite-noreply
Issue 665: Request: MusicXML backend http://code.google.com/p/lilypond/issues/detail?id=665 New issue report by v.villenave: This feature has been proposed by Reinhold Kainhofer on -devel: http://lists.gnu.org/archive/html/lilypond-devel/2008-06/msg00129.html More recently, an user shared his