➜
This issue tracker has been migrated to GitHub,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
Created on 2005-07-26 16:37 by orenti, last changed 2022-04-11 14:56 by admin. This issue is now closed.
| Files | ||||
|---|---|---|---|---|
| File name | Uploaded | Description | Edit | |
| diff.txt | doerwalter, 2005-09-01 17:33 | |||
| Messages (4) | |||
|---|---|---|---|
| msg48632 - (view) | Author: Oren Tirosh (orenti) | Date: 2005-07-26 16:37 | |
The utf7 encoding seems to be used quite a lot in Europe for emails (probably because it's more compact and readable than utf8+base64 or utf8+quopri). Some systems use the encoding name "unicode-1-1-utf-7" for 'utf7': http://www.google.com/search?q=unicode-1-1-utf-7 This patch adds this name as an alias for utf7. |
|||
| msg48633 - (view) | Author: Martin v. Löwis (loewis) *  |
Date: 2005-08-09 15:03 | |
Logged In: YES user_id=21627 There's no uploaded file! You have to check the checkbox labeled "Check to Upload & Attach File" when you upload a file. In addition, even if you *did* check this checkbox, a bug in SourceForge prevents attaching a file when *creating* an issue. Please try again. (This is a SourceForge annoyance that we can do nothing about. :-( ) |
|||
| msg48634 - (view) | Author: Walter Dörwald (doerwalter) * |
Date: 2005-09-01 17:33 | |
Logged In: YES user_id=89016 Here's another version of the patch. BTW, "UNICODE-1-1-UTF-7" is explicitely mentioned in RFC 1642 (http://www.faqs.org/rfcs/rfc1642.html) |
|||
| msg48635 - (view) | Author: Walter Dörwald (doerwalter) * |
Date: 2005-10-09 19:43 | |
Logged In: YES user_id=89016 Checked in as: Lib/encodings/aliases.py 1.29 Doc/lib/libcodecs.tex 1.37 Misc/NEWS 1.1390 |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:56:12 | admin | set | github: 42223 |
| 2005-07-26 16:37:08 | orenti | create | |