Re: content encoding etc.

Hatuka*nezumi - IKEDA Soji writes:

> Although preferred encoding method etc. depend on charset,
> mono-lingual (-charset) configuration (*) won't link unicode
> library.
> 
> (*) And charsets of HTTP content and outgoing message are identical
>   (See Ichikawa's recommendation).
> 
> And generally, text/* attachments can be of charsets not listed 
> in unicode/charsetlist.c (I've not work on this problem yet).
> So rfc2045/rfc2045charsetinfo.c lists unsupported charsets too.

The unicode list includes most common character sets in use.  The 
unsupported charsets are rarely seen, and in any case if their Unicode map 
is known they can simply be added.

Mono-lingual, non-unicode configuration are only useful with traditional 
ISO-8859-based environments.  In all other cases you need unicode support in 
order for sqwebmail to be useful.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQBAmh8Hx9p3GYHlUOIRAtlRAJ45QWlMzqLZ/kQMiXfAl6WDfHccCgCfQ6Wm
j/HjoAmER0+dueJcEJl+a+8=
=uGlX
-----END PGP SIGNATURE-----