Daniel Higgins writes:
somehow, something happened to sqwebmail's 8bit support between
0.44.2.20040112 and 0.45.3.
every extended characters now appears as a losange in mozilla (ï) or
percent in internet explorer. pasting the characters in a shell i get
\x{FFFD} if that can help. the english template looks fine, but my
french translation has these. the only configuration i can find is
LC_ALL in courierd (it is set to en_US, which usually supports all the
8bits characters i need)
any idea? a new configuration i overlooked maybe? it worked fine before
This is why I like to often cite
http://www.catb.org/~esr/faqs/smart-questions.html.
â8 bit supportâ covers a lot of ground. It's a fairly generic description
that can apply to a wide range of subjects. For example, one very plausible
way to interpret your question is that you're saying that something wrong
happens when sqwebmail displays contents of messages that contain 8-bit
text.
As it is, that's obviously not the case. It took me a while to understand
that what you're really saying is that you've modified the template files to
include text with 8-bit iso-8859-1 characters, and that they are no longer
correctly shown in a web browser.
sqwebmail now detects which character sets are supported by the browser, and
if the browser understands UTF-8 sqwebmail will set the character set to
UTF-8. If the web browser does not support UTF-8 sqwebmail will fall back
to ISO-8859-1.
This is possible only because the default HTML templates use only the 7-bit
US-ASCII subset and, as such, can be sent either in the UTF-8 or ISO-8859-1
encoding.
Because you have ISO-8859-1 characters in your template files, you need to
remove UTF-8 from /usr/local/share/sqwebmail/CHARSET, leaving only
ISO-8859-1.
However, I suggest that you do it the other way around. Use iconv to
convert your ISO-8859-1 text to UTF-8, then remove ISO-8859-1 from the
CHARSET file, leaving only UTF-8.
pgp00000.pgp
Description: PGP signature
