You are currently viewing a snapshot of taken on April 21, 2008. Most of this content is highly out of date (some pages haven't been updated since the project began in 1998) and exists for historical purposes only. If there are any pages on this archive site that you think should be added back to, please file a bug.

International M13 Status Page

by Katsuhiko Momoi
Last Update: 2/1/99

This page tracks the progress of M13 International features.  By the time M13 is completed, this page should have all the completed M13 features and testing hints. If you are interested in what has been completed in the prior Milestone, visit the M12 international status and testing hints page.

M13 International features that have been completed:


I18n Engineering and Milestone Tasks document is available here.
I18n Beta 1 Feature Plan is available here.
I18n Beta 1 Mail/News Functional specifications are available here.
Localizing Mozilla document.
A list of Non-English Mozilla Mail lists and Discussion groups is here.
Bitstream Cyberbit Unicode font for Windows  (version 2.0) is available here. Read READMEFirst file for details before downloading the fonts.
Report international bugs: Use Bugzilla.
Questions and comments:
    Note: The name of the executable is mozilla. (At one point during the development, it was apprunner.exe.)


  • The Mac installer for the M13 binary could be very slow compared to Windows and Unix builds -- please be patient.
  • There is very little need to directly edit Preferences file, prefs.js.  Both profile migration and new profile creation are very easy to accomplish with the improved Profile Manager. Users who have had trouble setting up Mail server(s) before should try Edit | Account Setup menu available in the Messenger window.
  • Mozilla can migrate Communicator 4.x profiles you have on your system. Choose an existing one made by 4.x from the list and a new one will be created for Mozilla.
    • The window for profile migration will appear the first time you start a new Mozilla build after the installation.
    • If it does not, you can start with the profile manager: mozilla -installer (Unix & Win).  Mac users can start with the Mozilla Profile Manager file.
  • If you have used an earlier version of Mozilla, we recommend that you delete the file called mozregistry.dat (Win)/Mozilla registry (Mac)/registry (Unix) before you run M13 Mozilla. (Don't delete Netscape Registryfile for Mac, which is for Communicator 4.x.). We recommend this procedure because during an earlier Milestone, i.e. M10, there has been a change in the way registry works and the old registry prior to M9 will not work well with builds later than M9. Read the section in the Release Notes called Files Used or Created to find out where you can find these files.
  • When you start M13 after having deleted mozregistry.dat or registry, you will be asked to create a new profile. If you name an existing profile, that profile will be used. Otherwise "Default" profile called "mozProfile" will be created. If this latter happens, you can replace the prefs.js file in the Default folder with the one from an existing profile directory. (Note that the default profile name changed from prefs50.js (of M8 and earlier) to prefs.js starting with M9.)
  • Note on non-ASCII path names: For both Profile manager and Mail/News Account setup manager, it would be best to avoid choosing folder or path names which contain non-ASCII characters at this point. Internationalization of these is not complete yet. (Mail/News Account names in non-ASCII display OK, however.)
  • Also read the Installation instructions for your platform carefully in this Release Notes.
  • Performance: Generally speaking, M13 should be quite usable as as a daily browser for international users. Note some of the bugs described in this section, however.
  • Copy/Paste: Copy/Paste operation of non-ASCII data is working more or less well in M13 within Mozilla with the exception of Mac which currently has a problem of copying from the Browser window. See below in the Editor section for details.
  • Window Title display of non-ASCII: Due to a dependency on platform specific widgets, currently Mozilla cannot display Window titles (Browser, Editor, Messenger, etc.) if they contain non-ASCII characters not supported by the operating system. For example, Korean titles will display OK under Korean OSs but not under Japanese Windows, etc.
  • Sidebar: You should be able to display non-ASCII names here, e.g. Related sites. Sometimes display of non-ASCII names may be corrupt. There are a few bugs on this problem. See Bugs 24557, 24933.
  • Bookmarks: Bookmarks titles support non-ASCII characters. (Note: IE favorites are not imported correctly yet and will not display non-ASCII characters well. See Bug 6770.)
  • Accept-Language: Backend work for Accept-Language was completed in M13. The Pref UI is not done yet but Mozilla now sends out Accept-Language values in an HHTP header when the following line exists in prefs.js: e.g.  user_pref("intl.accept_languages", "ja,en"); . The language values (ja and en in the formula) should be from ISO-639-1.
  • Font Preferences: Backend work for font preferences was completed back in M12. The UI for font preferences now also exists in M13. Changing fonts through the pref UI does not work yet, however -- we expect this work to be completed in M14.  In the meantime, font names and sizes can be manipulated by editing prefs.js file for all platforms -- in M12, this worked only for Windows.  Here are some highlights of new font preferences at M13. Font work is not finished yet and some of these specs might change later.
    • The font preferences can now be set for 5 generic font families: serif, sans-serif, monospace, cursive and fantasy
      • Mozilla does not map non-generic font family names such as "Times", "Courier", and "Arial" to corresponding CJK fonts. Web page designers should use generic font names if this is the desired result.
    • The font preferences are in principle set for language/script groups (except for Unicode) rather than for charsets as was done in Communicator 4.x.
    • The font size can be set for: variable or fixed.
      • variable setting only controls the default HTML display which is set by the following line:
        • user_pref("font.default", "sans-serif");  -- serif should be the default and this probably does not have to be set unless you want to change the HTML display default to sans-serif type. The 2 values most often used for this HTML display default would be serif or sans-serif.
      • fixed setting only affects monospace font setting. e.g. mail message viewing.
      • The font sizes are measured in pixels rather than in points.
    • These preferences will be consulted to select fonts to use in case the page you are visiting does not have fonts specified.
    • Non-ASCII font names are also supported. We don't have the UI working yet for setting fonts but you can play with non-ASCII font names and font sizes by editing prefs.js. Be careful, however, because prefs.js must be in UTF-8 if it contains any non-ASCII characters. UTF-8 editor is hard to find. Japanese font names are known to work on Japanese Windows95/98/NT4 and on Macintosh. Font names to use are the same ones found in Control Panel | Fonts for Windows, Key Caps utility for Mac, and the font family name for Unix as indicated by the red bold type in this example. Font names can also contain spaces.:

    • -adobe-courier-medium-o-normal-0-0-75-m-0-iso8859-1

    • Help us by trying out the Korean and Chinese font names under the respective language operating systems. Below is an illustration on how you might edit prefs.js for font preferences on Japanese Windows. The key point is that if prefs.js contains non-ASCII characters, it must be encoded in UTF-8.:
      • Find your current  prefs.js file, and make a backup copy, then rename the original prefs.js to something like jpprefs.txt.
      • Using a text editor like NotePad, edit jpprefs.txt with the following templates for font names and sizes:
        • user_pref("", "Font_name_in_JPN");    -- You can set fonts for each of the 5 font types mentioned below.
        • user_pref("font.size.variable.ja", 12);  -- sizes are in pixels.  This controls HTML default display.
        • user_pref("font.size.fixed.ja", 12); -- sizes are in pixels.  This controls monospace display such as <pre>.. </pre> text or Plain Text Mail message display.
          • Possible font types: serif, sans-serif, monospace, cursive and fantasy.
          • Possible language groups are: ja, zh-TW, ko, zh-CN, x-western, x-central-euro, x-cyrillic, el, tr, x-unicode, zh-TW
          • Possible font size categories: variable, fixed.
          • Possible font size: integer in pixels.
        • For mail message viewing, due to Bug 26182, the font types and sizes are currently controlled by x-unicode setting only rather than based on the language of the message in view. For example,
          • user_pref("", "Font_name_in_JPN"); --> for HTML message display
          • user_pref("", "Font_name_in_JPN"); --> for Plain Text message display
        • When inserting font names in Japanese, pay special attention to how the font names are spelled -- is the alphabet part using full-width Roman? Is the space half-width or full-width? You can see how the font names are written by looking in the Windows Control Panel's Font utility program.
        • You can also set the screen resolution with the following type of preference item in prefs.js file.
          • user_pref("browser.screen_resolution", 120);
      • Now that you have edited jpprefs.txt using Japanese font names, you should convert the encoding to UTF-8 using the following command line utility shipped with Mozilla (Win and Unix only) in the same directory as the mozilla executable. See below on details of how to use the conversion utility.
        • nsconv -f Shift_JIS -t UTF-8  jpprefs.txt prefs.js
          • Note: nsconv does not replace an existing file of the same name -- that's why you should rename the original prefs.js to something else first.
        • Now Mozilla can read the Japanese font names you specified and reflect your choice.
      • Any additional Japanese editing should be done on jpprefs.txt only. Then the conversion utility should be used to get the UTF-8 version of it -- unless you have an editor which can handle UTF-8 data directly. Note: On Windows 2000 (currently Beta), editing utilities should be able to save data into UTF-8. If you know of other such editors, please write to me and tell me about it.
      • None of these hand-editing would be needed when the font UI is done, which should be coming in M14.
      • Unix font display problem and future directions:
        • Currently the code bases the "line height" always on the Latin 1 font height. Since other language fonts (e.g. Japanese) could be larger than the Latin-1 fonts on Unix, lines look too close together and even overlap in some cases. These effects are visible in both UI and HTML display. In the near future, we will be making a change in such a way as to base the line height based on the language of the text being displayed. This means that the line height needs to grow when dealing with Japanese texts, for example. This should improve the situation considerably.

  • Big 5 fonts on Unix:
    • It is now possible to use Big5 fonts with the suffix
    • Fixed!: Big 5 fonts and Japanese Kana display on Unix: In M12, when you have Big5 fonts like Taipei on your Unix system, due to a Big5 converter table error, it led to non-display of Japanese Kana characters. This Bug 21209 was fixed in M13.
  • Form: Form submission of non-ASCII data is working generally.
    • Fixed!: Multipart file upload is now working in M13 --> Bug 8209.
    • Fixed!: If a web page form uses JavaScript and escape() function on form input data, at M12 JS returned unicode data instead of the charset which matches the web page. This led to incorrect data submission and failure of search. Bug 22594.
    • There is a bug which shows only blank for non-ASCII data input when the Back button is pressed on the page which resulted by submitting form data. Cf. Bug 22580.
  • GFX widget/Ender is ON by default. This means that all input areas in M13 support non-ASCII character input including input using CJK IMEs. Read the Editor section below for more information.
  • M13 converter(s): There are no new converters in M13.  See here for a list of all the converters at M13.
    • Unix charset testing:  As mentioned in the M7 Release Notes, the display for the supported charsets except Armenian, Thai, and Vietnamese should be working.  We would like users to continue to look at various Unix charsets and file a bug if a problem is found. The list of the supported charsets at M13 can be found below. Please download the Unix binary and check out our support for these character sets. (Note: You need appropriate fonts to display these languages -- pcf.gz format on Linux. Visit this site for ISO and Cyrillic BDF fonts, and this site for multi-byte language fonts. If you want to get the entire international font set, try one directory above for this file, intlfonts-1.2.tar.gz . For converting from BDF to PCF format fonts, use bdftopcf utility. Once installed you need to update the fontsdir, i.e. mkfontdir, and then rehash the font path, i.e. xset +fp `pwd` .)
  • View | Character Set menu:
    • Note: The current Character Set menus (including the name of the menu itself) are temporary and will be replaced in M14 by a new single dynamic menu. The new menu specs for the Browser have been published here. The name "Character Set" will also be replaced by "Character Coding". At M13, much work has been completed -- according to the specs above --  to make the Character Coding menu dynamic, customizable, and eventually accommodate new Character sets via a plug-in directory. The dynamic Character Coding menu will use the Extensibility Model as discussed in this document.
    • You will notice that there are 7 Character Set Menus in the Browser window, and 6 in Composer/Editor and Messenger.
    • The first 6 "static" menus with sub-titles such as "ISO" constitute a temporary workaround for long, non-customizable and non-scrollable menu.
    • The 7th Character Set menu -- found only in the Browser window -- is the dynamic menu which is under development but will replace the workaround menu in M14. This is the same menu as the first 6 put together. It does not scroll under Linux and Windows and so you cannot probably see the whole list except on Mac, but the dynamic menu is created via a script and it will be customizable.
    • Both types of  menus should work in M13 and one of them is actually redundant. This is harmless, however. Character set menus in other components are still static at this point and you will not see the dynamic menu.
  • View | Character Set menu usage:
    • You can switch to different Character set upon encountering a page which does not have a  meta charset tag and which is not displaying correctly. If you happen to have a charset detector ON and if the display is failing, you need to first turn OFF the detector setting, and then try the Character Set menu. Otherwise, the charset detector's choice will always predominate over the manual menu selection. You will not see a checkmark next to the menu item yet, however.
  • Charset detection modules in the Browser Menu.
    • The charset detection modules for Chinese, Japanese, Korean, East Asian (CJK), Chinese (Simplified & Traditional Chinese), Ukrainian, and Russian are in a menu below the Character Set menu.
      • Russian & Ukrainian: Crashing bugs reported for Russian and Ukrainian auto-detection have been fixed in M13.  Cf. Bugs 17094 & 17103 -- both fixed in M13.  )
    • You can select 1 charset detection module at a time. Once selected, the auto detection for the charsets of  language(s) you selected will be ON until you turn it OFF.
    • The charset detector will be engaged even when you have selected a Character Set explicitly via the Character Set menu. If you need to override the effect of the charset detector in effect, choose OFF, and then select a new Character Set from the Character Set menu. Please use the charset detector feature for a variety of web pages in the languages of your choice and let us know how we are doing. File a bug at Bugzilla or send your comments to netscape.public.mozilla.i18n or
    • Until M10, these charset detectors could be used only by prefs.js settings. This is no longer necessary since the charset detector menu fulfills exactly the same function.  The menu now controls what gets inserted into chardet_name of:
      user_pref("intl.charset.detector", "chardet_name");
      If the charset detector is OFF, then chardet_name value will be empty. As reported before, unit testing also can be done via a utility called "Detectch.exe" found in the same directory as the "mozilla.exe" file. If you are interested in modifying the prefs.js for charset detector modules or use the command line utility, read the usage instruction here.
  • HTTP charset: Mozilla supports server-generated HTTP charset correctly. (The order of priority is: HTTP charset > Document Meta Charset > Browser Menu choice.)
  • View | Page Source: works only partially for different charsets.
    • It works OK:
      • if the page has a correct server-generated HTTP charset or document-based Meta charset associated with it
    • In other cases, there are failures of correct display. They fall under 2 types of cases:
      • The page has been correctly loaded with the use of a charset detector --> the source view will load but may not correctly display characters.
      • When none of the conditions above holds and the user has loaded the page correctly with the manual change of the Character Set menu --> the source view will load but may not correctly display characters.
  • CJK line breaking: Mozilla's line breaking implements specifications found in JIS X 4501 with some additional modifications. Read this news article posted to the newsgroup netscape.public.mozilla.i18n by Frank Tang for details.
  • CJK basic printing: should be working on M13 on Windows and Mac. Not verified to be working on Linux -- probably not.
  • Mac: Baltic display:
    • ISO-8859-13: You may experience a problem in Baltic ISO-8859-13 display in that some of the uppercase characters may be missing the diacritical marks above them showing only the base characters.  See Bug 9165.
      • One Workaround:
        • 1) Install a Central European script bundle (CE) from this Apple file. (You need DiskCopy utility to mount this image). After you mount this disk image, rather than using the Installer, open the System file directory by double-clicking on it. In it, you will find among others, CE (script), Slovak (keyboard layout), and slovensk (keyboard layout). Drag these files to your current System Folder. Mac OS will then place them in the right places.
        • 2) Next, get the fonts for Central European from this Apple file. Once you mount this image file with DiskCopy, you will find a number of CE fonts. Drag and drop them onto your System Folder. Mac OS will then place them in an appropriate folder.
        • 3) After steps 1 and 2 are completed, re-start your Mac. You should now see ISO-8859-13 (also ISO-8859-4) characters correctly.
    • Central European ISO-8859-2 display: There seems to be a Mac bug -- some 8-bit range characters display as "?" even though a correct font exists on the system. See Bug 18095.
  • Java: Java Plug-ins on Windows. Java plugins probably are not be working on M13. The main reason is that Mozilla APIs sometimes get out of synch with published JRE/JDK plugins. For example, JDK/JRE1.3 plugins don't seem to operate with M13. See Bug 24487 to keep track of Mozilla and Java Plugins for M14. The following instructions are general setup steps for Java Plugins. When Mozilla APIs are in synch with JDK/JRE plugins, you can use these steps to activate Java.
    • To get Java working on Mozilla, if the installer gives an option to install a JRE package, the following steps will be taken care of automatically. If you choose not to use the installer, or the package you selected does not give you such an option (e.g. the JRE package is not currently included in Mozilla distribution), or if you want upgrade the Java plugins yourself, you need to take some extra steps as described below.
      • First get the International version of  JRE 1.2.2 or later from Javasoft. We recommend using JRE1.3 (Beta at this point) for improved Java support. JRE packages are distributed for JDK releases and Beta version downloading requires registration first. Install the package on your Windows. We find that JRE 1.3 Beta can run more applets than JRE 1.2.2 plugin files and are therefore recommended. Plugin files are also much smaller in size in the latter version.
        • Note to CJK Windows 95/8 users: If you want to use Java on these Asian Windows 95/98, you must get the international version of JRE which has i18n.jar file needed for conversion from native charsets to Unicode -- otherwise, Mozilla will crash when trying to start. NT4 users will have no crash of this type. If you are CJK Win95/98 users and are not using the international version of JRE and are experiencing startup crashes, then remove the 3 .dll files from the plugins directory and live without Java until an international version of JRE is installed. See discussion in Bug 21305 for details.
      • Create a directory named plugins in the same directory where the mozilla.exe resides.
      • Copy 3 files, npjava11.dll, npjava12.dll, and npjava13.dll, from the JRE's bin directory into the plugins directory you created in step 2.
      • (This part should be optional since Mozilla searches for plugins automatically.) If you have Java Plug-in Control Panel, you can check this from Windows Start | Program menu. The following settings (no others) should be checked.
        • Basic: Java Plugin, Java Console (optional), Cache Jar in memory
        • Detailed/Advanced: Use Java Plugin as default, Just in time Compiler is on
        • Proxy: use the browser setting
        • Certificates: (none)
    • Due to a few bugs, some applets simply will not run. Some string display applets do run and so far we have found none can actually display non-ASCII strings. See Bug 17169. If you have specific applets which deal with string display, write your finding to
Editor: For IME specifications, see this document by Tague Griffith. (Current editor i18n engineers are Frank Tang & Erik van der Poel.)
  • General: At M13, Editor is now quite usable for a variety of languages both in HTML composer and Plain Text editor (Mail included).
  • Global IME on Windows: is supported starting in M13 thanks to a contribution from Makoto Kato <> and integration work by Frank Tang <>. Include these 2 people in all bugs related to Global IME.
    • A Global IME module is an add-on for all language versions of  Windows 95/98/NT4. There are 4 Global IME modules (Chinese-Simplified, Chinese-Traditional, Korean, and Japanese). They can be downloaded from a Microsoft downloading site. Once installed, you can input in these languages (CJK) under any non-CJK language Windows versions. These modules also enable CJK Windows users to input in languages not supported by their operating system. For example, Japanese Windows users can install Chinese and Korean modules, etc. However, you should never install a Global IME for a language which is already covered by your OS. For example, do not install Japanese Global IME on Japanese Windows. Windows 2000 comes with options to install improved CJK IMEs. Therefore, users of Windows 2000 should not use these add-ons meant for other Windows.
    • You can install either a Global IME module by itself or a Global IME with a matching Windows font for that language. The latter is called Global IME with Language Pack. We recommend getting the Global IMEs with Language Pack. Visit this site, read the explanation, and download the modules you like. These Global IME packages will also install usage documentation under Start | Program | Microsoft Global IME.
  • Copy/paste now I18n-friendly: Basic intra-application copy/paste is now working in all areas of Mozilla for non-ASCII strings. You can copy from Browser or Messenger viewing window and paste into all Edit fields within the application. This should work for all languages we cover at present. (Macintosh does not allow you to copy from Browser window and there seem to be other problems still left in intra-application copy/paste.) Note: The inter-application copy/paste is working partially in M13 -- the status varies from platform to platform. See below for more.
    • You can copy/cut and paste within the same application
      • within the same same text area
      • from one text area to another text area (e.g. from HTML to Plain Text editor text area)
      • from one text field to another text area under HTML Mail Composer (e.g. from Mail compose subject header to body text area)
      • from a viewing window (e.g. Browser) to text Edit field (e.g. form, Editor, Mail composer, etc.)
    • Known bugs: Copy/cut and paste for non-ASCII string is not working in the following inter-application cases. These cases are being worked on and we should get most of this resolved in M14. See 8427 for details. The following paints a general idea of where copy/paste may not be working currently. Generally speaking, some of this is working on Windows but not usually on Mac or Unix. Mac currently lacks support for Unicode clipboard and this is part of the problem. Cf. Bug 10816.
      • From Mozilla to another application -- if the other application does not support Unicode clipboard in the target Edit field. (Note: It does not help the matter if the platform does not support Unicode clipboard, e.g. Win95/98.) On Mac and Unix, this function seems to be generally broken.
      • From another application to Mozilla -- if the platform does not support Unicode clipboard. This should work on WinNT4/2000 but probably will run into a problem Win95/98 in some cases. On Mac and Unix, this function is probably not working at all for non-ASCII data. The general bug to deal with this problem on all platforms is Bug 24010.
  • Saving with Editor Character Set menu: On a new document, change the encoding to the one you would like to save the document in and then use the File | Save as  menu to save the edited document in that character set. Bugs or comments to: Bugzilla or Here are some known bugs.
    • Now the document will be saved in a charset you specify via the Character Set menu. (Note: This behavior will change when the International Editor UI specs are implemented.)
    • Currently this menu does not reload a document. It can only be used to save a document into a different charset at the save time. This menu will be re-worked extensively later.
  • Basic IME support on Unix: We test Japanese input under Red Hat 6.0 + kinput2 + wnn4 + glibc-2.1.1-6. We need your help on testing other Unix platforms and other language IMEs!
  • Help test (Japanese) IME on Unix!: We need the following kinds of testing for Japanese IME  and others on Unix. Please send your comments to netscape.public.mozilla.i18n or file a bug using Bugzilla Bug Management System for Mozilla.
    • Testing on other platforms -- our reference platform is Red Hat 6.0.
    • Testing other XIM-based Japanese IMEs (both public domain and commercial ones such as Wnn6+xwnmo) to see how we are doing. We used kinput2 + wnn4 as our testing environment. We need input from people using other IMEs and servers. Write to us also if you can confirm other IMEs are working. If there are special conditions to be followed, include that information also.
  • Chinese and Korean IMEs on Unix: We would also like to hear from users of IMEs for Chinese and Korean IMEs. Write to: netscape.public.mozilla.i18n about your findings.
      • So far we have received reports that XCIN for Traditional Chinese works with Mozilla. For XCIN, see this English page for more info.
      • Also internally we could get one Korean IME to work. For Korean XIME general info, visit this English page by Jungshik Shin. For hanIM specific info, visit this Korean page.
  • CJK IME bug status:
    • On all platforms:
      • We don't see any major crashing bugs at M13.
      • Most  major bugs in basic operations of CJK IMEs have been fixed but there are some smaller bugs. They should be suitable for fairly heavy use now. Here are some of the current IME bugs.
    • On Unix: Unix IME is in fairly good shape though bugs remain but it is quite usable in M13.
      • Some bugs which had to do with the positioning of IME status window have been fixed.  Cf. Bug 22326.
  • Form Password field input bug:
    • Due to a bug, the form password input is not concealed completely when you engage CJK IMEs -- you can bring up the conversion candidate window and see what characters you are typing. To avoid this bug, turn off the IME and then input a password. Only this mode will work OK for the password field. The Half-width Alphanumeric mode (e.g. Japanese IME) normally works like the direct input mode but for this bug, it is not effective and reveals the input when the candidate window is brought up. Only ASCII input mode should be available in this field. See Bug 16940 for details.
  • ALT + NumPad Latin 1 input bug:
    • M13 has an annoying bug in Editor and Mail Composer where if you use ALT + NUM Pad to input Latin 1 accented characters, the input character gets placed one position to the left of the final position. It is also difficult to input Latin 1 accented characters consecutively using ALT+NUMPad method. See Bugs 22206 and 25280.
  • Notable bug fixes:
    • CJK IME force commit function has been enabled in some areas. For example, choosing a style menu item or inserting the cursor into other parts of the edit field will force commit, or clicking on a submit button in form.
    • AltGr combination should now work for international keyboards. There is one glitch remaining -- i.e. a menu will open if the key you happening to be using with AltGr key is also a menu shortcut key. Bug 9333.
    • XIME status window refreshes its position now as new input is made.
  • Filing Editor bugs. If you are filing editing related bugs, please CC the following people depending on the category of bugs you are reporting:
    • For all the Window keyboard input/ IME related bugs, add
      •,,, to the CC list
    • For all the Mac keyboard input/ IME related bugs, add
      •,,, to the CC list
    • For all the Linux keyboard input/ IME related bugs, add
      •,,,, to the CC list
    • For all the cross-platform keyboard input/ IME related bugs, add
      •,,,,, to the CC list
  • Summary of what has been enabled up to M 13:
    • CJK IMEs on Windows, Mac and Unix.
    • CJK force commit is functional in some areas -- there are some more tasks to be done.
    • Keyboard support for many one-byte languages on Windows: Please file a bug if you find a problem in your language or keyboard.
    • Keyboard support for many one-byte languages on Mac: Roman Australian,  Brazilian, British, Canadian-CSA, Canadian-ISO, Canadian-French, Dutch, dv-Dvorak, dq-Dvorak-Qwerty, Finnish, Flemish, French, French-numerical, German, Italian, Norwegian, Spanish, Spanish-ISO, Swedish, Swiss French, Swiss German, Cyrillic Bulgarian, Cyrillic-Qwerty, Russian, Ukrainian.
  • General: One of the key features of Mozilla is that it is relatively easy to localize menus and dialogs UI into any language. See the framework section below for a brief discussion of guidelines. Commercial browsers don't often get localized into languages with smaller number of speakers. If you want to see a fast, next generation browser in your own language, Mozilla offers a great chance to make it a reality.
  • Voluntary localization projects: Currently 17 voluntary language projects are going and more are likely to join. If you're interested in localizing Mozilla into your favorite language, this page explains it all. Current projects are: Bosnia, Brazilian, Catalan, Czech, Danish, French, Georgian, German, Greek, Hawaiian, Indonesian, Japanese, Norwegian (nynorsk), Polish, Spanish (es-CO), Spanish (es-ES), and Thai. Some of them already have published M13 kits. Check out the Mozilla L10n How-to Page.
  • Localization framework:
    • We have published a guideline for localization. Anyone interested in localizing Mozilla into another language should read this document carefully.
    • Here are some basic ideas to keep in mind when localizing Mozilla. For translating the entire Mozilla, you should read this document and do it in an organized way using leveraging tools to synch up from earlier versions. You might follow the following steps when doing a quick translation work of a few phrases.
      • Do not localize .xul files directly. All localizations must take place in corresponding  .dtd files or .property files.
      • Localizable strings have now been extracted from .xul into .dtd and .property files. The these files are found under  ../chrome/component_name/locale/en-US directory. They match the names of the corresponding .xul files which are placed under:../chrome/component_name/content/defaultdirectory.
      • Translators need not worry about this, but if you create a .xul file then you need to extract localizable string into a corresponding .dtd or .property file. (If you're creating Mozilla UI via a script rather than by a static .xul file, then you need to extract them into a property file.) To extract .XUL entities into DTD files for localization, read this document.
      • Mozilla assumes the default charset of all .dtd files to be in UTF-8, and all .property files to be in escaped Unicode. If you change UI strings to your language using non-ASCII data, they should show OK as long as they use the appropriate Unicode encoding format. (You can change menus to Japanese, for example, in file using the method suggested above and then convert the DTD file to UTF-8.)
      • All non-ASCII .dtd files must be in UTF-8 encoding and .property files in escaped Unicode -- these are Mozilla's default encodings for the resource files. You do not need to explicitly mark the resource files with these encodings, Mozilla will assume that they are in UTF-8 or escaped Unicode even if there are no charset tags.
      • Using a localized version under an operating system for another language: Some parts of  Mozilla are dependent on the operating system widgets for display. This means that there will be some areas (e.g. some part of dialogs, window title, etc.) which will not display correctly if you use, for example, a Japanized version under English Windows.
      • In summary:
        • It is best to use localization tools and methodologies mentioned on this page. If you want to do a quick and dirty translation on a few strings for a demo, you should keep the above steps in mind.
      • UTF-8/escaped Unicode conversion utility:
        • Use convenient converter utilities such as "uniconv" (for Windows and Unix) or "native2ascii" utility included in the latest JDK.
        • Mozilla's nsconv conversion utility has been enhanced by ""-- it now supports charset aliases: The original nsconv is by the courtesy of Frank Tang. nsconv is installed in the same directory as your mozilla executable. You can use any encoding names recognizable by Mozilla and their aliases checked into the source in using this utility. Here's the basic command line for using this utility:
          • Usage schema --any one of the following:
            • nsconv -f source_charsetname -t target_charsetname source_filename new_filename
            • nsconv -f source_charsetname -t target_charsetname source_filename > new_filename
            • nsconv -f source_charsetname -t target_charsetname < source_filename > new_filename
          • You can use the charset names you see within the parentheses of  the Character Set menu for source_charsetname and target_charsetname, e.g. iso-8859-1, Shift_JIS, Big5, EUC-KR, etc. Use UTF-8 and x-u-escaped for target encodings.
          • The utility does not seem to replace an existing file with the new output file. If you have an existing file with the same name as the intended output, first delete the existing file. Or else output into a new file with a different name.
  • DTD/XML encoding definition supported -- thus you can use charsets other than UTF-8 as the .dtd file charset, but using charset other than UTF-8 is not recommended for Mozilla localization. We assume UTF-8 as default. Cf. Bug 4431.
  • Notable bugs:
    • chrome.rdf file: Definitions in chrome.rdf files under locale directories can be used to switch to different chromes suitable for a particular language version, or make other chrome switches. Due to a bug (Bug 21647), this feature is not working well.
    • Access key and Command key shortcuts are supposed to be appended before an ellipsis character "..." in languages like Japanese but currently Access key is appended to the end after the ellipsis character "..." as in Save as ... (S). See Bug 14110.
Mail/News (Testing done on Windows and Linux only):
  • Performance: There have been 2 great improvements in M13 and Messenger is now very much usable. We recommend that users give it a try.
    • Messenger should now be able to handle mailboxes with several thousand messages. For moderate users of mail, Mozilla should be a usable daily mail client. M13 would be a very good chance to get your Mozilla mail experience going and participate in making it better.  (Note: In addition to performance improvement with server interactions, improvements in preference settings with Mail Account Setup were also made in M12.)
    • Message display code has been re-written in M13 to speed up the display of messages measurably. Users of M12 will notice this display speed gain immediately.
  • Preferences file: prefs.js (Note: Up to M8, the Preferences file was named prefs50.js. This file name is prefs.js instead for all later Milestones.)
    • General info for M13:
      • Once you create a profile via the Profile Manager, the rest is very easy to set up with the use of  Edit | Account Setup ... menu in the Messenger window. Read this section also for general preferences issues in addition to looking at Mail specific preferences.
  • Mail Account Setup manager: If you want to learn more about how to setup various mail and news servers, and multiple mail mail accounts, read this document. The future Mail Account Setup specs also have been published here.
    • SMTP sever setting:
      • If you have not done so already, after you start up Messenger, choose Edit | Account Setup ... and set the outgoing (SMTP) server and user name. This needs to be done only once but without setting, you will not be able to send out mail.
    • Password:
      • When accessing a mail server for downloading messages, you will be asked to provide a password via a dialog. If you want Mozilla to remember your password, use Edit | Account Setup ... menu and select "server" under each one of your accounts. Then check "Save password: box.
    • IMAP server setting:
      • Use Edit | Account Setup ... menu to set up a variety of IMAP server related options.
    • NNTP (News) server setting:
      • Use Edit | Account Setup ... menu and add an News server. Then when it is added, use File | Subscribe ... menu to add newsgroup you want to read. Currently there is no way to list all the newsgroups on a server. Just add newsgroups you want manually via the Subscribe... menu.
      • Reading in different languages is now working if the charset parameter is specified in news article headers. You can also use auto-detection modules enabled though the Browser menu to detect and display articles without a charset parameter. At this point, news reading in Chinese will be generally difficult since many Chinese newsgroups contain messages without any charset parameter.
    • POP Mail settings:
      • Use Edit | Account Setup ... menu and set up several different options using the server setting under each account.
      • You can set it up to keep the messages on the POP server after you have downloaded them, too.
    • HTML vs Plain Text Mail option:
      • You can set up HTML or Plain Text send option for each server in your account. In case a server is not selected in the Messenger's left pane, the setting for the very first server (on top) on the Account Manager list will be used as the default. In future, the default Mail Send option should become possible through an UI element.
    • Account Names in non-ASCII characters: For the names you want to give to each of the Mail or News account, you can now use non-ASCII characters. They will be preserved in prefs.js file. Remember, however, that when there is non-ASCII data, prefs.js will be in UTF-8 encoding. If you look in prefs.js with an editor, you will not be able to see the characters correctly unless your editor can display UTF-8 data. If you make changes and save the prefs.js file, your editor must be able to save in UTF-8. Otherwise, the prefs.js will become corrupt and unusable. If you're editing the prefs.js file and if it contains non-ASCII data, first create a backup file and edit this one rather than the prefs.js file itself.
    • Directory Path names in non-ASCII characters?: You can customize where you store your mail msgs and summary files. At this point, non-ASCII names must be avoided in path names.
  • Downloading POP msgs & IMAP headers :
    • The performance in these areas has improved further in M13.
    • Note: some POP servers don' t handle multiple, simultaneous accesses to the same account well. In such cases, keep only one connection alive to use it trouble-free.
  • Displaying Mail links with Browser: If clicking on an URL link in a message leads to display in the Messenger window rather than in the Browser window, choose Browser's Debug | URI Dispatching | Enable Dispatching. When you do this, URL links in mail messages will not be shown in the Messenger window but by the Browser window. In the near future, this will be the default behavior and links will not be shown inline in the Messenger window.
  • How various mail-related international functions are working at M13:
    • Address Book: supports Non-ASCII (including CJK) input, editing and display. The following features are working.
      • Non-ASCII Input into card fields
      • List View pane -- proper international sorting (Windows and Macintosh only.)
      • Each card view pane -- displays non-ASCII strings
      • Can re-edit existing cards with non-ASCII entries.
      • New Msg button on Address Book entries: works and will import any language name into the "To: " header for new mail correctly.
      • Address Picker on Mail Composer window: works for all languages we support and displays all non-ASCII names correctly.
      • Address auto-completion is working partially. If an Address Book entry contains non-ASCII characters, they are now displayed correctly. However, trying to match with with non-ASCII characters don't work with M13.
      • Importing 4.5 or later AB entries: Address book entries import from Communicator 4.5 or later is now possible. Just export your Address Book entries using Communicator 4.5 or later. This will create a file with .ldif extension. Import this file using File | Import  menu from the Address Book. (Note: This will not work with .ldif files created by Communicator 4.0x versions since they are not saved in UTF-8 and instead saved in the default charset of the operating system.)
      • Bugs:
        • On Unix, sorting in Address Book is not working well.
    • Multi-lingual mail viewing: This is working on all platforms.
      • Multilingual viewing is working on IMAP, POP3 and NNTP servers as long as the messages contain properly MIME-encoded headers and body with correct charset parameters.
      • View | Character Set menu is currently not working to override wrong MIME charset label, or view msgs which have no MIME charset (except for Latin 1) specified.
      • If you have a multilingual font or several fonts which together cover the Unicode ranges (e.g. Chinese, Japanese, Korean fonts + Pan-European fonts), we use them in displaying mail messages and headers for all the languages we support. We pay attention to the charset parameter in the Content-Type header and switch to an appropriate font. The Character Set menu is not needed to switch to different language views unless the message you're viewing is incorrectly labeled. If you would like a basic mono-weight multi-lingual font for Windows, you can get Bitstream Cyberbit font 2.0 here. Mail font settings are also affected by prefs.js setting as described above in the Browser section --
      • Earlier there were a few bugs which prevented Mozilla from displaying Thai (Windows-874 or TIS-620) mail messages. They have been fixed and now you can view mail messages sent in these encodings.
      • Viewing News: is working. Multilingual news articles viewing works if they have correct MIME charsets indicated in the articles. Be warned, however, that newsgroups postings are not always MIME-compliant and this could defeat our charset honoring mechanism.
      • Bugs:
        • Sender names do not display correctly in the thread pane except for Latin 1 names. (CJK names display as dots.) They are displayed correctly in the Message view window, however. Bug 8405.
    • Viewing non-ASCII attachments: generally working but there are some bugs.
      • Attachments should be viewable if they are of the same charset as the main body of the mail or if it has explicit charset parameter in the attachment headers, or if it contains a valid Meta-charset headers in the attached HTML file.  If an attachment lacks charset parameter info and if its charset does not match that of the main body, that attachment cannot be viewed currently even when the Character menu is changed to match the charset of the attachment. A charset detector as discussed above can work on attachments without explicit charset information -- if it is turned on via the Browser menu.
      • Multiple attachments in different languages: can now be viewed without changing the charset menu if each attachment's header contains a correct charset parameter or if a document contains a valid Meta-charset information. If you send a message from Mozilla with multiple attachments and if each attachment has a meta charset tag, Mozilla will create a content-type charset parameter for each attachment from the meta-tag information.
      • Latin 1 attachment to ASCII msg: In M12, if an attachment contained raw 8-bit Latin 1 characters and was attached to a mail body with an us-ascii charset parameter, Mozilla did not display these attachments correctly. We fixed this problem in M13 by assuming ISO-8859-1 instead of ASCII as the message charset in such a case. See Bugs 20997 & 22209 for details.
      • Japanese attachments and auto-detection:
        • The auto-detection module set for the Browser via its Auto-Detect  menu will also detect the charset of mail attachments. See above on how to set an charset detection module.
        • Currently there is a bug which corrupts Japanese EUC-JP attachment display. To work around this problem, we have put in a mail specific charset detector which only works in Messenger under Windows only. (Note: Eventually this detector will be removed when the EUC bug is fixed.) When this is set, this detector rather than the Browser detector will be used in Messenger.  This detector will be ON even when the Browser detector is OFF. For those wishing to view Japanese EUC files attached to mail messages, we recommend that this workaround be put in place. There is no UI for this but this is how you can use it:
          • In the prefs.js file, insert the following line:
            • user_pref("mail.charset.detector", "jaclassic");   <-- this is basically a detector module used for Communicator 4.x.
      • Printing: Basic printing is enabled. Currently it is rather primitive. Headers don't seem to be printed -- only body text.
    • View | Character Set menu and thread pane reloading:
      • The menu change causes the thread pane to reload properly. This makes it possible to display non-MIME-encoded headers which don't match the current Character Set menu setting.  Headers, body, and attachments without MIME charset information may not be displayed properly, however, even if the Character Set menu is changed.
    • IMAP and Local non-ASCII folder names: Latin 1 names display OK. Multi-byte folder names (e.g. CJK) don't display well yet. Cf. Bugs 7130 (IMAP), 7844 (Local).
    • International Sorting for Thread pane headers: works well in the Subject headers on all platforms with some problems still left on certain Unix locales. CJK characters are not displayed correctly in the Sender field and therefore cannot be tested. Sorting should be done according to the sort default for the language of your operating system. Date/Time sorting is also working as it should.
      • Linux sorting:
        • There seems to be a problem with Latin 1 sort -- this is under investigation.
        • Also sorting is working for some Japanese locale names but not others. It might have to do with locale name aliasing. This problem is under investigation. Cf. Bug 18338.
    • International Date/Time format:  now works for NT4, Win9x, and Mac for all locales. The format will be used according to your OS's date/time format setting.
  • Sending Latin 1 & Japanese attachments/pages:
    • File | Send Page works in addition to attaching a local file to a message.
    • Note that Mozilla will append a charset parameter to the attachment headers if the page contains an HTTP-Equiv meta charset tag.
  • Send-related bugs at M13: Here are some send-related bugs at M13.
    • If the message you're trying to reply to or forward as inline has an attachment displayed inline, none of  the attachment is quoted. Forward as attachment does work, however. Cf. Bug 23931.
    • Sending page with a meta charset tag will mark the attachment with an appropriate charset parameter but sending a page with HTTP charset does not add this charset info. This problem has been fixed in M14. See Bug 24940.
    • At M13, reply/forward does not initially set the charset to the same one as the original mail. This has been fixed in M14 to reflect the original mail's main body charset. See Bug 3979.
  • Sending messages in other languages: View | Character Set menu for New Mail Compose window is working for sending mail for many additional languages. Switch to the charset you want to compose a message in and then compose the message.  You will not see a checkmark next to the menu item yet, however. Let us know how we are in sending messages in other languages. Send your report to:
  • Composing Latin 1 mail messages:
    • In sending 8-bit range characters with HTML mail under Latin encodings, starting with M11, we used 8-bit characters rather than HTML entities, and certain special characters not in the chosen encoding were turned into CERs (so-called HTML entities) or NCRs (numeric character references). We changed this back at M13 to using HTML entities for all non-ASCII range of the Latin 1 table.
    • In sending 8-bit range characters with Plain Text mail, we will generally use QP-encoded characters. Those characters not in the chosen encoding, e.g. the EURO under ISO-8859-1 is turned into a "?" symbol. We are considering more user-friendly spec for this currently.
  • General Fallback strategy for sending characters not found in the chosen encoding:
    • CERs or NCRs will be used in HTML mail.
    • "?" will substitute for non-existing characters under Plain Text send option. In future, we may offer an option to send in UTF-8 or some other encoding which support the characters in question.
  • Domain Name completion: is now working. An user ID only input will be automatically completed with the default domain when the Enter key is pressed.
  • Message Send Status summary for Latin 1 and Japanese: No indicates that the functionality is not working well.

    Message send feature
    Latin 1 (ISO-8859-1)
    Japanese (iso-2022-jp)
    Header (subject, address)
    Body - HTML
    Yes (8-bit characters are sent as is with HTML entities. )
    Body - plain
    Yes (8-bit characters are sent as is with QP. When the chosen charset does not contain the character, "?" is used in its place currently.)
    Reply/forward header
    Reply/forward body html
    Yes -- POP mail, IMAP, NEWS (but some bugs) Yes -- POP mail, IMAP, NEWS (but some bugs)
    Reply/forward body plain
    Yes - IMAP, POP, News.  (but some bugs) Yes - IMAP, POP, News (but some bugs)
    Reply/forward inline attachments
    No attachment is quoted. Bug 23931. No attachment is quoted.  Bug 23931.
    Reply as attachment
    Yes. Yes.
    Send Attachment(s)
    Yes (Send - local file and web page) Yes  (Send - local file and web page.)
    Copy/paste into headers and body
    Yes (accented characters copy OK) Yes  (works OK within Mozilla)
Notes on Composing Latin 1 and Japanese Mail messages:
    • Composing Latin 1 Mail:
      • Copying/pasting accented characters into the headers and  body works from anywhere within the application where copy is enabled, e.g. Messenger Mail window, Browser window. You can also copy non-ASCII data from Communicator 4.x into Mozilla.
      • Keyboard input into headers (e.g. subject) also works for accented characters. Using the English keyboard for Latin 1 high-bit input, ALTGr + 0+Number Keypad method works, e.g. Right ALT key + 0232. There is an annoying bug about ALT+NumPad use -- see the Editor section for more.
      • Make sure to switch the View | Character Set  to your chosen Character set name before you send out a message.
      • Basic MIME compliance is there: Header Q encoding, and Body QP encoding for accented characters.
    • Composing Japanese mail:
      • Basic Japanese input works for body.  Japanese input/copying into the headers and body also work from within Mozilla. You can also copy JPN data from Communicator 4.x into Mozilla.
      • Mail goes out in ISO-2022-JP.  Header is B-encoded. (The Kanji-in escape sequence is that of JISX0208-1990/83. )
      • Make sure to switch the View | Character Set  to Japanese (ISO-2022-JP) before you send out a message.
    • Sending other charset mail -- is enabled. Please try out these new charsets! For example, Central European, Cyrillic, Greek, UTF-8, Thai, etc.
      • Though the mail text body can sense what keyboard you have selected and will switch font accordingly, there may be mapping bugs with some international keyboards.  If you find a bug with your charset/language, please file it here.
Mail/News (for Mac)
  • We don't currently test Mac for international features. Though we cannot vouch for accuracy, many of our Windows/Linux features should be working on Mac also.
List of Charset Converters available at M13:


  • Western (ISO-8859-1, Windows-1252, MacRoman), Central European  (ISO-8859-2, Windows-1250, MacCE), South European/Esperanto/Maltese (ISO-8859-3), Baltic/North European (ISO-8859-4, Windows-1257), Baltic/North European (ISO-8859-13), Cyrillic (ISO-8859-5, Windows-1251, KOI8-R,  ISO-IR-111 aka ECMA-Cyrillic, MacCyrillic, CP-866), Arabic (ISO-8859-6, Windows-1256) - (not in spec, might be removed from commercial build later) , Greek (ISO-8859-7, Windows-1253, MacGreek), Hebrew (ISO-8859-8 aka Windows-1255) - (not in spec, might be removed from commercial build later), Turkish (ISO-8859-9 aka Latin5, Windows-1254, MacTurkish), Nordic/North European (ISO-8859-10 aka Latin6), Celtic (ISO-8859-14), Western (ISO-8859-15), Armenian (ARMISCII-8), Thai (TIS-620 aka Windows-874), Ukrainian (KOI8-U, MacUkrainian), Vietnamese (VISCII, Windows-1258, VIET-VPS, VIET-TCVN5712), other Mac encodings (MacCroatian, MacIcelandic, MacRomanian).
  • Japanese (Shift_JIS, EUC-JP), Traditional Chinese (Big5, EUC-TW), Simplified Chinese (GB2312), Unicode (UTF-8, UCS-2, UCS-4), Korean (EUC-KR), Western (T.61-8bit) - support this for LDAP v2 and X.500.
  • Japanese (ISO-2022-JP), Unicode (UTF-7, IMAP4-modified-UTF7- Needed for IMAP folder names)