Comment #3 on issue 2889 by [email protected]: Bad unicode char value in error message
http://code.google.com/p/lilypond/issues/detail?id=2889

With the patch you now get

Processing `/home/nick/lilypond/examples/test.ly'
Parsing...
Interpreting music...
Preprocessing graphical objects...
warning: no glyph for character U+2E3A in font `/usr/local/share/lilypond/2.17.1/fonts/otf/CenturySchL-Roma.otf'
Finding the ideal number of pages...
[...]



Reply via email to