[Typo3-dev] mail charset, phpMail

Jan-Erik Revsbech jer at moccompany.com
Thu Sep 16 11:07:57 CEST 2004


>
> BE stuff will either be in forceCharset (preferredd) or in the charset
> of the current BE language.
>
> IMHO the API needs a way to set the charset. Defaulting is a feature but
> doesn't cove situations where one knows the charset (eg because your
> code has expclicitely converted some text into the wanted charset).
>
> I suggest doing an "auto-configure" via special mail config (localconf),
> then forceCharset, current BE language and if all fails iso-8859-1. Plus
>   it must be able to set the charset manually.

I agree completely. As for the direct_mail, it should rather set the
encoding to the encoding used by the language of the page its sending, but
that requires that the API is there off course.

>
> I wonder if we need some charset conversion logic as well. It simply is
> not enough to announce the charset in the mail headers. You must send
> the data in this charset :-) It's reasonable to assume, that this is the
> case for forceCharset and current BE language. But what about the
> special mail config and the API override. In whose responsibility is it
> that mail headers and mail data correspond in respect to the charset?
>
> Masi

I think the charset logic is a responsibility of the htmlmail class. I think
that we should try to work this into the 3.8.0 version right after the 3.7.0
is released. If we are to redelegate the actual mailsending as a service as
you suggested  (and I agree), then we might as well implement all charset
issues, and fix the quoted-printable bug that appears to be in the htmlmail
class as well.

/Jan-Erik






More information about the TYPO3-dev mailing list