6.0.0-beta1
7/8/25

[#8555] Incorrect quoted printable encoding of newlines?
Summary Incorrect quoted printable encoding of newlines?
Queue Horde Framework Packages
Queue Version Git master
Type Bug
State Resolved
Priority 1. Low
Owners slusarz (at) horde (dot) org
Requester jan (at) horde (dot) org
Created 09/06/2009 (5784 days ago)
Due
Updated 10/08/2009 (5752 days ago)
Assigned 09/22/2009 (5768 days ago)
Resolved 10/08/2009 (5752 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
10/08/2009 04:45:04 PM Michael Slusarz Comment #8
State ⇒ Resolved
Reply to this comment
Looks like the PHP documentation has been updated to make more clear 
that the same 'line-length' parameter used by the base64 filter can 
also be used by the quoted-printable filter.  So use that.
09/22/2009 07:01:39 AM Jan Schneider Comment #6
New Attachment: Tickets _6832_ Re_ Warn to user while move message to Notepad_Memo.eml Download
State ⇒ Assigned
Assigned to Michael Slusarz
Reply to this comment
Looks like PHP's en-/decoding is indeed causing some problems. See the 
attached message.
09/08/2009 05:59:39 PM Jan Schneider Comment #5
State ⇒ Not A Bug
Reply to this comment
I guess we have to live with it then. It doesn't make much sense to 
post-process the data. The benefit of using a php-internal 
implementation outweighs the readability loss IMO.
09/08/2009 05:53:30 PM Michael Slusarz Comment #4 Reply to this comment
Not sure what we can do about this.  Quoted-printable encoding is now 
done via a PHP stream filter, and this (encoding newlines) appears to 
be the expected behavior.  See the example at:

http://www.php.net/manual/en/filters.convert.php
09/07/2009 11:35:05 PM Michael Slusarz Comment #2
State ⇒ Feedback
Reply to this comment
Is this text/plain flowed data?
09/06/2009 04:35:54 PM Jan Schneider Comment #1
State ⇒ Unconfirmed
Patch ⇒ No
Milestone ⇒
Queue ⇒ Horde Framework Packages
Summary ⇒ Incorrect quoted printable encoding of newlines?
Type ⇒ Bug
Priority ⇒ 1. Low
Reply to this comment
I'm not sure, but I think we are incorrectly encoding newlines when 
converting to quoted printable now.

The longer stay as-is, but are converted to =0A. I don't see any other 
client doing this, and it makes the message source less readable, what 
the purpose of quoted printable vs. base64 is.

Saved Queries