Red Hat Bugzilla – Bug 146730
Mailman annals in iso-8859-1, apache default charset utf-8
Last modified: 2007-11-30 17:10:59 EST
Description of problem:
Annals show wrong here, as they are stored in iso-8859-1, but apache announces
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Send a latin-1 message to a mailing list
2. Look it up in the annals
Accented characters show wrongly
I'm confused by your assertion that the archives are stored in
iso-8859-1 (e.g. latin-1). Using the default archiver that comes with
mailman HyperArch, everything is converted to unicode.
I tested by sending a iso-8859-1 to a test list, it was properly
converted to unicode, the meta tag was UTF-8, and apache sent the
encoding in the HTML header as UTF-8, and the latin-1 message was
properly displayed (I tested with character 0xA9, copyright).
If you still believe there is a problem then please attach (not in the
comment section) the full source including all headers of the latin-1
message as received directly (not via the mailman list, e.g. sent to
the list and cc yourself), and the html page source from the brower
displayed archive message.
By any chance do you have your list set to perform language
translations? If so what language?
I have the same problem with RHEL4. And i don't think it has something to do
with the messages themselves. Since part of the footer "Mas informaciÃ³n..." or
"PrÃ³ximo mensaje" (spanish) is displayed wrong (in iso-8859-1 when the page
encoding is utf-8),
Note, this only happens when i use spanish as a default language for a mailing
list, for english lists, utf-8 is displayed with no problems. So I guess, the
header should be changed to iso-8859-1 when spanish is used.
I know it's not FC3, but i guess it's the same problem.
(This is a mass update to bugs which have been in NEEDINFO unmodified for over a
year and are for a currently unsupported version of Fedora Core.)
Closing per lack of response to previous request for information.
This bug was originally filed against a much earlier version of Fedora
Core, and significant changes have taken place since the last version
for which this bug is confirmed.
Note that FC3 and FC4 are supported by Fedora Legacy for security
fixes only. Please install a still supported version and retest. If
it still occurs on FC5 or FC6, please reopen and assign to the correct
version. Otherwise, if this a security issue, please change the
product to Fedora Legacy. Thanks, and we are sorry that we did not
get to this bug earlier.