Re: Issue 2159 in lilypond: Patch: lexer.ll: Warn about non-UTF-8 characters

[lilypond]

Comment #8 on issue 2159 by address@hidden: Patch: lexer.ll: Warn about  
non-UTF-8 characters
http://code.google.com/p/lilypond/issues/detail?id=2159

As I said: the problem is that LilyPond is not able to deal with UTF-8  
_elsewhere_.  You'll get programming errors whenever there is any kind of  
diagnostic occuring in a column after a non-UTF-8 character.  You'll get  
non-UTF-8 output thrown at any terminal listening to LilyPond.  Sure, I can  
try having the UTF-8 warning messages avoid giving the right column for the  
problem.  But I can't remove all column information for LilyPond  
diagnostics everywhere.

Or put differently: is it really _my_ job to make LilyPond safe against  
non-UTF-8 input elsewhere when it has not been so before, and the whole  
_point_ of the patch is to keep the user from using non-UTF-8?  That does  
not make all too much sense, does it?

And when we just accept non-UTF-8 strings without aborting, it means that  
_user_ _code_ must be prepared to deal with invalid UTF-8 sequences as well.