I'm in Canada, which as you probably know is an officially bilingual (english and french) country. I am attempting to set up some mailman discussion lists, with bilingual footers for the messages. These are on my web hosting service, dreamhost.com. Unfortunately, when I have US english set as the default language, mailman strips out all the accented characters in the french portion of the footer. Using french as the default language prevents this from happening, but most of my list administrators want english for their admin pages. What I would like would be a way to set mailman to NOT strip out accented characters when english is set as the default language. Alternatively, is there a way to have the admin pages open in english when the default language is french? Thank you for your help! Henry
Henry Olders wrote:
What I would like would be a way to set mailman to NOT strip out accented characters when english is set as the default language.
Add one of the following lines to mm_cfg.py depending on your preferred character set
add_language('en', 'English (USA)','utf-8')
or
add_language('en', 'English (USA)','iso-8859-1')
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Christian Mack wrote:
Why would this be true? Quoting from section 2.6 of the Unicode 5.0 standard <http://www.unicode.org/versions/Unicode5.0.0/ch02.pdf#G19273>:
Use of a BOM is neither required nor recommended for UTF-8, but may be encountered in contexts where UTF-8 data is converted from other encoding forms that use a BOM or where the BOM is used as a UTF-8 signature.
I would expect that one would only choose utf-8 as the character set for english in an environment where the web server's default character set is utf-8, and emails built from .txt templates will have a Content-Type: header specifying the character set. Thus, I don't see why the BOM would ever be needed.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 2011-03-02, at 2:38 , Mark Sapiro wrote:
Thank your for your response, Mark. I haven't been able to figure out how to access mm_cfg.py on my web hosting service - I suspect it's not at all accessible to me. I've requested dreamhost.com to make the change. Would changing to the iso-8859 option impact other users at dreamhost?
Henry
Henry Olders wrote:
Thank your for your response, Mark. I haven't been able to figure out how to access mm_cfg.py on my web hosting service - I suspect it's not at all accessible to me.
I'm sure that's correct since changes to mm_cfg.py are global and can be fatal if mistakes are made.
I've requested dreamhost.com to make the change. Would changing to the iso-8859 option impact other users at dreamhost?
It shouldn't have any negative effects, but it will have effects on the Content-Transfer-Encoding: of Mailman generated messages. I.e. it could cause messages which were previously unencoded to be quoted-printable (or in the case of utf-8 rather than iso-8859-1, base64) encoded. This could be visible to users with primitive MUAs.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Henry Olders wrote:
What I would like would be a way to set mailman to NOT strip out accented characters when english is set as the default language.
Add one of the following lines to mm_cfg.py depending on your preferred character set
add_language('en', 'English (USA)','utf-8')
or
add_language('en', 'English (USA)','iso-8859-1')
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Christian Mack wrote:
Why would this be true? Quoting from section 2.6 of the Unicode 5.0 standard <http://www.unicode.org/versions/Unicode5.0.0/ch02.pdf#G19273>:
Use of a BOM is neither required nor recommended for UTF-8, but may be encountered in contexts where UTF-8 data is converted from other encoding forms that use a BOM or where the BOM is used as a UTF-8 signature.
I would expect that one would only choose utf-8 as the character set for english in an environment where the web server's default character set is utf-8, and emails built from .txt templates will have a Content-Type: header specifying the character set. Thus, I don't see why the BOM would ever be needed.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 2011-03-02, at 2:38 , Mark Sapiro wrote:
Thank your for your response, Mark. I haven't been able to figure out how to access mm_cfg.py on my web hosting service - I suspect it's not at all accessible to me. I've requested dreamhost.com to make the change. Would changing to the iso-8859 option impact other users at dreamhost?
Henry
Henry Olders wrote:
Thank your for your response, Mark. I haven't been able to figure out how to access mm_cfg.py on my web hosting service - I suspect it's not at all accessible to me.
I'm sure that's correct since changes to mm_cfg.py are global and can be fatal if mistakes are made.
I've requested dreamhost.com to make the change. Would changing to the iso-8859 option impact other users at dreamhost?
It shouldn't have any negative effects, but it will have effects on the Content-Transfer-Encoding: of Mailman generated messages. I.e. it could cause messages which were previously unencoded to be quoted-printable (or in the case of utf-8 rather than iso-8859-1, base64) encoded. This could be visible to users with primitive MUAs.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (3)
-
Henry Olders -
Mailman Admin -
Mark Sapiro