Ray_Net wrote:
Barry Edwin Gilmour wrote, On 21/07/2012 02:27:
Ray_Net wrote:
Barry Edwin Gilmour wrote, On 20/07/2012 03:43:
Ray_Net wrote:
Thee Chicago Wolf [MVP] wrote, On 19/07/2012 20:18:
The subject of a mail is too long in the "window list of
subjects". But
is ok in the "window preview of the mail".
You certainly will argue that SM is perfect and this is because
the mail
came from another mail-client.
BUT SM is not consistent between his two windows
"window list of subjects"
and
"window preview of the mail"
As seen here: http://home.scarlet.be/~rs268454/subject-too-long.jpg
What can i do to permit a solution of this SM problem ?
If the width of the subject column is xx characters wide, you could
widen it. This is not the fault of Seamonkey nor another email
client.
It is a pixel limit in the column width.
You could always use a smaller display font which will then fit more
characters in whatever the width is of your Subject column. It up to
you, the user, to adjust the Subject column width to allow for long
subject lines.
- Thee Chicago Wolf [MVP]
You did not understand or you did not look at my screen copy.
The subject in the "window list of subjects" is INCORRECT.
Look in my screen copy the added string "
To: [email protected]"
or
X-Antivirus: avast! (VPS 120719-1, 19/07/2012), Outbound message
Came from the next part of the mail and have nothing to do with
the subject.
This extra string is not present in the "window preview of the
mail" which is ABOLUTELY correct.
and have nothing to do with the "...width of the subject column".
IT'S NOT A LONG SUBJECT LINE the subject should be only = to:
Tr : TR: Fw: Tr: : Comprendre le français.
or
Réf. : Crabe et Corsica
without any other text appended.
Message-Headers are erroneously displayed in SeaMonkey's
Thread-pane's "Subject" window..
THANKS .... with this short description, i was able to create
https://bugzilla.mozilla.org/show_bug.cgi?id=776096
Voila ! Now i will wait until i died for a solution :-)
Haven't seen it myself, but it certainly is unusual.
If you could copy the message's source-text, into your bug report (in
English, the menu is:- "View" -> "Message S_o_urce Ctrl+U"), I think
that may help locate the cause.
That's a very good idea, but if i do a copy/paste of the text in the
"Ctrl-U" windows i am not sure that this text will be exactly the same
as the text on my disk.
Anyway, it's done
In fact we can see a kind of "blank line" between the subject part and
the next header.
Perhaps i should isolate the message and put it in a separate empty
directory, so i can see the text in hex format.
I think you really need some explanation from our messaging gurus, but
the Subject line in both message-sources, is not the usual standard text
Subject headers that we see.
Also, it may not be relevant, but I often see the "=" sign at the end of
a header-string (e.g. 80 character line-length), denoting that the next
bit of text, should be joined to the previous-text, e.g.~
(rest of header line) barry.gilmour@bigp=
ond.com
displays in message-display as ~
(rest of header line) [email protected]
so I'm thinking that the "=" sign at the end of both of your
source-text's "Subject" header title (message-link?), may simply be
telling the application to display the linked-title with the next header
line, which is what it is correctly doing?
But I believe we need some insight from our messaging gurus, to
illuminate this.
I'd think the message-source from the network-server before it downloads
into a email-client, would be more useful, than the hex out of the
local-email-client would be?
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
