M10 Release Notes

These release notes, last updated October 11, 1999, describe installation instructions and known issues pertinent to the M10 release. These notes are updated as we receive feedback, so please check back for new information.

Related links

• For more information about known problems, you can also view an up-to-date list of fixed bugs.
• For status and notes on features in each milestone, see the milestone page.

Contents of This Document

• READ THIS Before You Install
• Installing the M10 Release Build
• Installation Instructions - Unix
• Installation Instructions - Win32
• Installation Instructions - Mac OS
• Uninstalling the M10 Release Build
• Files Created or Used
• Limited Support Features
• Available Navigator Functionality
• Available Mail/News Functionality
• Available Editor Functionality
• Available Gecko Functionality
• Known Issues
• General Browser Issues
• Issues with Bookmarks and History
• Sidebar Issues
• Issues With Profiles
• Editor Issues
• Java Issues
• Javascript Issues
• Issues With Small Fonts on Linux
• Known Issues in Mail and News
• International Issues

This release expires on December 15, 1999 at 00:01 am.

READ THIS Before You Install

If you experience a crash upon launch, delete your Mozilla registry. The format of the Mozilla registry has changed on all platforms since M9.

• Mac OS: Open your System Folder's Preferences folder, and delete the "Mozilla Registry" file.
• Windows: Open your Windows directory, and delete "mozregistry.dat".
• Linux: open your ~/.mozilla directory, and delete the "registry" file.

For more information, please see news://news.mozilla.org/37E8A320.D3420962%40netscape.com

If you have installed a Seamonkey build prior to August 10, your profile directory contains a "prefs50.js" file. In M9 (and all builds after August 10), Apprunner will look for "prefs.js" instead. To use your existing prefs, change the name of the prefs50.js file to prefs.js. If you have no previous profiles, you don't need to make the change.

Install into a clean directory, or delete previous builds before installing. Installing on top of previous milestone builds or released product builds may cause problems. Incompatibilities may be introduced from milestone to milestone while the software is under development.

On Linux systems that use glibc 2.0 (such as RedHat 5.2), there are problems with dl functions (dlopen(), dlsym()) not being thread safe. This might cause your M10 build to randomly crash at startup. If this happens to you, try running the application a few more times. The bits posted on ftp.mozilla.org are built on RedHat 6.0, which uses glibc 2.1 and does not have this problem. For more details, see bug 8849.

Do not use Java Plugin 1.3. It doesn't work with the most recent mozilla builds, and crashes will result. Make sure there are no files named *npjava*.* in either the bin/;lugins directory or the NS4.x plugins directory. This problem is being addressed. For more information about this bug, see bug 5369.

Proxies ARE working in this release. See bug 8559 for details on setting up.

Installing the M10 Release Build

Installation Instructions -- Unix

1. Create a directory named "mozilla" and move the tar.gz file into the mozilla directory.

mkdir mozilla ;
mv mozilla*.tar.gz mozilla

2. Change to the mozilla directory and untar the archive. This will create a directory called "package".

cd mozilla ;
gzip -dc mozilla-i686-pc-linux-gnu-M10.tar.gz | tar -xvf -

3. Change to the "package" directory.

mv mozilla*.tar.gz ../ ;
cd package

4. Run mozilla with the run script:

./mozilla-apprunner.sh

Mail Instructions for Unix

You can migrate an existing 4.x profile, or create a new profile and use Account Setup to set up your servers.

Installation Instructions -- Win32

You will need a copy of WinZip. This is shareware available at http://www.winzip.com (also at http://www.download.com).

1. Click once on the mozilla-win32.zip link. The file will be downloaded to your default folder.

 :
2. Click on the mozilla-win32.zip file to launch WinZip.

 :
3. After clicking "I Agree" to terms of WinZip shareware, click the Extract button in the WinZip tool bar. An x86 folder with application and associated files will be unzipped.

 :
4. Select Apprunner from x86 folder to launch the program.

 :
• Run "apprunner.exe" to use browser and mail.

 :
• Run "viewer.exe" to run only the gecko layout engine

Mail Instructions for Win32

You can migrate an existing 4.x profile, or create a new profile and use Account Setup to set up your servers.

Installation Instructions -- Mac OS

If you have StuffIt Expander™ installed and your browser is configured to use it:

1. Click once on the mozilla-mac.sea.bin link. The file will be downloaded to your default folder (usually the desktop) and StuffIt™ will start up and convert it to mozilla-mac.sea for you. Then StuffIt will open up mozilla-mac.sea and convert it to a folder called mozilla-mac for you.

 :
2. Open the mozilla-mac folder and double-click the file "apprunner." (Note: you no longer need the .bin or .sea files.)

Note: If you try step one and your browser asks you what you want to do it's because you don't have StuffIt™ configured. In that case, just click Save and continue from Step #3 below.

If you do not have StuffIt Expander™ installed or your browser is not properly configured:

1. Make sure you have StuffIt™ somewhere on your hard drive.

 :
2. Click and hold the mozilla-mac.sea.bin link.

 :
3. Choose "Save this link as...".

You will see a file dialog box where you can select where you want to save the file (for example, your Desktop).

4. Click the Save button.

 :
5. Double-click on the newly created icon "mozilla-mac.sea.bin".

 :
6. StuffIt™ will start up and simultaneously create a file "mozilla-mac.sea", and a folder called "mozilla-mac."

 :
7. Open the mozilla-mac folder and double-click the file "apprunner." (Note: you no longer need the .bin or .sea files.)

Mail Instructions for Macintosh

You can migrate an existing 4.x profile, or create a new profile and use Account Setup to set up your servers.

Uninstalling the M10 Release Build

Linux

• Remove the /package directory where you installed Seamonkey

 :
• Remove the ~/.mozilla directory, which contains profile information

Windows

• Delete the \x86rel directory where you installed Seamonkey

 :
• Delete c:\windows\mozregistry.dat

 :
• Delete the user profile directory, \users50

Mac OS

• Remove the the folder Mozilla in the Documents folder

 :
• Remove the file "Mozilla Registry" in the System Folder | Preferences folder

 :
• Remove the folder where you installed Seamonkey (probably mozilla-mac-M10)

Files Created or Used

*Note:"cookperm.txt" ("cookperm" on Unix) is a file used to selectively accept cookies from certain sites and not from others. It is used only if you set your preferences so you see a warning before accepting cookies. To do that, hand edit the prefs.js file to include:

user.pref ("network.cookie.rememberAboutCookies", true);

Limited Support Features

Available Navigator Functionality

Available Mail/News Functionality

Additional Mail Functionality

• The multiple POP accounts feature is available for you to try out. To set up multiple POP accounts, open the mail application and use the Account wizard. You will need to have identity and server information for the second account.
   
• You can use the Address Book window and the Select Address dialog. The Personal Address Book is working for adding cards, editing cards, and deleting cards. LDAP and additional address books are not working yet. The data is stored in a file called "abook.mab". Your Address Book information is used to auto-complete names entered into the mail compose window.

Available Editor Functionality

Available Gecko Functionality

Known Issues

General Browser Issues

• The page may not load correctly for http://www.disney.com/ and its secondary sites.
• 
   
• Clicking on a mailto: link causes an application crash.
• (bug 12198)

 
• You can't connect to secure sites (URLs beginning with "https://") in the M10 release.
• 
   
• Chosing the File menu's Open Web Location option leads to unpredictable results and may cause a crash.
• (bug 14885)

 
• Selecting the Edit menu's Wallet - Wallet Contents option may cause a crash.
• (bug 15170)

 
• A crash may occur if you print from Apprunner and then reload the page. (bug 12023)

 
• (Linux only) In 256 colors, loading the test10.html document in Apprunner will cause a crash. (bug 11090)

 
• Loading problems (possible crash or freeze) sometimes occur on pages that contain applets.

 
• FTP is not fully functional in M10. (bug 10737)

 
• The Stop button fails intermittently

 
• Print (toolbar button & menu item) and Print Preview fail intermittently

 
• Keyboard shortcuts/command keys are not available for most menu items with the exception of the following for the mail compose and editor window: Ctrl-C (copy), Ctrl-V (paste), Ctrl-Z (undo). and Ctrl-Y(redo) and their Mac OS equivalents. The old Unix equivalents (using Alt- instead of Ctrl-) don't work; use Ctrl- .

 
• Within Viewer, many options within the Debug & Tools menu items are not currently working or produce unpredictable results.

 
• Windows only:

 
• Using the collapse and expand widget to collapse the top three toolbars in your browser window (from top to bottom in succession), and then trying to expand them again, will result in a browser crash. (bug 15489.)

 
• Links on pages that use CSS do not work.

 
• If you have a second video display monitor connected to your computer, links displayed on that monitor will not work.

 
• Selecting the Print option causes crashes.

 
• Mac OS only:
• FTP directory listings do not work.

 
• Linux only:

 
• Password dialogs do not correctly handle some characters.
(bug 15463.)
 
• Using the collapse and expand widget to collapse the top three toolbars in your browser window (from top to bottom in succession), and then trying to expand them again, will result in a browser crash. (bug 15489.)

 
• Using the File menu's Close option to close a secondary browser window will close out Apprunner. As a workaround, use the close box. (bug 15308.)

 "
• Using the File menu's Close option may bring up the Print dialog. (bug 14759.)

 "
• The Back and Forward buttons do not work for manually entered URLs.

 
• The throbber, mozilla animation in the upper right corner of a page, may not work while the page is loading, though the page still loads.
• Solaris only:

 
• The Copy command in the browser's Edit menu is not working. (bug 6253)

Issues with Bookmarks and History

• Incorrect bookmark behavior can be related to profile problems. See Issues With Profiles.

 
• Drag and drop is not yet implemented, but you can use cut, copy, and paste to manipulate your bookmarks.

Sidebar Issues

• Clicking on the Customize button may cause a crash.

 
• You cannot yet add or remove sidebar panels using the UI.

 
• Changes you make in the Customization dialog will not be reflected in the Sidebar.

 
• To hide the sidebar, select Sidebar from the View menu.

 
• General Sidebar UI is not finished.
• (Windows only) Double clicking on Related Sites in the What's Related folder will not open the URL. You can manually open the page by entering its URL into the URL bar. (bug 15481.)

Issues With Profiles

• IMPORTANT: All the information regarding profiles is stored in the registry file. The registry file gets created even if you have used earlier versions of Apprunner. When you check out a new build, make sure you delete or rename the following items before you install, build, and run the new executable:

 
• Windows mozregistry.dat ( c:\winnt or c:\windows or equivalent),
• Mac OS Mozilla Registry (System Folder:Preferences),
• Linux registry (~/.mozilla/)

 
• You open Profile Manager with the command line argument : -ProfileManager. The Profile Manager user interface appears, supporting creating a new profile, and deleting and renaming existing profiles. When you finish any of the tasks you can click Exit to quit the Profile Manager. You can click a Start Communicator button to start Apprunner with a selected profile. Also, users can migrate 4.5 Communicator profiles (Windows only, for now).

 
• Various command line options to create and manage profiles are:

# apprunner -P <Profilename>

Runs Apprunner with the <Profilename>.

# apprunner -CreateProfile "<Profilename> <ProfileDir>"

Creates a profile (i.e., <Profilename>) and creates a directory at the specified location i.e., <Profiledir> and launches Apprunner.

# apprunner -CreateProfile <Profilename>

Creates a profile and creates a profile directory under default profile location.

# apprunner -ProfileWizard

Launches the Create Profile Wizard to create a new profile. The Create Profile Wizard lets users create a new profile at the default location or the location of their choice. At the end of the process a profile is created and marked as the current profile, and Apprunner is launched with that profile. The wizard is currently just two screens. Mail and News related preferences/information will be collected by a different application.

# apprunner -ProfileManager

Brings up Profile Manager for managing profiles. Users can select a profile and click on the Start Communicator button to launch Apprunner with the chosen profile. The current profile (usually the last used profile) appears preselected.

# apprunner

Several scenarios:
 number of profiles = 0 --> Brings up Create Profile Wizard
 number of profiles = 1 --> Launches Apprunner directly with that profile
 number of profiles > 1 --> Brings up Profile Manager

Default profile locations for profile directories are <3 levels up from the exe location>\Users50, on Windows :Documents:Mozilla:Users50: on Mac OS, and ~/.mozilla on Linux.

• Profile Manager (Windows and Linux only): If you enter the Profile Manager using the Apprunner - installer command and try to create a new profile here, a crash will occur. Do one of the following:

 
1. Remove mozregistry.dat and Users50(Win)registry and .mozilla (Linux)
2. Run apprunner to bring up Create Profile Wizard
3. Choose [NEXT], enter profile data, [FINISH]

This should launch Seamonkey with the created profile

OR

1. Remove mozregistry.dat and Users50(Win), registry and .mozilla (Linux)
2. Run apprunner -installer
3. Select a profile to migrate from list (*if only one 4.x profile exists, it will be migrated silently)
4. Press [START]

This should launch Seamonkey with the migrated profile

See bug 15075
 

• Profile Manager (Windows and Linux only): The Rename and Delete buttons are not working properly.

 
• Profile Migration (on Windows only): 4.5 profiles now can be migrated to 5.0. In the process of migration, 4.5 profile information is undisturbed. In 5.0 the new location for the migrated profiles is the default location as mentioned in the above paragraph. Migration is functional on Windows only, but will soon be extended to the Mac OS. (A date for Linux availability is currently unknown.)

To migrate 4.5 profiles, run Apprunner with the command line option -installer. The profile to be migrated is listed as <profilename> - migrate in the Profile Manager's list box. Users can select a profile to be migrated and click on the Migrate button. If the migration is done successfully, the suffix ' - migrate' disappears in the display, marking that profile as a 5.0 profile. Currently, only the prefs.js file and mail and news folders are copied in the migration process. Users cannot rename or start Communicator with a profile that must be migrated. With the changes that went in at the end of M7, it is required to create a 5.0 profile before using the migration service. This will be fixed in M8 (so that there is no dependency on having a 5.0 profile).

• Mac OS only: In creating your default profile, don't use spaces in the profile name. The actual folder will be named with "%20" for each space you include. As a result, if you use Messenger, your mail folders will not load or display. (bug 6744)

 
• If the Bookmarks menu has only the Add Current Page and Manage Bookmarks menu items, and they are not followed by a list of bookmarks, then bookmarking will not work correctly until you do one of the following:

 
• Migrate an old 4.x profile over to Seamonkey, or

 
• Create a new profile by following these steps:

 
1. Remove your current profiles and mozregistry.

 
2. For Windows, remove the "mozregistry.dat" file in your Windows (or winnt) directory; also remove the entire "Users50" directory.

 
3. For Mac OS, remove the "Mozilla Registry" file from your Preferences folder (System Folder|Preferences|Mozilla Registry). Then remove the "Users50" folder from the Documents folder that was placed on your hard drive when you installed Seamonkey (documents|mozilla|Users50).

 
4. For Linux, remove the .mozilla/ directory.

 
5. Launch Seamonkey and create your new profile. The menus should now appear and behave normally.

  (See also bug 9505)

Editor Issues

• The editor doesn't launch on the Mac OS unless you give the browser the focus. (bug 9701)

 
• Apprunner crashes on launch at times. (bug 8849)

 
• Preview is not working. (bug 9200)

 
• The image dialog is not fully implemented. (bugs 9751), 9753, 9754, 9755, and 9757,)

 
• The menu and toolbar items don't get disabled. (bug 5563)

 
• Popup menus in dialogs don't work.(bug 14340)

 
• There are some missing menu items. (bug 14342)

 
• Table editing needs to be implemented. (bug 6256)

 
• Mac OS and Linux: The spellcheck dialog does not come up. (bug 6864)

 
• You must click in a document in order for the caret to reappear.
(bug 13887)
 
• Mac OS only: The editor doesn't launch. (bug 9701)

 
• Linux (Solaris) only: Highlighting doesn't work. (bug 10699)

 
• Linux only: Apprunner may crash on launch. (bug 8849)

 
• Linux (Solaris) only: Highlighting doesn't work. (bug 10699)

Java Issues

• If you have installed the latest JRE 1.2 from Sun Microsystems, you may crash at startup if the Java plugin is present. To fix this, remove the following dlls from the Plugins folder located in your 4.5 (or later) Communicator directory: npjava32.dll, npjava12.dll and npjava11.dll.

 
• On Linux, Java is not yet implemented.

Javascript Issues

• document.write fails to write HTML tags and any text written before the last tag. (bug 11141)

 
• JavaScript alert dialogs are not being displayed. (bug 4279)

 
• None of the JavaScript window.xxx() functions work with AppRunner windows. Windows can be opened using the ToolkitCore, but those windows don't play well with most of the JavaScript properties and methods.

 
• "javascript:" is not working.

Issues With Small Fonts on Linux

• If the fonts are too small in your environment, it may be possible to alleviate this by setting a preference in Mozilla. Add a line like the following to the preferences file (~/.mozilla/prefs.js):

 user_pref("browser.screen_resolution", 120);

This sets the dpi to 120. If you set the pref to zero (0), Mozilla will use the X server's dpi value. If the pref is not set, it uses the default value of 96.

There is some info about setting the X server's DPI value at http://www.mozilla.org/unix/dpi.html.

If your fonts are still too small (or too large) after setting the DPI correctly, you can adjust the font size as follows:

setenv GECKO_FONT_SIZE_FACTOR 1.5

Note that the latter only affects fonts. The screen_resolution preference affects anything that specifies absolute size (e.g. CSS "pt" points).

Known Issues in Mail and News

• IMAP only: After you compose a message and click Send, an Alert dialog appears and the compose window re-opens. The message is sent. (bug 14591)

 
• Cancelling a news message doesn't remove it from thread pane. (bug 8216)

 
• When using the Address Picker, the cc field is not displayed (bug 14722)

 
• Messages sent from Unsent folder arrive with the header and message body in the body, and in plain text format. (bug 14797)

 
• You may be unable to read messages generated by Outlook2k and Word 9. (bug 14905)

 
• Collapsing the addressing pane in the mail compose window may result in a crash. As a workaround, do not collapse the addressing pane. (bug 11856)

 
• Currently, the Delete key does not delete messages. Choose Delete from the Edit menu, or use the Delete toolbar button to delete messages.(bug 8985)

 
• When addressing a message to multiple recipients, use a comma to separate the recipients. If you use a semicolon, a program crash may occur.(bug 8276)

 
• Although you can bring up the Search and Filters dialogs, backend code for these features has not been implemented so you will not be able to perform any functions in these dialogs.

 
• When you select an unread message with the message pane collapsed, the message is marked as read. (bug 6485)

 
• If you have local folders with more than 1,000 messages, don't point the Mail application at your actual local folder hierarchy. Larger folders may take too long to load and may consume vast amounts of memory.

 
• Vcards in mail are not fully functional and may cause failures when clicked.

 
• Mac OS only:

 
• After startup, you must click inside the browser window to bring it to the front before using any of the menus. (bug 9701)

 
• In creating your default profile, don't use spaces in the profile name. The actual folder will be named with "%20" for each space you include. As a result, if you use Messenger, your mail folders will not load or display. (bug 6744)

 
• Linux only:

 
• Typed text isn't display until you press enter and start typing again. (bug 14845)

 
• When you select the Newsgroup, Cc, and Bcc fields, widgets do not hold but you can still type and send. (bug 15186)

 
• Using Message|Copy to copy a news message to a folder posts an empty subject and sender, and an incorrect date in the thread pane. (bug 15216)

 
• Clicking on a folder crashes after you select Send Later. (bug 15254)

 
• Text under the toolbar buttons is not readable. For a workaround, see http://www.mozilla.org/unix/dpi.html.

 
• Issues in the Mail Compose window:

 
• (Windows only) To access the drop down list boxes in the addressing fields, use the down arrow key to scroll the list of choices (such as "from:," "cc:" or "newsgroup:" etc.). Alternatively, you can collapse then expand the addressing panel before choosing from the list. (Data you enter prior to collapsing the panel will be lost. Enter your recipients after collapsing the panel.) (bug 9537)

 
• The cursor does not appear in the message field until you begin typing.

 
• The received message does not wrap lines, so you may want to embed hard returns in your messages.

 
• Messages may contain either too much vertical white space or not enough.

 
• If you are using plain text (instead of HTML) for messages, you may need to press Enter twice at the end of a line to move the cursor to the next line.

 
• To use the plain text compose window, add this line to your preference file:

 

user_pref("mail.identity.id1.send_html", false);

International Issues

For updated information on features, fonts, and testing for Internationalization, visit this page.

General:

I18n Engineering and Milestone Tasks document is now available here.
I18n Beta 1 Feature Plan is now available here.
I18n Beta 1 Mail/News Functional specifications are now available here.
Localizing Mozilla document.
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: I18n --> netscape.public.mozilla.i18n, L10n --> netscape.public.mozilla.l10n, Testing--> netscape.public.mozilla.qa.i18n

Preferences

• Dealing with preferences has become much easier! With M10, Mozilla 5.0 offers you to migrate any Communicator 4.x profiles you have on your system. Choose an existing one from 4.x and a new one will be created for 5.0. The window for profile migration will appear the first time you start M10 build after the installation. If it does not, you can start with the profile manager: apprunner -installer (Unix & Win).  Mac users can start with the Mozilla Preferences file..
• If you have used an earlier version of Mozilla 5.0, we recommend that you delete the file called mozregistry.dat (Win)/Mozilla registry (Mac)/registry (Unix) before you run M10 apprunner. (Don't delete Netscape Registry file for Mac, which is for Communicator 4.x.). We recommend this procedure because during M10, there has been a change in the way registry works and the old registry for M9 will not work well with M10. Read the section in the Release Notes called Files Used or Created to find out where you can find these files.
• When you start M10 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 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.)
• After a new orefs.js file is created, the apprunner may simply quit or crash. However, when you start it again, your new preference should be honored. The first time you start, not all UI in the side bar area in the Browser and Messenger windows may be drawn correctly. This is a known bug. The problem normally disappears when you simply quit and re-start the apprunner the second time.
• Also read the Installation instructions for your platform carefully in this Release Notes.
Browser:
• There have been steady improvement in stability and features that matter to international users in M10.
• New GFX widget/Ender is now ON by default and thus requires no special setting in the prefs.js as was reported for M9. This means that all input areas now support non-ASCII character input including input using CJK IMEs. There are a few significant bugs left in M10, however, for inputting via CJK IME. Read the Editor section below for more information if you plan to use CJK IMEs.
• M10 converter(s): There are no new converters in M10.  See here for a list of all the converters at M10. (Note: Not all menu items may be displayed in the Character Set menu for Windows and Unix clients because the menu does not scroll yet, but the charset you need can be enabled by simple modification of appropriate .xul and .dtd files. See below for details on how to modify these files.)
• Unix charset testing:  As mentioned in the M7 Release Notes, the display for the supported charsets except Armenian, Thai, and Vietnamese should be working now.  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 M10 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. For converting from BDF to PCF format fonts, use bdftopcf utility.)
• EUC-TW bug: M10 has a bug which produces wrong display for EUC-TW (Traditional Chinese) pages. Big5 display is working, however.
• Charset detection modules are now in the Browser Menu!
• The charset detection modules for Chinese, Japanese, Korean, East Asian (CJK), Chinese (Simplified & Traditional Chinese), Ukrainian, and Russian are now in a menu below the Character Set menu.
• 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  netscape.public.mozilla.qa.i18n.
• In M9, 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 "apprunner.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.
• View | Character Set menu:
• The Browser Character Set menu is now dynamic, i.e. created via a script. This is first of the series of steps we will be taking to make the Character Set menu completely dynamic and eventually accommodate new Character sets via a plug-in directory. The dynamic Character set menu will use the Extensibility Model as discussed in this document.
• In M10, the dynamic menu is only for Browser and co-exists below the static Character Set menu. Both menus work in M10 and one of them is actually redundant and will be eventually eliminated. This is harmless, however. Character set menus in other components are still static at this point and you will see only one set of menus.
• 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.
• View | Character Set menu Display problem workaround: The list currently contains 49 items and is too long and unwieldy -- overall charset menu specs are under consideration.
• The Character set menus will be eventually a) scrollable and b) customizable via a menu. At M10, however, neither of these features has been checked in. For Unix and Windows clients, this presents a difficulty since the Character Set menu items may not be all visible on these platforms even if your monitor size is 21-inch. If you have this problem, we would like to suggest the following workaround ideas:
• For languages for which the charset detection modules are available, choose one and see if that would not be sufficient for your viewing needs.
• If you need to use the Character Set menu items and they are not visible on your screen, you can modify the Character Set menus to re-arrange the order of menu items.  Read this file to accomplish this workaround.
• HTTP charset: We now support server-generated HTTP charset correctly. (The order of priority is: HTTP charset > Document Meta Charset > Browser Menu choice.)
• View | Page Source: now works correctly for all charsets if 1) the page has a correct HTTP charset associated with it, or 2) the page has a correct document-based meta charset tag, or 3) the page has been correctly loaded with the use of a charset detector. One case where the source page viewing does not work correctly is when none of the conditions in 1) - 3) holds and the user has loaded the page correctly with the manual change of the Character Set menu.
• CJK line breaking: has been improved in M10. All Kinsoku rules should be working now.
• 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. The same problem might also exist for Baltic ISO-8859-4 display.  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.
• Java: Java Plug-ins are working now on Windows.
• To get Java working on Mozilla, you need to take some extra steps as described below.
• First get the JRE 1.2.2 or later from Javasoft. (JRE package may be included in Mozilla distribution also.) Install the package on your Windows.
• Create a directory named plugins in the same directory where the apprunner 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.
• Check the Java Plug-in Control Panel from Windows Start | Program menu. The following settings (no others) must 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)
• Currently due to a few bugs, a lot of applets simply will not run. Some string display applets do run and so far we have found none can actually display non-ASCII strings. If you have specific applets which deal with string display, write your finding to netscape.public.mozilla.qa.i18n.
Editor: Anyone who uses non-ASCII input in Browser, Messenger, etc. should read this section. For IME specifications, see this document by Tague Griffith.
• CJK IME handling: has been improved and has gained more stability in general, particularly on Windows and Macintosh.
• Basic IME support on Unix: has been enabled for M10 thanks to Sun engineers. It is not working perfectly yet but we now have at least a primitive IME functioanlity working on Unix. We tested Japanese input under Red Hat 6.0 + kinput2 + wnn4. We need your help on testing other Unix platforms and other languaeg IMEs! Important: There are some bugs, however, and you need to know the workarounds to see how this is working. See below for details.
• 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 was 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.
• We would also like to hear from users of IMEs for Chinese and Korean. Write to: netscape.public.mozilla.i18n about your findings.
• Critical IME bugs -- you should know the following workarounds to use IMEs effectively.
• On all platforms:
• If you turn on an IME and insert a cursor into a text field of any kind and start inputting multi-byte characters, e.g. Japanese, the apprunner will crash. Workaround: Before starting to input via the IME, insert 1 ASCII character such as a space character into the field. Then turn on the IME and input CJK characters. This will avert a crash.  By the way, after inputting Japanese characters, you can then delete the ASCII character by backspacing over it.
• On Unix: In addition to the CJK crash bug, you need to be aware of  the following bugs for Unix IME.
• In addition to the crash bug as described immediately, you need to be aware of the following bugs on Unix.
• The over-the-spot position of the input area is not well-aligned when you first start inputting character. It is positioned above the top edge of the current window. You will not see the characters well until the first input has been committed. Once the initial string has been committed, the next input process brings down the IME input area to the visible position.
• In form input field, no CJK characters can be committed when you press the "Enter" key, i.e. the field displays no input.  Because of some critical problems, the commit key action for IME has been disabled for M10. This will be fixed shortly in M11 but until then, you can use the following workaround to retain the input. Taking Japanese kinput2 as an example,
• First, before turning on the IME, insert one ASCII space or character into the form field to avoid a crash.
• Next, turn on the IME (e.g. kinput2) and position the cursor next to the 1st character.
• Start inputting Japanese.
• Then when you are ready, just turn OFF the IME. You should now see the characters you just typed in.
• Form Password field input bug:
• Due to a bug, the form password input is not concealed when you engage CJK IMEs. 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 password input as you enter characters.
• Copy/paste in Non-ASCII strings: Basic intra-application copy/paste is now working for non-ASCII strings.
• 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 (e.g. from Mail compose subject header to body text area)
• Known bugs: Copy/cut and paste for non-ASCII string  is not working in the following areas
• from one application to another
• from one text area to another text field (e.g. Mail compose text area to the subject field)
• from one text field to another (e.g. from subject field to the "To" " field.)
• within the same text field (e.g. copy a string in Browser location window and paste into another position in the same location window.)
• 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 editted document in that chracter set. Bugs or comments to: Bugzilla or netscape.public.mozilla.qa.i18n. Here are some known bugs.
• 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.
• There is a bug in that when the same-named document is saved, the new document not replace the old one.
• Summary of what has been enabled up to M 10:
• CJK IMEs on Windows and Mac.
• IME on Unix enabled. (Known to work for Japanese. Other languages not tested.)
• 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.
Localizability:
• Localization framework has been explicitly defined:
• We have published a guideline for localization. Anyone interested in localizing Mozilla into a native language should read this document carefully.
• Here are some basic ideas to keep in mind when localizing Mozilla.
• Do not localize .xul files directly. All localizations must take place in corresponding  .dtd files or property files.
• Most localizable strings have now been extracted from .xul into .dtd (or property files) files. The .dtd 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/default directory.  (Note: Some samples of property files, which can also be localized, are found under ../res directory but there are currently only a few examples of this type of files.)
• If you create a .xul file then you need to extract localizable string into a corresponding  .dtd 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.
• XUL/XML/RDF files assume the default charset to be in UTF-8. If you change UI strings to your favorite language, they should show OK as long as the localized files use UTF-8 charset. (You can change menus to Japanese, for example, in ..chrome/navigator/locale/en-US/navigator.dtd file using the method suggested above and then convert the DTD file to UTF-8.) The menu items generally cannot be in languages your system does not support, e.g.  no Japanese menu for US Windows is possible at the moment.
• All non-ASCII .dtd and .property files must be in UTF-8 encoding, which is Mozilla's default encoding for resource files. You do not need to explicitly mark the resource files with this encoding, Mozilla will assume that they are in UTF-8 if there are no charset tags.
• UTF-8 conversion utility:
• Use convenient converter utilities such as "uniconv" (for Windows and Unix) or "native2ascii" utility included in the latest JDK.
• New Character Set conversion utility!: Mozilla now has its own Character Encoding conversion utility (courtesy of Frank Tang) in the binary distribution. It is called nsconv and is installed in the same directory as your apprunner executable. You can use any Character set names recognizable to Mozilla in the use of utility. Here's the basic command line for using this utility:
• nsconv -f source_charsetname -t target_charsetname source_filename new_filename
• Type nsconv for instructions.
• DTD/XML encoding definition is now supported -- thus  you can use charsets other than UTF-8 as the resource file charset, but using charset other than UTF-8 is not recommended for Mozilla localization. We assume UTF-8 as default. Cf. Bug 4431.


Mail/News (Testing done on Windows only):

• Preferences file: prefs.js (Note: Up to M8, the Preferences file was named prefs50.js. This file name must be prefs.js instead for all later Milestones.)
• Preferences changes for M10:
• There have been a number of changes affecting mail related preference settings. Read this section first before you look at Mail specific preferences.
• SMTP sever setting:
• In M10, the outgoing mail server settings have been changed. 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. If you want to learn more about how SMTP setup and multiple mail mail accounts, read this document.
• Password: Starting with M9, Mozilla now ignores the password provided in the prefs.js file. You will be asked to provide a password via a dialog prompt. If you want Mozilla to remember your password, insert this line into the prefs.js file.
 
user_pref("mail.server.server1.remember_password", true);

where "1" in "server1" should be changed to match your server number.

• Mail (POP & IMAP) and News viewing does not work unless you have a correct prefs.js file in the correct location for your platform. Read this page and set up the correct preferences before you do any mail testing. For the location of the prefs.js file, read the installation instructions for your platform on this page - see above.
• In addition to the general preferences items, international users might want to pay attention to the following lines in the prefs.js. The first controls HTML/Plain Text mail option, the second and the third control sending out properly MIME-encoded mail body and headers, respectively. If you want to send Plain text mail, set the first option's value to "false".  The MIME options are to be touched only if you need to test non-MIME mail send. Here are the relevant prefs.js settings.
• user_pref("mail.identity.idX.compose_html", true);  <-- default is "true"
• ... where "X" in 'idX' should be replaced by a number which corresponds to your account identities number, e.g. id0, id1, etc.
• The above is for HTML mail send. For Plain Text mail send, change the value to "false".
• Prior to M8, this was controlled by:  user_pref("mail.identity.idX.send_html", false);  <-- this has been obsoleted.
• MIME-related:
• user_pref("mail.strictly_mime", true);  //No need to set this line unless you want a false value for special testing.
• user_pref("mail.strictly_mime_headers", true);      //No need to set this line unless you want a false value for special testing.
• Downloading POP mail for the first time:
• If the POP Mail directory designated in your prefs.js file contains no existing folder (i.e. new), it may require patience to get your mail downloaded for the first time.  POP mail downloading could be slow and depending on how many messages the server has, it may take 5-10 minutes for the downloading to complete. We recommend not using an account which has more than a few hundred messages in it. The performance in this area has improved much since M9 and so Mozilla should be able to handle a mailbox with a few hundred messages without much trouble, however.
• The POP option is for leaving mail behind on the server after the messages have been downloaded.
• How various mail-related international functions are working at M10:
• Address Book: now 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
• Each card view pane -- displays non-ASCII strings
• Can re-edit existing cards with non-ASCII entries.
• New message button -- quotes non-ASCII names correctly
• Composer Address Picker -- now select non-ASCII names correctly.
• Address auto-completion is now working but for ASCII display only. If an Address Book entry contains non-ASCII characters, they are not displayed correctly.
• 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, you can get Bitstream Cyberbit font 2.0 here.
• 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.
• Viewing non-ASCII attachments: generally working but there are some bugs
• Plain-text attachment sent from M10 has an incorrect Content-type header and cannot be viewed inline by M10. Plain text attachments from other MIME-complaint mailers are displayed correctly.
• 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.  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 is not effective for attachments.
• Multiple attachments in different languages: can now be viewed without changing the charset menu if each attachment's header contains a correct charset parameter.
• Japanese attachments auto-detection improved further for M10: The Japanese auto-detection module has been further improved. Display of non-ASCII attachment names is also working.
• The auto-detection module set for the Browser via its new charset detector menu will also work to detect the charset of mail attachments. See above on how to set an charset detection module.
• Currently there is a bug which corrupts EUC-JP attachment display. To work around this problem, we have put in a mail specific charset detector which only works in Messenger. (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 dto 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 pres.js file, insert the following line:
• user_pref("mail.charset.detector", "jaclassic");   <-- this is basically a detector module used for Communicator 4.x.
• 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 Latin 1 folder name: displays OK. Multi-byte folder names (e.g. CJK) don't work yet.
• International Sorting in Thread pane headers:  now works well in the Subject and Sender headers on all platforms. 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.
• 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:
• Important: M10 has a bug which freezes the Messenger when a file with more than 8K in size is attached. This has been resolved in M11 but M10  contains this bug.
• File | Send Page is not working currently.
• 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. Le us know how we are in sending messages in other languages. Send your report to: netscape.public.mozilla.qa.i18n.
• Composing CJK mail messages:
• Important: There is an Editor bug (for all platforms) which leads to a crash easily if a workaround is not taken when inputting with an IME. Read the section on Editor for a workaround suggestion.
• Composing Latin 1 mail messages:
• In Reply/Forward, quoting of Q-encoded Latin 1 Subject header and QP-encoded body text fails in display in the Message pane. (Quoting in the Subject field itself works correctly). Latin 1 headers encoded with CERs are quoted correctly. Since Q-encoded or QP-encoded strings are used primarily in plain text mail, that is where you will encounter this bug normally.
• Domain Name completion: is now working. An user ID only input will be automatically supplied with the default domain address.
• 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)	Yes	Yes (M9 bug was fixed)
Body - HTML	Yes (HTML entities are used for 8-bit characters)	Yes
Body - plain	Yes	Yes
Reply/forward header	Yes	Yes
Reply/forward body html	Yes -- POP mail, IMAP, NEWS	Yes -- POP mail, IMAP, NEWS
Reply/forward body plain	Yes - IMAP, POP, News.	Yes - IMAP, POP, News
Send/View Attachment(s)	Yes (Send - local file only..)	Yes (Send - local file only.)
Copy/paste into headers and body	Yes (accented characters copy OK)	Yes  (from headers to body) No (from body to headers)

Notes on Composing Latin 1 and Japanese Mail messages:
• Composing Latin 1 Mail:
• Copying/pasting accented characters into the headers and  body works
• 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.
• 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: works both for HTML and Plain text mail now.
• Basic Japanese input works for body.  Japanese input/copying  into the headers and body also work.
• Mail goes out in ISO-2022-JP.  Header is B-encoded. (The Kanji-in escape sequence is now correct -- 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, 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 and Linux)
• We don't currently test these platforms for international features. Though we cannot vouch for accuracy, many of our Windows features should be available on these platforms also.  Linux mail is somewhat behind Windows and Mac, but catching up fast.

Features that are not supported in M10:

• No CK IME support on Linux. (Japanese IME is support is now available.)
• No CJK printing on Linux.

 
List of Charset Converters available at M10:

Single-byte:

• 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).
Multi-byte:
• 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.
Stateful:
• Japanese (ISO-2022-JP), Unicode (UTF-7, IMAP4-modified-UTF7- Needed for IMAP folder names)