Thanks. Is there a solution to the problem? It's happening in about 30%
of the unicode.
On 05/05/2013 11:15 PM, Nick Payne wrote:
On 06/05/13 00:46, Peter O'Doherty wrote:
\mark \markup { \char ##x1080B }
error:
programming error: FT_Get_Glyph_Name () error: invalid argument
continuing, cross fingers
programming error: Glyph has no name, but font supports glyph naming.
Skipping glyph U+1001080B, file
/home/peter/lilypond/usr/share/lilypond/current/fonts/otf/CenturySchL-Roma.otf
This means there is no such glyph in the corresponding font - and the
error message incorrectly pads the unicode value out to eight digits.
The current development version gives a much better warning in the log:
warning: no glyph for character U+1080B in font
`/usr/local/lilypond/usr/share/lilypond/current/fonts/otf/CenturySchL-Roma.otf'
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
--
//=============================
-> Peter O'Doherty
-> http://www.peterodoherty.net
-> m...@peterodoherty.net
//=============================
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
