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 |
State ⇒ Resolved
that the same 'line-length' parameter used by the base64 filter can
also be used by the quoted-printable filter. So use that.
Bug #8555: Linewrap q-p datahttp://git.horde.org/diff.php/framework/Mime/lib/Horde/Mime/Part.php?rt=horde-git&r1=379bc8815bb5432509e27a7d0c8d3be11445f82b&r2=7e3db187475cd661ab892c7a8e15b4b32983b562
New Attachment: Tickets _6832_ Re_ Warn to user while move message to Notepad_Memo.eml
State ⇒ Assigned
Assigned to Michael Slusarz
attached message.
State ⇒ Not A Bug
post-process the data. The benefit of using a php-internal
implementation outweighs the readability loss IMO.
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
http://cvs.horde.org/diff.php/framework/Mime/test/Horde/Mime/mail_003.phpt?r1=8d38a43880bfd2f005b63d098c51bb904cdaacfd&r2=3bf3c137d359062d2d9e04dfb60b10dbddf12e8e
State ⇒ Feedback
State ⇒ Unconfirmed
Patch ⇒ No
Milestone ⇒
Queue ⇒ Horde Framework Packages
Summary ⇒ Incorrect quoted printable encoding of newlines?
Type ⇒ Bug
Priority ⇒ 1. Low
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.