Re: Issue 755 in lilypond: SVG backend improvements

2010-01-24 Thread lilypond
Updates: Status: Verified Comment #3 on issue 755 by v.villenave: SVG backend improvements http://code.google.com/p/lilypond/issues/detail?id=755 ... Aand Verified. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this i

Re: Issue 755 in lilypond: SVG backend improvements

2010-01-02 Thread lilypond
Updates: Status: Fixed Owner: pnorcks Labels: fixed_2_13_4 Comment #2 on issue 755 by pnorcks: SVG backend improvements http://code.google.com/p/lilypond/issues/detail?id=755 All of the above problems were fixed before 2.13.4 was released, so I'm going to close this is

Issue 755 in lilypond: SVG backend improvements

2009-05-26 Thread codesite-noreply
Comment #1 on issue 755 by pnorcks: SVG backend improvements http://code.google.com/p/lilypond/issues/detail?id=755 You can find the latest status of the SVG backend here: http://wiki.lilynet.net/index.php/SVG_backend -- You received this message because you are listed in the owner or CC field

Issue 755 in lilypond: SVG backend improvements

2009-02-28 Thread codesite-noreply
Status: Accepted Owner: v.villenave Labels: Type-Defect Priority-Medium OpSys-All New issue 755 by v.villenave: SVG backend improvements http://code.google.com/p/lilypond/issues/detail?id=755 Greetings, I'm opening this issue to gather reports about SVG export problems and ideas on how to improv