Open Bug 113120 Opened 23 years ago Updated 2 years ago

Trailing space not deleted after soft line break in QP messages

Categories

(MailNews Core :: MIME, defect)

x86
Windows 98
defect

Tracking

(Not tracked)

People

(Reporter: karl, Unassigned)

Details

Attachments

(1 file)

When using 'quoted-printable', RFC 1521 says:

 "=" at the end of an encoded line, indicating a soft line break
      (see rule #5) may follow one or more TAB (HT) or SPACE characters.
      It follows that an octet with value 9 or 32 appearing at the end
      of an encoded line must be represented according to Rule #1.  This
      rule is necessary because some MTAs (Message Transport Agents,
      programs which transport messages from one user to another, or
      perform a part of such transfers) are known to pad lines of text
      with SPACEs, and others are known to remove "white space"
      characters from the end of a line.  Therefore, when decoding a
      Quoted-Printable body, any trailing white space on a line must be
      deleted, as it will necessarily have been added by intermediate
      transport agents.

Trailing white space after a = character is *not* deleted. See the attached e-mail.
Attached file Test-case
Note that the line 'sendast som 7-bits' have tons of trailing white space which
is not deleted. The four lines below also have trailing whitespace, which
should be deleted, and the line should be 'merged' to *one* line (since a soft
line break has been used). The entire paragraph should look like this:

---
Litt apropos: Eg hadde ein gong eit program for dekoding av
Base64, som var skriven som ASCII[1] (og som dermed kunne
sendast som 7-bits							       
     
tekst). Nokon som kjenner til dette, og kan
senda det til meg/lista (ikkje ødvendigvis som vedlegg)?
---

Note that the last paragraph also has trailing spaces which should be deleted.
The only place where there *should* be a trailing space, is the signature
seperator (which is coded --=20).
Sorry, I forgot to remove the trailing spaces. :)
The paragraph should look like *this* (trailing spaces should *always* deleted,
even if a hard line break is used):

---
Litt apropos: Eg hadde ein gong eit program for dekoding av
Base64, som var skriven som ASCII[1] (og som dermed kunne
sendast som 7-bits
tekst). Nokon som kjenner til dette, og kan
senda det til meg/lista (ikkje ødvendigvis som vedlegg)?
---
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla1.1
I can confirm that this bug is still present in Moz 1.2.1.

And since the 'Target Milestone' (1.1alpha) has already been released, should I update it, or just leave it?
Product: MailNews → Core
(In reply to comment #1)
> The entire paragraph should look like this:

It would have been good if you'd mentioned how it actually looks.  With TB 1.5, I'm seeing:
====
Litt apropos: Eg hadde ein gong eit program for dekoding av
Base64, som var skriven som ASCII[1] (og som dermed kunne
sendast som 7-bits [spaces]
tekst). = [spaces]
Nokon = [spaces]
som kjenner = [spaces]
til dette, og kan
senda det til meg/lista (ikkje nødvendigvis som vedlegg)?
====

That is, with the '=' appearing within the text.
Assignee: ducarroz → nobody
Status: ASSIGNED → NEW
QA Contact: esther
Target Milestone: mozilla1.1alpha → ---
QA Contact: mime
Product: Core → MailNews Core
Still confirmed.

Thunderbird 52.0.1 (32-bit)
Windows 7 64-bit
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: