| Summary: | Attachments with Koi-8 encoded file names are not displayed correctly | ||
|---|---|---|---|
| Product: | [Applications] kdepim | Reporter: | Alexander Yavorsky <kekcuha> |
| Component: | messageviewer | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | aspotashev, kde |
| Priority: | NOR | ||
| Version: | 5.6.3 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Linux | ||
| URL: | https://oc.t-rosta.com/owncloud/index.php/apps/gallery/s/9q5GBrPxeO5204s#snapshot2.png | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Alexander Yavorsky
2016-05-05 10:38:47 UTC
I can confirm this bug with some additional info. I have the same problem with utf-8 coded filename* parameters. So it looks like the messageviewer does not implement https://tools.ietf.org/html/rfc5987 which then referes to https://tools.ietf.org/html/rfc2231. (Very) short summary: One can issue a MIME Header Content-Disposition: ..., filename=filename.ext or - if the filename contains non ISO-8859-1 letters: Content-Disposition: ..., filename*=coding'language'filename.ext So in my case the MIME-Part header looks like: Content-Disposition: attachment; filename*="utf-8''some-filename-with-utf-8-encoding.ext" Double quotes are optional but allowed according to RFC. Kmail takes everything between the double quotes literally as the filename. I'm on arch linux so everything pretty current: KDE Apps 17.04.1, Plasma 5.9.5, Framework 5.33.0, QT 5.8.0 Really no one even confirmed? This is a bug against current messageviewer (despite original report) not implementing a mime related RFC? Roundcube does it, Thunderbird, python mime lib... even recent Outlook! Last checked KDE Apps 17.08.3 Progress! Kmail 5.6.3 can handle this, so e.g. the following header works: Content-Disposition: attachment; filename*=utf-8''Hall%C3%B6chen.pdf Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |
