Actions
Bug #14683
closedform mails not supporting different charsets (utf-8)
Start date:
2005-04-18
Due date:
% Done:
0%
Estimated time:
TYPO3 Version:
3.7.0
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:
Description
Judging from postings on the mailing lists it seems that it is already a known fact that formmails (and apparently all mails generated by t3lib_htmlmail) are always ISO Latin1 encoded, even when the site's charset ist set to e.g. utf-8, thus producing messed up emails for non-ASCII characters.
But I didn't find any posting on bugs.typo3.org on this issue, so I hope this is already fixed for 3.8.0 or will be!?
(issue imported from #M992)
Updated by Karsten Dambekalns over 19 years ago
AFAICT the mails are encoded according to the forceCharset setting, but the mail headers states it's in 8859-1. So it should be enough to fix the header, there is even an extension that attempts to do this.
Updated by Ådne Hovda over 19 years ago
The cleanest solution might be:
- Remove the hardcoded charset in t3lib_htmlmail.
- Fetch the charset in tslib_fe, $TSFE->charSet.
- Pass the charset along with the rest of the mail to t3lib_htmlmail, via t3lib_formmail
Actions