If you create a dotted chord with tremolo then export to lilypond, lilypond will refuse to compile it because of bad syntax. If you put clefs in the middle of a score lilypond exports also fail. Reproducible: Always Steps to Reproduce: 1. create the dotted tremolo chord or clef 2. export to lilypond 3. run "lilypond my-export.ly" will post patches shortly...
Created attachment 325942 [details] failing example Here is an example of a file that will fail when exported to lilypond markup.
Created attachment 325944 [details, diff] patch to fix bad clef exporting
Created attachment 325946 [details, diff] patch to fix bad tremolo exporting
disclaimer: these patches haven't been validated by upstream, and I've only had a chance to do minimal testing up till now. At least the code only touches parts that are run for lilypond exports, so the rest of the program will run the same way.
Created attachment 325966 [details, diff] patch to fix bad clef exporting v2 found a bug while testing more complex scores. v2 of this patch exports all sample scores perfectly.
(In reply to comment #5) > Created attachment 325966 [details, diff] [details, diff] > patch to fix bad clef exporting v2 > > found a bug while testing more complex scores. v2 of this patch exports all > sample scores perfectly. Did you try to contact upstream about your patches?
(In reply to comment #6) > Did you try to contact upstream about your patches? yes, never got an answer. http://mailman.tu-chemnitz.de/pipermail/nted-user/2012-October/000612.html
(In reply to comment #7) > (In reply to comment #6) > > Did you try to contact upstream about your patches? > > yes, never got an answer. > http://mailman.tu-chemnitz.de/pipermail/nted-user/2012-October/000612.html I am pretty sure upstream is 'dead' as they haven't released anything in years. In any case, I can't comment on the patch as I've no idea how this package works internally, so if it works for you, I will go ahead and apply it
(In reply to comment #8) > I am pretty sure upstream is 'dead' as they haven't released anything in > years. In any case, I can't comment on the patch as I've no idea how this > package works internally, so if it works for you, I will go ahead and apply > it I use this package a lot. The patches have been holding up so far. If there is a place you can add me as a contact so I can at least get notification of future bug reports please do so. (I like to maintain things I submit ;)
Yeah I can add you as maintainer on metadata.xml so all bugs are assigned to you. You can contact me if you have proposed fixes for the bugs. Thanks a lot :)
Ok, then please remove me as maintainer.
+*nted-1.10.18-r1 (09 Nov 2012) + + 09 Nov 2012; Markos Chandras <hwoarang@gentoo.org> + +files/nted-1.10.18-lilypond.patch, +nted-1.10.18-r1.ebuild, metadata.xml: + Add patch for fixing invalid lilypond export markup. Thanks to Christopher + Harvey <chris@basementcode.com>. Bug #437540. Adding him as proxy maintainer +