Werner LEMBERG <w...@gnu.org> writes: >>> How will you discern intended and unintended input? Additionally, >>> due to FontConfig providing a fallback mechanism for missing >>> characters, you normally don't get warnings if you are getting a >>> `strange' letter. >> >> What about a "maybe error" message? Something like "you file >> doesn't use utf-8 encoding. For best results you may want to save >> your input encoded in utf-8, see Program Usage Manual chapter x >> section y for more information". > > If we get an invalid UTF-8 sequence, I'm all for it. But it is not > too difficult to not get invalid sequences but still have wrong > output.
Theoretically. But it is impossible to write just a single non-ASCII byte without hitting an invalid sequence since all non-ASCII bytes must be part of multi-byte sequences. Only combinations of non-ASCII bytes can form valid utf-8 sequences, and the probability of several of them being "just right" is not all that high. -- David Kastrup _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
