[TYPO3-core] Correction to charset setting in t3lib_htmlmail

Ernesto Baschny [cron IT] ernst at cron-it.de
Fri Jun 30 16:29:54 CEST 2006


Martin Kutschker schrieb am 30.06.2006 16:13:

>> Looking at the related bug #3600 it should become clear that
>> TSFE->renderCharset is the only correct version. Only when you use it
>> mail header and mail body will have a matching charset.

> I counted Stanislas submission and Franz +1 as two +1 and have commited
> (with and added ; which was missing) the patch.
> 
> Unfortunately nobody took part in the discussion
> metaCharset/renderCharset. Both a probably the same for 99% of all
> cases, but when they are not IMHO the data supplied to it will be in
> renderCharset (the one TYPO3 uses for processing *all* data). So I used
> this value for commit.
> 
> If anybody is unhappy with this decision I suggest we go and ask Kasper
> for his opinion. He has made up all the meta/render-charset stuff :-)


Just by reading the discussion and the bug report, I would say that we
need a htmlmailCharset, as Stanislas suggested, so that one can have a
different Charset for generated emails. It might be nice to have a
website in UTF-8 but still send out emails in iso-latin-1 or vice versa.

But I would agree with Stanislas that metaCharset should be used for
sending mails, while we have no other setting, because this is what the
admin explicitly set-up for the "output", and email is just another
"output" that TYPO3 might generate. From the source code comments:

 $renderCharset => Internal charset of the frontend during rendering
 $metaCharset => Output charset of the websites content. This is the
charset found in the header, meta tag etc.

I would regard "email output" as "etc". ;)

Cheers,
Ernesto



Cheers,
Ernesto



More information about the TYPO3-team-core mailing list