Re: Incorrect point-and-click URIs of files with non-ASCII content on Windows

[Bertalan Fodor (LilyPondTool)]

>   3) UTF-8 characters.  In UTF-8 locales, terminals need to know about
>   the byte offset, so I am using the character count to specify this
>   offset.  An example would be "3:11:10".
>
> The third case is arguably misleading, so maybe it should be changed
> to use the "3:10:10" instead.  I am okay with either format.  If we
> want to use "3:10:10" instead, then an additional parameter would be
> needed to calculate the byte offset.
>   
I hardly believe anyone or anything should care about byte offset. 
LilyPond source files contain UTF-8 characters and not bytes! If a 
terminal/editor doesn't support UTF-8 character streams, than the 
terminal/editor should be fixed.

Bert