Libmime to generate a meta-tagged html to the html parser. Currently, we can only view mails of us-ascii. Originally, i18n eng. was trying to enable the charset menu but it's not available (#2341). Proposed change is to put a meta-tag (for iso-2022-jp) only if the system code page is 932 (Japan). Post dog food, we should generate a utf-8 html (so always put a meta-tag as utf-8) or Rich may have idea.

Need a temporary hack for the Dog Food M3 build in order to enable QA to test reading Japanese email. Originally bug 2341 "[I18n]No encoding menu." was planned for M3, but it may require a change to the nsParser::Parse interface, so we have post-poned it until after M3.

changing qa contact from lchiang to msanz for reassignment.

This is the diff file for the proposed change. Index: mimehdrs.c =================================================================== RCS file: /cvsroot/mozilla/mailnews/mime/src/mimehdrs.c,v retrieving revision 1.6 diff -c -r1.6 mimehdrs.c *** mimehdrs.c 1999/02/11 00:43:20 1.6 --- mimehdrs.c 1999/03/15 22:01:49 *************** *** 2361,2366 **** --- 2361,2375 ---- status = MimeHeaders_grow_obuffer (hdrs, /*210*/ 750); if (status < 0) return status; + #if XP_PC + // For the dog food only. Post dog food should be always utf-8. + #include <windows.h> + #define MHTML_META_TAG "<meta http-equiv=\"Content-Type\" content=\"text/html; charset=iso-2022-jp\">" + if (GetACP() == 932) { + status = MimeHeaders_write(opt, MHTML_META_TAG, PL_strlen(MHTML_META_TAG)); + } + #endif + /* * First, let's import some style sheet information and * JavaScript!

The change checked in,reviewed by rhp, approved by chofmann.

reassigning QA contact to momoi

** checked with 3/19/99 M3 final candiadte build ** For both browsing and mail display, the temporary workaround is to: 1. Use the system charset as the reference for font selection in display. Under a Japanese Windows, apprunner/viewer will use whateevr is specified in the prefs.js as Japanese fonts. Under US Windows, it will use the default 8859-1 fonts. This workaround has been confirmed to work for the above build.