I just noticed that when I accidentally saved my swedish lyrics in a
non-utf8 format (most likely windows codepage cp1252 or somesuch) I got a
few screenfuls of
programming error: FT_Get_Glyph_Name returns error
continuing, cross fingers
programming error: Glyph has no name, but font supports glyph naming.
Skipping glyph.
continuing, cross fingers
It might be beneficial to provide a better error message (if the situation
is possible to detect, that is)
regards,
Simon
PS. attaching a small demo file with bad encoding and output
PPS. Another glitch is that the \version statement does not seem to be
recognised..
\version "2.9.9"
fooWords = \lyricmode { å ä ö aa }
notes = \relative c' {
c c c c
}
\score {
<<
\new Voice = "sopranos" { \notes }
\context Lyrics = sopranos \lyricsto sopranos \fooWords
>>
}
GNU LilyPond 2.9.9
Processing `encodingbug.ly'
Parsing...
encodingbug.ly: 0: warning: no \version statement found, please add
\version "2.9.9"
for future compatibility
Interpreting music... [1]
Preprocessing graphical objects...
programming error: FT_Get_Glyph_Name returns error
continuing, cross fingers
programming error: Glyph has no name, but font supports glyph naming. Skipping
glyph.
continuing, cross fingers
programming error: FT_Get_Glyph_Name returns error
continuing, cross fingers
programming error: Glyph has no name, but font supports glyph naming. Skipping
glyph.
continuing, cross fingers
programming error: FT_Get_Glyph_Name returns error
continuing, cross fingers
programming error: Glyph has no name, but font supports glyph naming. Skipping
glyph.
continuing, cross fingers
Calculating line breaks... [2]
Drawing systems...
Calculating page breaks...
Layout output to `encodingbug.ps'...
Converting to `encodingbug.pdf'...
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
