[TYPO3-core] RFC: Fix charset encoding in TYPO3 mails (not onlydirect_mail)

[Stanislas Rolland]

Michael Stucki a écrit :
> Hi Martin,
>
>   
>>> - added "formatflowed" to the Content-Type when 8bit is used
>>>       
>> Sorry to speak up so late, but I only noticed it now.
>>
>> format=flowed has a special meaning and AFAIK requires special formatting,
>> see http://www.ietf.org/rfc/rfc3676.txt
>>
>> Basically, to get paragraphs you have to end each line with a space
>> (except the last one).
>>
>> Does it hurt to announce a flowed format when it isn't?
>>     
>
> I really don't know. This option was added by Stanislas but I added the same
> behaviour to t3lib_div::plainMailEncoded(). Maybe he can explain, otherwise
> I have nothing against removing it again.
No, it does not. In fact, I think we should add it also on the other 
text/plain headers.

For example, when using Direct Mail and generating the plain text 
version of your message with plaintext:Lib.inc, you could modify 
plaintextLib.inc so as to use chr(32).chr(10) as linebreak inside 
paragraphs (instead of just chr(10)). Email clients that do not 
understand format=flowed will just ignore it and display the text 
version of the email message the usual way (lines of 76 characters or of 
whatever length you choose to use). But modern email clients will 
understand the format=flowed parameter and will treat linebreaks that 
are preceeded by a space as soft linebreaks. They will thus rewrap the 
text to fit the width of the window in which it is displayed. The text 
will just "flow" in a normal fashion. The result is much nicer display 
of plain text messages.

Regards,
Stanislas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.netfielders.de/pipermail/typo3-team-core/attachments/20060201/2817e09d/attachment.html