Open Bug 273700 Opened 20 years ago Updated 2 years ago

[html2txt] signatures in html-messages ignored in text-only view

Categories

(MailNews Core :: Composition, enhancement, P5)

x86
All
enhancement

Tracking

(Not tracked)

People

(Reporter: motto, Unassigned)

Details

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; MyIE2; MRA 4.0 (build 00768); Maxthon; .NET CLR 1.1.4322)
Build Identifier: Mozilla Thunderbird 1.0 (Windows/20041206)

Signatures in html messages ignored by TB in "Message Body as Plain Text" view, 
and in message replying if this view was selected, or if replying is allways in 
plain text

Reproducible: Always
Steps to Reproduce:
A:
1. Select any HTML mesage with signature, without (!) text-plain part 
(
<pre class="moz-signature" cols="$mailwrapcol">-- 

Kind regards,
<br /></pre>
)
2. Select View->Message Body As -> Original HTML
3.  Select View->Message Body As -> Plain Text
B:
3. Check off Tools -> Account -> Settings -> Compose message in HTML format
4. Select Reply to HTML message
Actual Results:  
A2: Signature detected as signature
A3: Signatire not detected as signature

B4: Signature quoted in reply

Expected Results:  
A2: Signature detected as signature
A3: Signature detected as signature

B4: Signature cuted off from reply

seems like bug in html2txt
Note that even replying to an HTML mail *as* HTML does not cut the sig from the 
original text -- bug 43829.  That only happens when replying to a plain text sig 
as plain text.  So I'm not sure whether result (B4) is due to the HTML2TXT bug 
you're citing here, or to that bug -- or whether *that* bug is due the HTML2TXT 
bug!

Anyway, this is true in Mozilla as well as Thunderbird; and it's true whether 
the sig file itself is HTML or plain text.
Assignee: mscott → sspitzer
Status: UNCONFIRMED → NEW
Component: General → MailNews: Composition
Ever confirmed: true
Product: Thunderbird → Core
Version: unspecified → Trunk
There is no standard to signify a signature in HTML (in plaintext, there is:
"-- \n"). I made up one by adding a special class (moz-signature), and there's a
default stylesheet for it to make it display grey. It only works when sent by
Mozilla and received by Mozilla.

Understandably, the HTML->TXT converter does not have code to detect that class
and thus does not convert it by adding "-- \n", which  would be the plaintext
way to express a signature. In fact, I think I might have wanted to do that back
then, but some people were so opposed to adding *anything* in the plaintext
output of the converter that's not looking *exactly* like that in the HTML
version as well (and adding dashes would surely count as that, for these people)
that I didn't even try. I guess I could add it in the mode where I am allowed to
add stuff, like / for <i>.

So, that would be low-priority enhancement of the HTML->TXT converter in fancy
mode only.

I recommend using Simple HTML mode and the HTML composer. Works much better,
because it's much cleaner.
Severity: normal → enhancement
Priority: -- → P5
sorry for the spam.  making bugzilla reflect reality as I'm not working on these bugs.  filter on FOOBARCHEESE to remove these in bulk.
Assignee: sspitzer → nobody
QA Contact: composition
Product: Core → MailNews Core
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.