>> For single-byte encodings, you are correct. However, the
>> probability is *much* higher if you consider legacy two-byte
>> encodings for CJK scripts.
>
> The probability of people accidentally writing two-byte encodings for
> CJK scripts in an ASCII-based programming language and being totally
> surprised by coding issues is not all that high.
??? I thought we take about strings like lyrics.
> I also consider it much much more likely that somebody unused to
> coding problems tries getting just a composer's name right in a
> Latin script is higher than with Chinese letters. It is much easier
> to make your computer produce a diacritical Latin letter foreign to
> you (like with using a Compose key) than produce a Chinese letter.
>
> So I don't really see the point in giving up before trying.
Again, as mentioned previously in another mail in this thread: If
Pango reports an invalid UTF-8 sequence (as it already does), I'm all
for it to make it more visible. What kind of improvement do you
envision?
Werner
_______________________________________________
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
