From 2b21fdcc0d6747304f884267de50f1b68af32194 Mon Sep 17 00:00:00 2001 From: bwarsaw Date: Fri, 9 Aug 2002 23:40:24 +0000 Subject: GetConfigInfo(): Add description of encode_ascii_prefixes. --- Mailman/Gui/Language.py | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) diff --git a/Mailman/Gui/Language.py b/Mailman/Gui/Language.py index 00fff1470..c2c50d8aa 100644 --- a/Mailman/Gui/Language.py +++ b/Mailman/Gui/Language.py @@ -73,6 +73,31 @@ class Language(GUIBase): default language must be included.''')), + ('encode_ascii_prefixes', mm_cfg.Radio, + (_('Never'), _('Always'), _('As needed')), 0, + _("""Encode the + subject + prefix even when it consists of only ASCII characters?"""), + + _("""If your mailing list's default language uses a non-ASCII + character set and the prefix contains non-ASCII characters, the + prefix will always be encoded according to the relevant + standards. However, if your prefix contains only ASCII + characters, you may want to set this option to Never to + disable prefix encoding. This can make the subject headers + slightly more readable for users with mail readers that don't + properly handle non-ASCII encodings. + +
Note however, that if your mailing list receives both encoded + and unencoded subject headers, you might want to choose As + needed. Using this setting, Mailman will not encode ASCII + prefixes when the rest of the header contains only ASCII + characters, but if the original header contains non-ASCII + characters, it will encode the prefix. This avoids an ambiguity + in the standards which could cause some mail readers to display + extra, or missing spaces between the prefix and the original + header.""")), + ] def _setValue(self, mlist, property, val, doc): -- cgit v1.2.3-70-g09d2