Re: Issue 887 in lilypond: PDF point-and-click URI links with special chars wrongly encoded depending on the OS

[lilypond]

Comment #11 on issue 887 by pnorcks: PDF point-and-click URI links with  
special chars wrongly encoded depending on the OS
http://code.google.com/p/lilypond/issues/detail?id=887

I now think there is a problem with both the URI encoding and the GUI  
interpreting
the URIs.

Using percent (%) escapes for the filename instead of octal escapes seems to
partially fix the problem.

For example, consider a file named "á.ly".  Ghostscript produces a textedit  
URI
encoded as "\303\241.ly".  Using Skim.app, clicking on the URI does  
nothing; the
LilyPond GUI is not opened, and no error message is produced.

If I change the encoding to "%C3%A1.ly", clicking on the URI open the  
LilyPond GUI,
but the file is not opened.  For this case, I suspect the GUI  
interpretation is to blame.

I'll be able to investigate this more next week.

--
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