On 09/26/2011 03:08 PM, Mike Easter wrote: > NoOp wrote: >> Mike Easter wrote: > >>> Could you please set your send_plaintext_flowed to true instead of false >>> and also compose/post something with one or more 'normal' longer >>> paragraphs > > Now that you are configured to f=f, your SM did the 'opposite' of f=f by > stripping off the trailing spaces in the cited material above. My > previously flowable lines above no longer flow. That is part of the > paradox mentioned earlier. > >> Could you please set your send_plaintext_flowed to true instead of false >> and also compose/post something with one or more 'normal' longer >> paragraphs which contains lines sufficiently long so that your editor >> wraps them at your linewrap length? > > Your original material above me here will flow because it has trailing > spaces. > >> However I'm not sure that will make any difference as my settings are to >> 'Wrap plain text messages at 72 characters anyway. > > The wrap length is for the 'infrastructure' for where the f=f softbreaks > go, as described at the Tbird link explaining how plaintext and f=f > works that I posted earlier. > > If you look at flowed text with flowed text display enabled, the flowed > text flows to the window edge, but if you look at flowed text based on > infrastructure with a reader which does not display f=f as flowed, or if > you look at flowed text in the message source, you will see what looks > like normal wraps at 72 chars. > > That is part of the beauty of f=f, that it 'degrades' compatibly if the > reader isn't 'doing' f=f display.
Rolls eyes... sorry I'm just going to stick with my standard: mailnews.display.disable_format_flowed_support;true mailnews.send_plaintext_flowed;false Not because you may/may not have a valid point, but because I don't use it anyway. Sorry & good luck sorting this out on your side. _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
