| Summary: | display errornous base64 encoding? | ||
|---|---|---|---|
| Product: | [Unmaintained] kmail | Reporter: | Christof Schulze <christof.schulze> |
| Component: | general | Assignee: | kdepim bugs <pim-bugs-null> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | normal | CC: | martin |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Gentoo Packages | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Christof Schulze
2007-02-21 12:32:36 UTC
I'm not the encoding guru, but I ask myself, how can such a mail be displayed correctly ? The Content-Transfer-Encoding says base64, but the content is partly plain text (the line 'has trailing "-"') and partly base64 encoded. In my test I just removed the 'has trailing "-"' line and, voila, the text is shown correctly. For me it's also not clear, what that single half-line 'has trailing "-"' shall mean at all, because the complete decoded rest says (see below). So I'd say, this is not worth looking into any further. #79: VERSION string in resulting shell script has trailing "-" -------------------------+-------------------------------------------------- Reporter: anonymous | Type: enhancement Status: new | Priority: major Milestone: Version 0.8 | Version: 0.7 Keywords: | -------------------------+-------------------------------------------------- -- Ticket URL: <https://faracvs.cs.uni-magdeburg.de/projects/christsc-darbackup/ticket/79> christsc-darbackup <https://faracvs.cs.uni-magdeburg.de/projects/christsc-darbackup> My example project |