To show the attachment links in a mail, we use the function "link_att()". In this function we use nocc_imap::mime_header_decode() to decode the filename. Unfortantly this broke the string, if it is not decode...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
A other problem is "nocc_imap::mime_header_decode()" in the html/send.php file. If we use here also "nocc_imap::utf8()" we have no problem. I'am not sure, if we really a convert function at this place, but it also not hurt. ;)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I can reproduce this behaviour, as far as I can see in the source code it looks like a NOCC problem.
One of the problems is, that NOCC not correctly encode the filename from a attachment.
If I send a file with the (funny) name "Ümlaute.txt" with Thunderbird, I got the following source code:
Content-Type: text/plain;
name="=?ISO-8859-15?Q?=DCmlaute=2Etxt?="
Content-Transfer-Encoding: base64
Content-Disposition: inline;
filename*=ISO-8859-15''%DC%6D%6C%61%75%74%65%2E%74%78%74
With NOCC is looks like the following lines:
Content-Type: text/plain;
name="Ümlaute.txt"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename="Ümlaute.txt"
To show the attachment links in a mail, we use the function "link_att()". In this function we use nocc_imap::mime_header_decode() to decode the filename. Unfortantly this broke the string, if it is not decode...
use imap_utf8() in link_att() function
We can fix one of the problems, if use "nocc_imap::utf8()" instead "nocc_imap::mime_header_decode()" in the link_att() function.
use imap_utf8() in html/send.php
A other problem is "nocc_imap::mime_header_decode()" in the html/send.php file. If we use here also "nocc_imap::utf8()" we have no problem. I'am not sure, if we really a convert function at this place, but it also not hurt. ;)
Confirmed and in work...