[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Issue 887 in lilypond: Non-ASCII characters in textedit URIs should
From: |
lilypond |
Subject: |
Re: Issue 887 in lilypond: Non-ASCII characters in textedit URIs should be percent-encoded |
Date: |
Sun, 07 Feb 2010 20:08:51 +0000 |
Comment #27 on issue 887 by harmathdenes: Non-ASCII characters in textedit
URIs should be percent-encoded
http://code.google.com/p/lilypond/issues/detail?id=887
Thanks for the fix! Now non-Latin-2 characters work correctly, e.g.
a/ő.ly -> a/%c5%91.ly
But non-ASCII characters in the path are still encoded differently from
those in the file
name, e.g.
á/á.ly -> a%cc%81/%c3%a1.ly
Couldn't they be encoded the same way?
--
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
- Re: Issue 887 in lilypond: Non-ASCII characters in textedit URIs should be percent-encoded, lilypond, 2010/02/05
- Message not available
- Re: Issue 887 in lilypond: Non-ASCII characters in textedit URIs should be percent-encoded,
lilypond <=
- Message not available
- Re: Issue 887 in lilypond: Non-ASCII characters in textedit URIs should be percent-encoded, lilypond, 2010/02/07
- Message not available
- Re: Issue 887 in lilypond: Non-ASCII characters in textedit URIs should be percent-encoded, lilypond, 2010/02/07
- Message not available
- Re: Issue 887 in lilypond: Non-ASCII characters in textedit URIs should be percent-encoded, lilypond, 2010/02/07
- Message not available
- Re: Issue 887 in lilypond: Non-ASCII characters in textedit URIs should be percent-encoded, lilypond, 2010/02/07
- Message not available
- Re: Issue 887 in lilypond: Non-ASCII characters in textedit URIs should be percent-encoded, lilypond, 2010/02/07