Werner LEMBERG <w...@gnu.org> writes: >>> But string handling is delegated to Pango... >> >> Not as far as I can see. String _typesetting_ is delegated to Pango. > > Ok. My knowledge of the code is too restricted. Does LilyPond itself > check the validity of UTF-8 somewhere? Otherwise, we could reuse code > from `gnulib', file `unistr/u8-check.c'.
Issue number: 5505090 (http://codereview.appspot.com/5505090) Issue description: lexer.ll: Warn about non-UTF-8 characters Making the warnings point to the exact bad byte rather than the enclosing construct would be nice. -- David Kastrup _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
