Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

TB 12.0

1 view
Skip to first unread message

James Silverton

unread,
Apr 29, 2012, 11:00:22 AM4/29/12
to
Just for the record, I have just installed 12.0 smoothly and without
incident. Best of luck to everyone else.
--

James Silverton ( NOT not.jim.silverton)

Mike Easter

unread,
Apr 29, 2012, 11:10:39 AM4/29/12
to
James Silverton wrote:
> Just for the record, I have just installed 12.0 smoothly and without
> incident. Best of luck to everyone else.

... which /still/ doesn't do format=flowed quoted material
properly/compliantly.

It baffles me that the quoted material has trailing spaces just like the
new content, but when 'transmitted', the trailing spaces are stripped
from the quoted material but not from the new/unquoted material.

Very puzzling. Very very puzzling indeed.

--
Mike Easter

David

unread,
Apr 29, 2012, 12:08:11 PM4/29/12
to gen...@lists.mozilla.org
What is the Bugzilla number for this?

--

David


Mike Easter

unread,
Apr 29, 2012, 12:25:01 PM4/29/12
to
456053 is the one I visit, but there are numerous others related to the
problem.

https://bugzilla.mozilla.org/show_bug.cgi?id=456053 Bug 456053 - Quoted
text receives hard line breaks in f=f plain-text replies

There has even been a patch provided as early as 2008 Sep by Andrly
Tkachuk, but for reasons that only developer-types understand, that
solution hasn't been used to (actually) solve the problem in any releases.

Apparently, if something is gecko related, it doesn't get fixed until
such time that gecko people want to fix it instead of 'Tb' people, or
something else interfering with a resolution that I don't understand
either.

The old dodge 'we can't actually use this patch to fix the problem
because it might break something else' is presumably operative -- like I
say, I'm not a developer and I don't understand.

All I understand is that the developers ignore the problem and don't
care and don't think it is of any significance that they care to fix.
Periodically someone will get somewhat interested, then they lose interest.


--
Mike Easter

David

unread,
Apr 29, 2012, 12:53:19 PM4/29/12
to gen...@lists.mozilla.org
Wow. That is an old one. I added 'me' to the Cc: but I am not exactly
sure just was this looks like. Maybe seen it but don't recognize it?

--

David


Man-wai Chang

unread,
Apr 29, 2012, 1:35:16 PM4/29/12
to
On 29/04/12 11:00 PM, James Silverton wrote:
> Just for the record, I have just installed 12.0 smoothly and without
> incident. Best of luck to everyone else.

Same!

--
@~@ Remain silent. Nothing from soldiers is real!
/ v \ Simplicity is Beauty! May the Force and farces be with you!
/( _ )\ (Fedora 15 i686) Linux 3.3.3
^ ^ 01:32:01 up 2 days 4:48 0 users load average: 0.01 0.02 0.05
不借貸! 不詐騙! 不援交! 不打交! 不打劫! 不自殺! 請考慮綜援 (CSSA):
http://www.swd.gov.hk/tc/index/site_pubsvc/page_socsecu/sub_addressesa

Luuk34

unread,
Apr 29, 2012, 1:48:48 PM4/29/12
to Mike Easter
When looking at bug 448198 (which is the bug wat 456053 depends on), and
sending a mail to meself with this setting:
"Turn format=flowed back on (set the pref back to True)."

and sending the "Ben & Jerry" test, the message is already stored the
wrong way in my .Sent folder.....

Mike Easter

unread,
Apr 29, 2012, 3:31:16 PM4/29/12
to
David wrote:
> Mike Easter wrote:

>> https://bugzilla.mozilla.org/show_bug.cgi?id=456053 Bug 456053 -
>> Quoted text receives hard line breaks in f=f plain-text replies
>>
>> There has even been a patch provided as early as 2008 Sep by
>> Andrly Tkachuk, but for reasons that only developer-types
>> understand, that solution hasn't been used to (actually) solve the
>> problem in anyreleases.

> Wow. That is an old one. I added 'me' to the Cc: but I am not
> exactly sure just was this looks like. Maybe seen it but don't
> recognize it?

The default mode for Tb is for f=f to be enabled to send/post and for
the f=f text to display 'html-ized' (which term I don't really like),
but the most noticeable characteristic is that when you are viewing f=f
text, it wraps to the window.

The really important thing is that the wrapping is 'flowed', so when
working properly for f=f text, it is 'impossible' to develop ugly
shortlines or embarassing linewraps or whatever you want to call it.

Tb posts its new material flowed properly and makes a f=f header; but Tb
does *not* post its quoted f=f material properly flowed, but instead
strips the trailing spaces in the quoted material which exist during the
editing/composing of the message so that when the message is posted (or
reaches the Sent folder) the quoted material isn't f=f.

The presence or absence of trailing spaces can be identified in a
message which is being read by using ctrl-U and locating the cursor at
the EOL to see if there is a space there.

The presence or absence of trailing spaces can be seen in a message
which is being editing by simply placing the cursor at the end of the
line, such as for the quoted material.

What will become f=f original material will show trailing spaces at the
EOLs within a par, but no such trailing spaces at the EOLs which also
end par/s. That is as it should be and works properly for the original
message content; but while that is also as it should be at the EOLs in
the quoted material, it doesn't end up like that after being Sent.


--
Mike Easter

Ron Hunter

unread,
Apr 29, 2012, 3:55:56 PM4/29/12
to
I am afraid the ugly truth is that only You and Mike really CARE.
Give it up.

David

unread,
Apr 29, 2012, 4:37:46 PM4/29/12
to gen...@lists.mozilla.org
Thanks for the sympathy. For Mike that is. :-)

I'm still not sure that I have ever seen what he is talking about with this.


--

David


Mike Easter

unread,
Apr 29, 2012, 5:04:33 PM4/29/12
to
David wrote:
> Ron Hunter wrote:

>> I am afraid the ugly truth is that only You and Mike really CARE.
>> Give it up.
>
>
> Thanks for the sympathy. For Mike that is. :-)
>
> I'm still not sure that I have ever seen what he is talking about with this.

I'm sure you have routinely seen people posting with Tb here and their
text wrapping to the window.

If I post here (or .test) using an agent which does f=f properly^1, and
then I reply to that f=f, the quoted material will *also* wrap to the
window. Likewise and so forth if I reply to that reply, etc. The
important thing is that it will flow, so as the lines get longer due to
quoting marks, those quoted lines don't start breaking up into ugly
shortlines and so they don't need to be reformatted on a regular basis.

Perhaps the rewrapping was introduced in the development as an 'apology'
or compensation for not doing f=f properly


^1 such as Opera, which is the handiest one I have, since I'm normally
in linux and I don't have MesNews or Gravity on my Win boxen,


--
Mike Easter

David

unread,
Apr 29, 2012, 5:15:10 PM4/29/12
to gen...@lists.mozilla.org
Hmm... At times I have seen 'funny' wraps. But there are so many OS's
and so many email / newsreader clients all set to so many different
fonts with different word-wraps I just assumed that was the reason.

There is a lady on another OT list that I visit that sends a 'text type
birthday cake' on your birthday. I know what it is *supposed to look
like* but it is always 'messed up'. I always assumed that was Kmail and
Mandriva v. me and my stuff. Although now she tells me she uses Claws
and Mageia. :-)
--

David


WLS

unread,
Apr 30, 2012, 8:45:29 AM4/30/12
to
On 04/29/2012 11:00 AM, James Silverton wrote:
> Just for the record, I have just installed 12.0 smoothly and without
> incident. Best of luck to everyone else.

Nice to hear.

I believe TB 12.0.1, and SeaMonkey 2.9.1 are due to be released today.

--
Thunderbird Beta | openSUSE 12.1 | KDE 4.7.2
Humans aren't a color of skin, a religion, a sex, a sexual orientation,
or a flag. We are human beings and that is how we need to see and treat
each other. - Justin Sane


0 new messages