On Thu, 06 May 2004 07:18:31 -0400 Sam Varshavchik <[EMAIL PROTECTED]> wrote:
> 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. Sometimes adding new charset costs much. For example: JIS X 0213 (ISO-2022-JP-3 etc.) will be used for a language of indigenous people in Japan. However, it is a superset of JIS X 0208 (ISO-2022-JP etc.) and adds over 4000 charater maps. I think an inexpensive alternative to adding charsets is encoding text off-line and upload it as inline text/plain attachment. This workaround will also reduce update works caused only by addition of charset support, even if it's a small charset (such as VISCII). How about this idea? > 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. OK. I'll not consider about non-Unicode configuration so much. --- nezumi
