[TYPO3-core] Correction to charset setting in t3lib_htmlmail

[Stanislas Rolland]

Peter Niederlag a écrit :
>
> .metaCharset is just used for telling the browser which charset is used
> (html-tag, xml-prologue, http-header), while .renderChrset actually does
> a conversion.
>   
Then, it makes sense for t3lib_htmlmail to use metaCharset to set the 
mail headers, does it not?
> If only renderCharset is used (&& no BE|forceCharset) than renderCharset
> should be used as well for conversion *and* for information about the
> charset used (html-tag, xml-prologue, http-header)
>   

See 
http://typo3.org/documentation/document-library/references/doc_core_tsref/current/view/7/3/  
:
"If renderCharset and metaCharset are different the output content is 
automatically converted to metaCharset before output and likewise are 
values posted back to the page converted from metaCharset to 
renderCharset for internal processing."

t3lib_htmlmail does not do any conversion. However, I think that if 
renderCharset and metaCharset are different, the invoking process should 
do the conversion, so that the final output uses metaCharset.
>> The point of this patch is that currently, when config.metaCharset is
>> not set, the charset of the mail may be incorrectly set to the charset
>> forced in the backend.
>>     
>
> Dont know about that but IMHO .renderCharset seems to be the way to go.
>   
Sorry, I cannot follow you down this path.

Stanislas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.netfielders.de/pipermail/typo3-team-core/attachments/20060501/3b3c51ed/attachment.htm