Re: Issue 887 in lilypond: Non-ASCII characters in textedit URIs should be percent-encoded

[lilypond]

Comment #28 on issue 887 by pnorcks: Non-ASCII characters in textedit URIs  
should be percent-encoded
http://code.google.com/p/lilypond/issues/detail?id=887

They *could* be encoded in the same way, but since "a%cc%81" and "%c3%a1"  
are both
valid ways of representing "á" in UTF-8, everything should be okay.

Since my solution is to escape every non-ASCII character byte-by-byte,  
according to
the XDG file URI spec  
(http://www.freedesktop.org/wiki/Specifications/file-uri-spec),
this means Mac OS X is representing the same character, "á", in two  
different ways in
the same path/file name!!

I consider this to be a problem with Mac OS X, in that it's inconsistent  
with its
representation of characters.

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings