Special characters and KLauncher

[Thiago Macieira]

Rafael Fernández López wrote:
>toEncoded() is just wrong (from Qt assistant):
>
>"The user info, path and fragment are all converted to UTF-8, and all
>non-ASCII characters are then percent encoded."
>
>non-ASCII characters are then percent encoded.
>
>That means that our special characters are killed down by this method
> and we just lose the ability of accessing those files.

Your comment makes no sense. toEncoded() works perfectly by 
percent-encoding all non-ASCII characters, as it should. That's done in 
the URL. If you want to access the file name pointed to by a file:/// 
URL, you should call localFile(). That will return the proper UTF-16 
encoded name that is used throughout Qt/KDE code.

But in URLs, everything is UTF-8. This is required by the IRI RFC, which 
we do support and give preference to. The other competing standard is the 
file:/// spec from freedesktop.org, that requires the URLs to contain the 
actual byte sequences from the 8-bit-encoded filename. The only way to 
conciliate them is to restrict to UTF-8 locales.

Therefore, KDE 4 is NOT SUPPORTED in non-UTF-8 locales.

I will not lift a finger to fix that. 

-- 
  Thiago Macieira  -  thiago (AT) macieira.info - thiago (AT) kde.org
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20071008/4e513f1f/attachment.sig>