[TYPO3-core] RFC: fix bug #3600 - config.formMailCharset

[Franz Holzinger]

Martin Kutschker a écrit :

>Franz Holzinger schrieb:
>  
>
>>Hello Martin,
>>
>>    
>>
>>>Part 2:
>>>To make the setting really work it is necessary to convert the charset
>>>from the form into the desired mail charset. The patch does this. Note
>>>that renderCharset is used because TYPO3 (see index_ts) does
>>>automatically convert the sent data (metaCharset) into the internal
>>>charset (renderCharset).
>>>
>>>Testing:
>>>
>>>Set up a FORM or form content element and set config.formMailCharset
>>>to any desired charset.
>>>
>>>      
>>>
>>>$this->from_email = ($V['from_email']) ? $V['from_email'] :
>>>(($V['email'])?$V['email']:'');
>>>      
>>>
>>>$this->replyto_email = ($V['replyto_email']) ? $V['replyto_email'] :
>>>$this->from_email;
>>>      
>>>
>>Nearly everything is converted with the charset. Why not the emails too?
>>Domain names with Umlaute like günstig.de are possible in Germany.
>>    
>>
>
>IDN-domains are set as plain ASCII, eg günstig.de => xn--gnstig-3ya.de
>
>So for such domains we don't need a charset but an IDN conversion. TYPO3 
>has currently no code for this.
>
>  
>
So please open a case on the bugtracker for this.

The test went wrong.
Can you send me the total file, because I cannot check out from CVS at
the moment to apply the diff? I forgot to copy the file before changing
it manually.

Or +1 if no more test is needed.


- Franz