Summary: | Broken handling of non-textual URLs in UTF-8 mode | ||
---|---|---|---|
Product: | [Unmaintained] kdelibs | Reporter: | Thiago Macieira <thiago> |
Component: | general | Assignee: | Stephan Kulow <coolo> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | Page displaying the problem |
Description
Thiago Macieira
2004-09-15 06:10:18 UTC
Created attachment 7533 [details]
Page displaying the problem
Yet another problem, probably related: The same file, when saved to disk and opened directly (as opposed to loading from network), or when charset=utf-8 in the <meta> header, displays even more bizarre URLs. Apparently, "n%edvel.png" gets converted using Latin 1 into its Unicode form, then decoded into UTF-8. Therefore, we get: written in page: n%EDvel.png desired name: 6e ed 76 65 6c 2e 70 6e 67 name shown in Konqueror: nÃvel.png requested through network: n%c3%advel.png opened locally: 6e c3 83 c2 ad 76 65 6c 2e 70 6e Conclusion: ED got displayed as C3 AD and that opened C3 83 C2 AD. The problem with loading the wrong URL, as in comment #0, has disappeared. The wrong filename is still shown, though. |