Mike Easter wrote:

f=f behavior comes in several levels of implementation as seen in a number of news agents.

 -1- post original content with trailing spaces
 -2- honor the existing trailing spaces in quoted material
 -3- stamp f=f properly in the header

SM is performing 1 and 3 but not 2,

Honoring f=f in quoted material, #2, is a very important function/necessity for f=f compliance and benefits.

Tb2 performs all 1-3. Only Andriy Tkachuk patch built versions of Tb3-7 and corresponding SeaMonkeys so perform. Opera presently performs 1-3, I'm not familiar with its version history re f=f, but I think Opera has been supporting f=f a long time.

Opera also has some interesting workarounds to the 'rewrap' problem. All Tbirds including Tb2 rewrap by stripping the trailing spaces, thus de-f=f/ing the rewrapped content.

If Opera pastes a 'EOL and > cleaned' paragraph with no linewraps or quotes into the content and a single quote mark is placed at the beginning of that par, when sent, the posted par is in normal quoted f=f and wrapped condition. This facilitates one variety of rewrapping workaround.

Opera cannot paste as quotation like Tb/SM, but it can do the above as a workaround for that too.

The editor Vim supports f=f formatting.

There are no practical workarounds for the quoted text f=f deficiency of all modern versions of Tb and SM with the exception of using the Tkachuk patch and building. It is not possible to manually fix what happens to the quoted text for the non-Tb2 versions, as the sending strips any trailing spaces which are manually introduced.

Now that I understand that this problem is not exclusively SM but all Tb/s after Tb2, I've taken it to moz.dev.apps.tbird instead of staying here with my whinge.

--
Mike Easter
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey

Reply via email to