Updates:
Status: Verified
Comment #6 on issue 905 by philehol...@googlemail.com: LilyPond should
accept UTF-8 BOM signatures even if preceded with other chars
http://code.google.com/p/lilypond/issues/detail?id=905
(No comment was entered for this change.)
Comment #4 on issue 905 by brownian.box: LilyPond should accept UTF-8 BOM
signatures even if preceded with other chars
http://code.google.com/p/lilypond/issues/detail?id=905
Should be fixed_2_15_10 or something else?
$ LANG=C lilypond test.ly
GNU LilyPond 2.15.9
Processing `test.ly'
Updates:
Status: Fixed
Labels: -Patch-review fixed_2_15_9
Comment #3 on issue 905 by reinhold...@gmail.com: LilyPond should accept
UTF-8 BOM signatures even if preceded with other chars
http://code.google.com/p/lilypond/issues/detail?id=905
Pushed as commit
Updates:
Labels: -Patch-new Patch-review
Comment #2 on issue 905 by pkx1...@gmail.com: LilyPond should accept UTF-8
BOM signatures even if preceded with other chars
http://code.google.com/p/lilypond/issues/detail?id=905
passes make and reg tests
Updates:
Status: Started
Owner: reinhold...@gmail.com
Labels: Patch-new
Comment #1 on issue 905 by reinhold...@gmail.com: LilyPond should accept
UTF-8 BOM signatures even if preceded with other chars
http://code.google.com/p/lilypond/issues/detail?id=905
Patch up for
Status: Accepted
Owner: v.villenave
Labels: Type-Defect Priority-Medium Encoding
New issue 905 by v.villenave: LilyPond should accept UTF-8 BOM signatures
even if preceded with other chars
http://code.google.com/p/lilypond/issues/detail?id=905
Currently, LilyPond fails to parse UTF-8 files
