Hi, Paul. Please see comments below...
Date: Thu, 05 Nov 2009 16:37:42 -0500 From: "Paul B. Gallagher"
<[email protected]> To:
[email protected] Subject: Re: TEXT PARTIALLY GRAY
INSTEAD OF BLACK. WAS: Message-ID:
<[email protected]> Content-Type:
text/plain; charset=ISO-8859-1; format=flowed Daniel wrote:
> James, some people use signature blocks which contain their names,
> contact details, amusing quotes, whatever. These can be added,
> automatically, by telling SM where the sig file is.
> > Then, at the end of the real message, SM adds a sig delimiter
(a line
> consisting of two dashes followed by a space) and then adds,
usually in
> a lighter text, the sig file.
Actually, the sig file is grayed out as a display feature, just as
quoted material is italicized or reddened (depending on your settings),
but if you look at the source code you'll see nothing -- no special
codes to make it do that. SM, like its predecessors, recognizes quote
marks and sig delimiters and uses that input to modify the display.
> If things are happening right, when that message is quoted the sig
> delimiter and the sig file are not quoted.
> > But, if things don't happen right, the sig delimiter might not be
> removed, so anything after the sig delimiter is in the lighter text.
> > Can be a real problem if people top post, i.e. reply at the top
of the
> message.
Yep. Everything after their sig, including the entire original message,
is treated as their sig, which means a) it's grayed out, and b) it's
stripped out when the next person replies, a sort of automatic
pruning.;-)
-- All it takes is a line of dash-dash-space for SM to decide this is
the sig and everything from here on out is grayed and stripped from
replies. See? My message now contains three sig delimiters, and
everything after the first one is grayed out.
-- War doesn't determine who's right, just who's left. -- Paul B.
Gallagher
.
.
Your message is marked exactly as you say it should be on my end. As
a matter of fact the entire digest follows it correctly. Unless I'm
remembering it wrong other digests have had random mixes of light and
dark type. I'll check out a few more and shout back if I don't
understand it.
Thanks,
James
.
.
Hi, Paul. I told you I would let you know when I find another example
of the apparent random application of light or dark text and here it
is. I'm including the entire message, which is totally light gray text
[header and all; completely light type] in case you might pick up some
clue as to why it should all be light. Or not. Here's the post:
.
Message: 2
Date: Thu, 05 Nov 2009 23:17:15 +0000
From: Andrew Paxton<[email protected]>
To:[email protected]
Subject: SM 2.0 personal toolbar strangeness...
Message-ID:<[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Hi,
Apologies if this has already been discussed& I've missed it - just
joined this list and there is a lot of stuff..
Just upgraded to Build identifier: Mozilla/5.0 (Windows; U; Windows NT
5.1; en-US; rv:1.9.1.4) Gecko/20091017 SeaMonkey/2.0 on both my home&
work PCs (winxp)
on my home machine, everything was fine; however, on my work pc, the
installation over-wrote my bookmarks (not a prob as I backed it up), and
my personal tool bar with the defaults.
Try as I might, I can't drag any links onto the personal toolbar on the
work PC - fine on the home one.
Any pointers?
Cheers,
PS tried the mozilla.support.seamonkey NG - can read, but can't post..
A News (NNTP) error occurred: Posting Failed (Article NOT Posted to a
Valid Newsgroup
.
End of quote. While in the digest ALL of the text above is light type here in
my composer it's all dark type. Why would it be all light type in 2.0?
In addition the next message [number 3] in the digest [which happens to be from
me] shows exactly the same result: All light type, including header in the
part I wrote, while the quoted material [from NoOp] is all dark. Here's the
post:
.
Message: 3
Date: Thu, 05 Nov 2009 18:27:56 -0500
From: James<[email protected]>
To:[email protected]
Subject: SEAMONKEY 2.0 QUICK LAUNCH ICON SHORTCUT GONE
Message-ID:<[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Could you please tell me what of the many features of the referenced
page addresses my question?
Thanks,
James
.
Above is the part I wrote, all in light type. Below is the quoted part of the
post, which is all dark type:
.
> Message: 3
> Date: Wed, 04 Nov 2009 08:26:30 -0800
> From: NoOp<[email protected]>
> To:[email protected]
> Subject: Re: SEAMONKEY 2.0 QUICK LAUNCH ICON SHORTCUT GONE
> Message-ID:<[email protected]>
> Content-Type: text/plain; charset=UTF-8
>
> On 11/04/2009 07:46 AM, James wrote:
>
>> > I know how to fix the problem [simple] but I'm wondering what would
>> > cause it. Vista Home Basic 64 bit did update and I had a message that
I
>> > needed to restart to complete them but the quick launch icon was gone
>> > and was still gone after I rebooted. Why??? AFAIK Seamonkey still
>> > works fine.
>> >
>>
> http://www.seamonkey-project.org/releases/seamonkey2.0/
.
.
End of quote. And again the type [while all light in my browser] all shows up
dark in composer.
Next I have messages 4, 5, 6 and 7 which all show complete dark type, including
headers.
Message 8 is all dark type except the part past the two dashes, which is light.
I believe this is the way you're saying it should be. And AFAIK messages 9
and 10 follow in the manner you describe.
Sorry for so much typing, and I hope some of it makes sense.
Thanks,
James
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
