> I neglected to mention that in recent 2.13 versions, the warning > messages for invalid character encoding look like this: > > (process:1375): Pango-WARNING **: Invalid UTF-8 string passed to > pango_layout_set_text() > > These warnings are generated by Pango. > > Is this an improvement?
Yes, thanks. I assume that it is not possible to add the offending text string to the warning message since a Pango warning is not visible to lilypond... Perhaps it makes sense to add a UTF-8 checker to lilypond just for that. Werner _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user