M5 Release Notes

• Installation Instructions - Unix
• Installation Instructions - Win32
• Installation Instructions - Mac OS
• Files Created or Used
• Limited Support Features
• Known Issues
• International Issues

Installing the M5 Release Build

Unix Instructions

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-M5.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

Note: Bookmarks are temporarily reading the file "mozilla/package/res/rdf/bookmarks.html." instead of "~/.netscape/bookmarks.html". You can copy your bookmarks file as a workaround for now:

Mail Instructions for Unix

The current build reads the following preferences. For Windows, Mac and UNIX, the name of the preferences files is "prefs50.js". The preferrences file must live at ~/.mozilla/prefs50.js

Only change the red dummy values. Leave everything else the same. Make sure you have those first three lines (two comments and one new line).

// Netscape User Preferences
// This is a generated file! Do not edit.

user_pref("mail.accountmanager.accounts", "account1");

user_pref("mail.account.account1.server", "server1");
user_pref("mail.account.account1.identities", "id1");
user_pref("mail.server.server1.type", "pop3");
user_pref("mail.server.server1.hostname", "dredd");
user_pref("mail.server.server1.userName", "test");
user_pref("mail.server.server1.password", "clear text pop password");
user_pref("mail.server.server1.directory", "/disk/test/mozillamail");
user_pref("mail.identity.id1.fullName", "Mozilla Q. Dragon");
user_pref("mail.identity.id1.organization", "mozilla.org");
user_pref("mail.identity.id1.useremail", "test@netscape.com");
user_pref("mail.identity.id1.smtp_server", "dredd");
user_pref("mail.identity.id1.smtp_name", "test");

Unix Specific Notes:

• Don't set the "mail.server.server1.directory" pref to your real nsmail directory. Instead, make a copy of your nsmail directory and point the "mail.server.server1.directory" pref to that copy.
  
  
• Make sure that the directory you set as your "mail.server.server1.directory" exists. (#4861)
  
  
• Folders with a more than 100 messages will take a long time to load the first time.

Win32 Instructions

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

The current build reads the following preferences. For Windows, Mac and UNIX, the name of the preferences files is "prefs50.js". If your binary lives in C:\tmp\package\bin\apprunner.exe, your preferences file must live here: C:\tmp\Users50\Default\prefs50.js.

// Netscape User Preferences
// This is a generated file! Do not edit.

user_pref("mail.accountmanager.accounts", "account1");

user_pref("mail.account.account1.server", "server1");
user_pref("mail.account.account1.identities", "id1");
user_pref("mail.server.server1.type", "pop3");
user_pref("mail.server.server1.hostname", "dredd");
user_pref("mail.server.server1.userName", "test");
user_pref("mail.server.server1.password", "clear text pop password");
user_pref("mail.server.server1.directory",
"c:\\program files\\netscape\\users\\test\\mail");
user_pref("mail.identity.id1.fullName", "Mozilla Q. Dragon");
user_pref("mail.identity.id1.organization", "mozilla.org");
user_pref("mail.identity.id1.useremail", "test@netscape.com");
user_pref("mail.identity.id1.smtp_server", "dredd");
user_pref("mail.identity.id1.smtp_name", "test");

Note: If you are unable to send mail, make sure the directory specified at "browser.download_directory" actually exists.

You can bring up Messenger using any of these methods:

• From within apprunner's UI under Tasks | Messenger



• From command line using -mail argument

Mac OS Instructions

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.)

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

The current build reads the following preferences. For Windows, Mac and UNIX, the name of the preferences files is "prefs50.js". The preferences file must live in your startup volume, the one that contains the active System folder, at: :Documents:Mozilla:Users50:Default:prefs50.js.

// Netscape User Preferences
// This is a generated file! Do not edit.

user_pref("mail.accountmanager.accounts", "account1");
user_pref("mail.account.account1.server", "server1");
user_pref("mail.account.account1.identities", "id1");
user_pref("mail.server.server1.type", "pop3");
user_pref("mail.server.server1.hostname", "dredd");
user_pref("mail.server.server1.userName", "test");
user_pref("mail.server.server1.password", "clear text pop password");
user_pref("mail.server.server1.directory", "/HD/System Folder/Preferences/Netscape Users/Test/Mail");
user_pref("mail.identity.id1.fullName", "Mozilla Q. Dragon");
user_pref("mail.identity.id1.organization", "mozilla.org");
user_pref("mail.identity.id1.useremail", "test@netscape.com");
user_pref("mail.identity.id1.smtp_server", "dredd");
user_pref("mail.identity.id1.smtp_name", "test");

Additional Macintosh Specific Notes:

• The directory path "mail.server.server1.directory" must be described using Unix syntax (start the path with a "/" and use a"/" as folder separators) and not Macintosh syntax (don't use a ":" as a folder separator).
• The message pane in the 3-pane mail window has a layout rendering problem (#2236, #5450).
• IMAP and NNTP are not supported yet.
• VCard display is not supported yet.

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

Additional Mail Functionality

All Platforms:

The multiple POP accounts feature is available for you to try out. In your preferences file, add another account name to this line:

You will need to have identity and server information for the second account. For example:

where id2 and server2 preference lines exist and point to actual servers, etc.

Win32 and Linux:

You can bring up the Address Book and see the UI. However, the data is hardcoded at this time and you cannot make any address book entry changes or additions.

Mac OS:

Address Book and News are not implemented in M5.

Known Issues

• Clicking OK or Cancel in the Preference dialog may cause the browser to crash. (bug 5844)



• Visited links don't show up in a different color. (bug 3437)



• Opening multiple browser windows causes unpredictable results. Any URL entered into a new browser window affects only the first window. Closing multiple windows in the wrong order can cause a crash.



• The Sidebar may appear collapsed when you first launch Apprunner. The Sidebar collapses when you resize a window.



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



• You cannot copy and paste in the Location bar.



• Several problems are under investigation for the URL http://my.netscape.com. My Netscape is diverted to the Netscape home page on all platforms.



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



• 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 Communicator directory: npjava32.dll, npjava12.dll and npjava11.dll.



• 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.



• The following toolbar and menu items are either not fully functional or disabled:



• The Back button doesn't work with manually entered URLs or URLs accessed through bookmarks



• The Stop button fails intermittently



• The Close menu item doesn't work (use the close box to close windows)



• 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- .



• Information about preferences related to saving username/password or form data:


• To see a warning prompt before saving username/password or form data, set the following preference (by hand) in your prefs.js file:
user_pref("wallet.useDialogs", true);

This pref is false by default, so saving will be done silently. This is done because there currently are no dialog boxes and the warning prompt would occur in the console window.



• To suppress saving of form data altogether, set the following preference (by hand) in your prefs.js file:
user_pref("wallet.captureForms", false);

This preference is true by default.



• To supress saving of username/password, set the following preference (by hand) in your prefs.js file:
user_pref("network.singon.rememberSignons", false);

This preference is true by default.




• If you have local folders with many saved messages (hundreds or thousands), don't point the Mail application at your actual local folder hierarchy. All folders reparse at startup, and vast quantities of memory could be consumed if your total number of messages is high.



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



• Issues in the Mail Compose window:



• Closing the compose window in Mail will result in a crash; you must leave the compose window open even after you've sent a message. (bug 5793)
• The cursor does not appear in the message field until you begin typing.



• At the end of a line, you may need to press Enter twice before the cursor moves to the next line.



• 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.



• Windows only:



• You may not be able to subsequently enter text into any compose window after the first try, due to editor timing problems.



• 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.



• Preferences now load, but are not completely functional.



• The CSS property "bgcolor" does not work.



• The Wallet feature does not work correctly.






• Mac OS only:



• The message pane in the mail three-pane window is not properly laid out (the message pane is divided into two parts). (bug 5450)



• Messages are displayed in the thread pane with the year "1929." Internally, the messages are stored with the correct date; this is a display problem. (bug 5934)



• The Application menu does not appear when Apprunner is on top. You can click on another application or the desktop to switch applications. You can also use Command-Tab to cycle through applications.



• Resizing windows occasionally causes failures.



• Print is not functioning.



• Increasing allocated memory to greater than 35 MB causes Apprunner to crash on launch.



• There is unexpected behavior on the Mac when sidebar categories are selected. Expected behavior: Clicking once on a category should select it, and clicking twice should open it. Actual behavior: Sometimes a single click opens a category, and when this happens the previous category is highlighted after the single-clicked category opens.



• If an included .css file is missing, the application will crash.



• Cookies are not yet ready.



• Linux only:



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



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



• Java is not yet implemented.



• In the mail compose window, pressing the backspace key may cause a string of text to be duplicated. (bug 5867)



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



• You can use an environment variable to alleviate the small font problem:

setenv GECKO_FONT_SIZE_FACTOR 1.5


• Bug 4103: On Linux, a crash occurs if you:



1. Start apprunner.



2. Select "File / New Browser Window."



3. Close a window.



4. Select "File / New Browser Window." a second time.



• Solaris only:



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

M5 International Issues

For updated information on features, fonts, and testing for Internationalization, visit the International Info & Testing Hints for Milestone Builds page.

Browser

• Improving muilti-font rendering on Win:



• Euro display on Win95/98 is now enabled. (This was a bug in M4.)



• All printing used to be done in Arial only. This M4 bug was fixed. (See the menu; Debug | Viewer | Demo #0 page.)



• Other bug fixes:



• Win95-J crashing bugs



• Additional converters are now in:



• Single-byte/Unicode converters: Western (ISO-8859-15), Armenian (ARMISCII-8), Baltic/North European (ISO-8859-4, Windows-1257) , Celtic (ISO-8859-14), Cyrillic (ISO-8859-5,Windows-1251, KOI8-R, MacCyrillic), South European/Esperanto/Maltese (ISO-8859-3), Nordic/North European (ISO-8859-10 aka Latin6), Arabic (ISO-8859-6) - (not in spec, might be removed later), Hebrew (ISO-8859-8) - (not in spec, might be removed later), Thai (TIS-620), Ukrainian (KOI8-U, MacUkrainian), Vietnamese (VISCII, Windows-1258, VIET-VPS, VIET-TCVN5712), other Mac encodings (MacCroatian, MacIcelandic, MaRomanian)



• Multi-byte/Unicode converters: ISO-2022-JP (for Japanese mail)



• These converters in addition to the ones added in M4 make it possible for Mozilla to display pages written in these character sets. Note, however, that Mozilla has not implemented any bi-directional layout routines and therefore, Arabic and Hebrew display may be possible with these converters but whatever you get in this regard are accidental. In the final commercial binary product, we may remove these bi-di converters if the bi-di support is not completed. However, developers are welcome to make use of them and the converters will remain in the mozilla sources.



• On Linux -- because we have not completed GFX Multi-font rendering part yet, display works only for Latin1 and Japanese at the moment. Not much change from M4 here.



• On Mac: Multi-font rendering is being re-written and will not be ready until M6. It does work right now but the layout foundation will change dramatically by M6 and testers should wait until then for serious testing. What you find as faults at this point will have to be looked at again any way when the new layout code is in.



• View | Character Set menu: is now working! You can switch to different encoding when encountering a page which does not have a meta charset tag. You will not see a checkmark next to the menu item yet , however.



• The list is currently too long and unwieldy. This issue will be dealt with in the future.



• For pages which have meta charset tags, you may still need to reload the page to get correct display.



• On Mac, some menu items are dimmed due to the limitation on the number a Mac menu can carry. This problem will be fixed in future. Though the menu items are dimmed, the converters for these charsets are working. So if you have a web page which has a meta tag indicating its charset, display should work. You can edit the file called "../res/samples/navigator.xul" to re-arrange the order of Character set menu items. Look for a section which begins: <menu name="Default Character Set"> and place the Character set names you want to the end of the list. You may have to play with the order a few times to get them the way you like.



• On Linux/Unix, long menu items are currently not scrollable due to a bug. This affects the Character set menu also. The number of Character set items you see depends on your monitor size and resolution. If you would like to see your favorite charset toward the top of the list, you can edit a file called "../res/samples/navigator.xul". Look for a section which begins: <menu name="Default Character Set"> and place the Character set items you want to the top of the list.



• On some NT4 machines, reloading may not work. If you have one of these machines, you need to switch the View | Character Set menu before you go to the next site. Hopefully you know ahead of time what charset the page is using.) If you experience the same problem of not being able to reload, please let us know and provide info on whether or not your problem is reproducible.

Editor

• Input method - on Windows, we can now do very primitive Japanese input. There are several IME related bugs which make inputting Japanese very difficult. These bugs are scheduled to be fixed in M6.

Localizability

• Some do-it-yourself localization is now possible.



• XUL/XML/RDF files now 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 res/samples/navigator.xul file and then convert the file to UTF-8 charset.)



• Limitation: you cannot specify other charsets yet since XML parser support of general entities in the external DTD files is yet to be done. Although it is possible to have resource files for Mozilla to be in charsets other than UTF-8, keep in mind that Mozilla will be standardizing on UTF-8 for resource files.

Mail/News (Windows Only)

• Multi-lingual mail viewing is now working: 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. We pay attention to the charset parameter in the Content-Type header and switch to an appropriate font. The Encoding 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.



• View Japanese mail body -- mostly working now. Occasionally where there is a line break, some unwanted characters will show up. This is scheduled to be fixed in M6.



• View | Character Set menu for New Mail Compose window is now working fore sending mail. Switch to Latin 1 or ISO-2022-JP before sending a message. You will not see a checkmark next to the menu item yet , however.



• Sending Latin 1 mail via POP3



• Copy/paste accented characters into the headers and body works



• Keyboard input into headers (e.g. subject) also works for accented characters. Using the English keyboard, ALTGr + 0+Number Keypad method works, e.g. Right ALT key + 0232.



• Make sure to switch the View | Character Set to Latin 1 before you send out a message.



• Basic MIME compliance is there: Header Q encoding, and Body QP encoding for accented characters.



• Sending Japanese mail via POP3



• Basic/primitive Japanese input now works. The mail composer body can retain Japanese input. Japanese input into Subject header does not work yet, however.



• Mail goes out in ISO-2022-JP. (The Kanji-in escape sequence is that of JISX0208-1976, however. This will be fixed by M6.)



• Make sure to switch the View | Character Set to Japanese (ISO-2022-JP) before you send out a message.



• The Japanese content used to disappear upon sending. This bug was fixed recently.



• Sending other charset mail -- has not been enabled yet. There also seem to be bugs with some international keyboards for input.



• You can now play with View | Character Set menu and add your favorite charset. Look for a file called msgcompose.xul in the directory, ..x86rel\res\mailnews\compose directory, search for a string "<menu name="Character Set">". When you find it, you will see how the 2 Character set menu items for Latin 1 and Japanese Mail send have been constructed. Just add your charset name basing the name on what you find in the Browser's View | Character Set menu.



• 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 and so there is no guarantee that correct characters will be input. Copy/paste may work better. Let us know what you find if you try this.



• prefs.js file for M4 can be re-used for but there have been slight changes for M5. First, the name is now prefs50.js. Second, there are some other changes which make some M4 prefs.js lines unnecessary. If you would like an M5 sample prefs50.js file, you can find it here. The location of the prefs50.js file has also changed. On Windows, this file now must be placed under a directory 2 levels up from the directory which contains the apprunner executable. For Unix, the directory is $HOME/.mozilla. If you have never run a Mozilla apprunner before on Windows, then look for a new directory called Users50. You'll find the prefs50.js file under the Default sub-directory. If you ran an earlier Mozilla version on Windows, find a file called mozregistry.dat in the top level directory of your Windows operating system directory. Delete this file before you start M5 build for the first time. This will force M5 to create Users50 directory. On Unix, you will find registry file under $HOME/.mozilla -- You might want to delete the old one before you start a new M5 build.

Features that are not supported in M5:

• No CJK IME support on Mac and Linux.



• Linux can only view Latin and Japanese.



• No Japanese Auto-Detect.



• No posting non-ASCII forms data.



• No CJK printing on Linux.



• HTTP charset won't be handled.



• Viewing Latin 1 & Japanese newsgroups



• Sorting in mail headers



• Proper change of date/time format in headers



• Sending/receiving IMAP mail