| Ticket UUID: | 503336 | |||
| Title: | Add no_softbreak flag to qp_encode | |||
| Type: | RFE | Version: | None | |
| Submitter: | usus | Created on: | 2002-01-14 14:29:02 | |
| Subsystem: | mime | Assigned To: | andreas_kupries | |
| Priority: | 5 Medium | Severity: | ||
| Status: | Closed | Last Modified: | 2002-01-17 02:39:03 | |
| Resolution: | Closed By: | andreas_kupries | ||
| Closed on: | 2002-01-16 19:39:03 | |||
| Description: |
Add the argument "no_softbreak" with a default value of false to the argument list of mime::qp_encode. If this flag is set to true, the extra handling of lines longer than 72 (shouldn't it be 76?) characters should be skipped. Reason: It is possible to qp_encode the subject string. If you do this and the subject exceeds 72 characters, a soft break is inserted. This scrambles the entire message at least if read with Outlook Express. If the insertion of soft breaks is skipped, it appears to work right with subject strings of arbitrary length (tried with strings up to about 200 chars). | |||
| User Comments: |
andreas_kupries added on 2002-01-17 02:39:02:
Logged In: YES user_id=75003 Committed to head. andreas_kupries added on 2002-01-17 02:32:59: File Added - 16213: 503336.diff andreas_kupries added on 2002-01-17 02:32:58: Logged In: YES user_id=75003 Ok, here is my patch implementing the feature. andreas_kupries added on 2002-01-17 02:24:41: Logged In: YES user_id=75003 Is a patch available ? You seem to have tested a change. usus added on 2002-01-15 19:44:42: Logged In: YES user_id=426984 I'm sure it's an Outlook bug. Nevertheless do I need this feature in order to compose messages with long subject strings destined to readers using Outlook. You are absolutely right, the standards don't say a word about a special handling of subject strings. andreas_kupries added on 2002-01-15 07:02:17: Logged In: YES user_id=75003 What does the standards say ? IOW I am suspicious that this is a bug in Outlook Express. | |||
Attachments:
- 503336.diff [download] added by andreas_kupries on 2002-01-17 02:32:58. [details]