If you are using Netscape Communicator Professional Edition (which includes Netscape Calendar, IBM Host On-Demand, and AutoAdmin) please read the information contained in these notes. In addition, you can click here to view the Release Notes specifically for Professional Edition.

• What's new in Preview Release 4
• Known issues in this release
• Security information
• Developer information
• International information
• Helper applications information

Additional information is available:

• From the Help menu, choose Help Contents
• Technical Notes

General and Setup

• Enhanced visual appearance and user interface
• Task bar that enables easy access to Communicator components
• Context-sensitive NetHelp for Windows 16-bit platforms
• Cross-platform support
• New animation indicating network activity
• Multiple user profiles

Navigator

• AutoComplete in the URL location field
• IIOP distributed objects
• If a system halt related to the Kernel32.dll occurs, update the kernel. You can obtain the update from http://www.microsoft.com/kb/articles/q148/3/36.htm. This may correct the problem.
• Symantec JIT
• Dynamic font support (including bitstream font displayer)
• New security information manager
• Enhanced kiosk mode
• Improved OLE support
• Java
• Communicator now supports Java and LiveConnect on all platforms
• Support for IIOP distributed objects
• Internet Foundation Classes 1.1 support
• A Java LDAP API support
• Support for JAR files
• Additional JavaScript enhancements
• Layering and absolute positioning
• Style sheets support
• Dynamic layers support

Composer

• Enhanced Composer plug-ins (now includes event model)
• Publishing enhancements for easy one-button publishing
• Table-editing enhancements
• Keyboard navigation
• WYSIWYG HTML editing
• Integrated with Messenger and Collabra
• Improved line- and character-spacing behavior
• Improved tool bars
• Spelling checker
• Japanese inline input
• Image resize
• Image import

 Messenger

• Improved performance when accessing server (IMAP) mail accounts
• LDAP retrieval of digital certificates for secure mail
• Support for mailing documents directly from desktop applications that support MAPI send
• Background colors and images for mail messages
• Encrypted/Signed Messages (S/MIME)
• Synchronized offline IMAP4
• End-user management of account (vacation and password changes)
• Intelligent sending of HTML, plain text, or multi-part alternative
• Rules and filters for IMAP server folders
• HTML compose with the ability to drag and drop images within a message (MIME HTML)
• Quoted text with HTML
• Intelligent sending of HTML or plain text based on address book entries

Collabra

• Fast message searching using the indexed search capabilities of the Collabra Server
• Ability to save search results on the Collabra server and create a Virtual Discussion Group
• Drag and drop links to a discussion group or individual message
• Background colors and images for discussion messages
• Offline reading of discussion groups
• End-user management of discussion groups on Collabra Server 3.0. Ability to create:
• groups
• categories
• access control lists
• Display to categories in Message List window with Collabra Server 3.0
• HTML compose with the ability to drag and drop images within a message (MIME HTML)
• Quoted text with HTML
• Ability to read and post to Internet newsgroups

Cosmo Player 1.0 (Win32) & Live3D (Win16)

• Improved lighting with Renderware 2.1 and new color model (Win32 only)
• Full support of route in and out for all Node fields (Win32 only)
• Rendering and event-handling performance enhancements (Win32 only)
• Rendering support for Intel's MMX extensions (Win32 only)
• Full PROTO support
• Full EAI support (Win32 only)
• Text/AsciiText and FontStyle Support
• Calculation of fieldOfView based on latest DIS spec changes
• Improved sensor handling and routing
• Full VRML 2.0/1.x support (including Live3D 1.0 extension nodes)
• JavaScript supported in Script Node
• Per-Vertex Colors
• Support for 3D sound using Intel's RSX Technology (Win32 only)
• Support for 256x256 and MPEG textures
• Improved lighting and material models
• Support for large data sets
• Improved collision with terrain following
• Support for MFString URLs

Conference

• Voice Mail for Windows 32-bit platforms can be compressed using either the Voxware ultra-low bit rate RT24 codec or the Lucent Technologies, low-bit rate high-quality speech, elemedia SX8300 codec
• Attendant mode allows the main interface to be hidden and still listen for incoming calls.  An icon appears in the Task bar tray to recall the main interface (Windows 95 and Windows NT 4.0)
• New high-quality elemedia SX8300P speech codec support
• New ultra-low bit rate Voxware RT24/29 codec support
• New Lucent Technologies G723 compliant audio codecs for Windows 16-bit and 32-bit platforms.

General and Setup

• This release has not been fully optimized for size or performance. 16 MB of RAM or more is recommended.
• Plug-ins installed in previous versions of Navigator are not automatically transferred to Communicator. Re-install these plug-ins.
• On some intranets, the default Collabra server is a secure Collabra server. The setup wizard does not have any way of specifying the default discussion host as a secure Collabra server.
• The browse button on file forms does not work.
• Pages containing layers cannot be printed.
• The cookie preferences from Navigator 3.0 is disregarded. If you want to be prompted before accepting a cookie, or if you want to reject all cookies, you must set this preference again.

Composer

• Composer does not resolve links properly if escape characters are contained in the URL.
• Two-page Composer windows might cause your system to hang.
• NetHelp is not available for all dialog boxes for Windows 3.1.
• You might experience a system halt if you use the Alt keyboard shortcuts to or from an open Composer window. Use the mouse to move between windows.

Messenger and Collabra

• You need a certificate of your own (in addition to the recipient's certificate) prior to sending any encrypted mail to the recipient.
• In the offline state, choosing the Send toolbar button in the Compose window places the message to the Outbox to send at a later time.
• In the offline state, accessing getting new messages causes Communicator to try to go online.
• The No Pages to Print error occurs if you have scrolled down to the bottom of a message. Scroll back to the top of the message and print again.
• If you get a system halt when invoking the Compose window, rename abook.nab (address book file) located in your Users Profile directory.
• Shortcut keys might not bring up the correct dialog or perform the correct action for Windows NT 3.51.
• In the Mail and Discussions Preferences, Identity section, include a valid user name and domain name in the Email field (for example, johndoe@company.com). If you do not include the domain name, a system halt might occur when using Composer.
 
Messenger
• The progress dialog remains at 100% for longer than necessary before continuing to download other messages, especially when using filters for incoming messages. This can be ignored.
• If you encounter a general protection fault in msvcrt.dll when sending a message, exit Communicator.  This is caused by a .tmp file Windows limitation. See your system administrator or equivalent about removing these .tmp files.  Afterwards, you can send messages from Communicator.
• The Empty Trash Folder menu item is disabled from the Message List window. Empty the Trash folder from the Message Center.
• When you open a saved draft message, the names in the Reply to and Follow up fields are not listed.
• After you get new messages, the message you had selected before downloading stays current. To get to the first new (unread) message, click Next on the toolbar.

Mail with IMAP Servers

• Your system may halt when you search for messages using the status criteria is replied, is forwarded, or is read.
• When using Communicator with some IMAP servers, you may wish to specify an IMAP mail directory.  Access the Mail & Groups Preferences. Under the Mail Server section, choose More Options. Specify the mail directory in this dialog. Exit and restart Communicator.
• When creating IMAP4 folders on a mail server, use only ASCII characters. If folders are named with European accented characters or Chinese/Japanese/Korean double-byte characters, the names are unreadable. Once created, these folders cannot be deleted.
• Filing a message from a discussion group in an online folder results in an empty dialog. File discussion group  messages in a local mail folder.
• You might get prompted for a POP password when sending a message under IMAP. Enter your POP password and the message is sent.
• After switching between IMAP and POP servers, exit and restart the application.
• You can specify a directory for your IMAP folders. Set this preference in Mail and Groups preferences under the Mail Server section. Click More Options and set the IMAP mail directory.
• If you mark all messages Read or Catch up by Date, the next time you get new messages, those messages become marked as unread again.  Manually mark each message as Read by selecting each one or clicking the green Unread indicator in the Message List window.
• Mail filters are supported on server folders in IMAP mode, but not for local folders.
• From the Message Center, the File, Empty Trash Folder menu item is enabled after you select a mail folder in the Message Center. Emptying the Trash empties both your online Trash folder, as well as your local Trash folder (POP server), if one exists.
• MIME HTML messages (mail with embedded images) does not display properly when read with IMAP.
 
Collabra
 
• Searching discussion messages command is case-sensitive.
• Composing a message to a discussion group with the Compose menu item (and not using To: Discussion from within the discussion group) sends the message to the default server. An error message occurs if the discussion group is not on your default server. Compose a message from within the discussion group so the To: Discussions toolbar or menu item is available.
• The unread and total counts displayed in the Message List window are per category.

Categories within Discussion Groups on Beta Collabra Server

• You can access categories created on Beta Collabra Server 3.0, which supports category creation. The Message List window shows the categories in the upper-left pane.
• A time delay might occur when marking a large (for example, 10,000 messages) discussion group as read using the Catch up by Date feature.
 
Windows 16-bit Issues
 
• Your system might halt when adding a secure news or discussions server that has an incorrect certificate.
• With some graphics cards, you might notice a flashing in the address pane in the compose window.
• You might be unable to select the address, attachment, or options tab in the compose window. Place your cursor in the Subject field before changing to or from the address, attachment, or options tab.
• On slower systems, there might not be appropriate feedback as you access the Subscribe to Groups dialog. If you hear the hard drive being accessed, then Communicator is still active. It may take a few minutes for the list of discussion groups to display.

Conference

• Conference needs to be running to receive calls.
• The Collaborative Browser does not work with JavaScript pages that require user action and anchors linking different portions of forms.
• Frame support during collaborative browsing is limited.
• Calling a fictitious user prompts you to leave voice mail.
• Calling a valid user that has selected the Do Not Disturb option notifies you they are not available but does not prompt you to leave voice mail.
• Voice mail must always be sent in HTML-only format.
• A voice mail recipient using an IMAP server will receive the following error message:
file not found or unknown format
• Placing a call to a valid user that is running Conference but does not accept or reject your call does not time out or prompt you to leave voice mail.
• Netscape Conference does not interoperate with Cool Talk or with the Netscape 411 Server for CoolTalk.
• Netscape Conference does not usually work across firewalls unless the firewall is configured to allow UDP data to pass through.
• Closing the Conference application may occasionally cause an invalid page fault in the Voxware codec.

Plug-ins

• ViewDirector Pro2 plug-in does not work.
• Plug-ins from other companies installed in previous versions of Navigator are not automatically transferred to Communicator. Re-install these plug-ins.
• You might experience color palette problems with plug-ins and Communicator. Minimize and restore the Communicator window. Also, running in 16-bit high-color mode solves the problem.

SmartUpdate

• SmartUpdate does not work on Windows 16-bit platforms.
• If a SmartUpdate download of an item occurs while that item is open or in use on your system, you need to restart your system for the update to take place.

Netscape defines several different kinds of access that signed Java code can request. To help you evaluate the potential danger posed by the particular form of access that an applet or other Java code is requesting, Netscape has also created a classification system based on three levels of risk. You may have a different opinion of the level of risk that a particular kind of access entails. These risk levels are provided as general guidelines only. Be sure to read the description of the access requested by a particular applet and make your own decision.

Netscape's current classification system is based on these categories:

• High risk. A major security attack is possible, permitting severe damage to your system or data. Major violation of privacy is possible, such as reading any information from hard disks connected to your computer. Very significant services may be requested, such as establishing a connection over the network to a remote computer.
• Medium risk. Major violation of privacy is possible, such as reading any information from a hard disk connected to your computer. Some significant services may be requested, such as writing files on a hard disk or sending email on behalf of the user.

Low risk. Minor violation of privacy is possible, such as reading your user ID. Relatively minor services may be requested, such as writing a single file to a specified noncritical directory on a hard disk connected to your computer.

What's new

• Java
• Communicator now supports Java and LiveConnect on all platforms.
• Netscape supports the latest  JDK 1.1 functionality with the exception of the AWT which remains compatible with JDK 1.0.2 but has additional performance improvements.
• Capabilities-based Java/JavaScript security
• Support for IIOP distributed objects
• Internet Foundation Classes 1.1
• A Java LDAP API
• Significant run-time performance improvements
• Support for the OBJECT tag
• Unicode support on all platforms
• Support for JAR files
• Shift-Reload causes applets to be reloaded and restarted
• Multicast socket support
• AWT callbacks are now handled on each applet's thread
• Additional Java console commands (type '?' in the console for information)
• Extended access for trusted Java applets
• Additional JavaScript enhancements
• Layering and absolute positioning
• Style sheets support
• Improved support for the W3C working draft standard "Positioning HTML Elements with Cascading Style Sheets." Specifically, the CLIP, OVERFLOW and HEIGHT properties are now implemented and percentage values can be specified where appropriate.
• HTML Layers
• The SRC attribute has been added to the layer tag for encapsulating an arbitrary HTML URL inside a layer.
• The HEIGHT attribute was added to the <LAYER> tag.
• The WIDTH, HEIGHT and CLIP attributes of the <LAYER> tag now accept percentage values.
• The VISIBILITY attribute accepts all three legal values, including SHOW for both <LAYER> and <ILAYER>.
• PAGEX and PAGEY attributes have been added for page-relative positioning of <LAYER> and <ILAYER>.
• The <NOLAYER> tag has been added to permit authors to incorporate content for older browsers that are not layer-capable.
• Dynamic Layers
• Every layer in JavaScript now has a DOCUMENT property that scopes all the reflected HTML objects inside the layer.  Similarly, JavaScript code  exists inside a <LAYER> tag will be scoped to the containing layer rather than the window. THIS CHANGE MAY BE INCOMPATIBLE WITH SCRIPTS DESIGNED TO WORK WITH COMMUNICATOR PR2.
• It is possible to create new layers after the document has loaded by using JavaScript's new layer constructor method.
• The document.write method can be used to dynamically generate the contents of a specified layer.
• The <LAYER> tag accepts onLoad, onMouseover, onMouseout, onFocus and onBlur JavaScript event handlers.
• More sophisticated event handling can take place through the setCapture, releaseCapture event mechanism.
• All document objects now have WIDTH and HEIGHT properties, which reflect the width and height of the content of the (layer's) document and which can be used to set the scrolling limits of the window.
• HTML that can be used to set the SRC attribute (or SRC property) can now contain <HEAD> and <BODY> tags.
• There are now pageX and pageY properties that provide page-relative positioning information.
• The LOAD method has been added to the layer object.  It can be used to simultaneously set a layer's WIDTH and SRC.

The offset method for layers has been renamed to moveBy, to be more consistent with the similar method on Window objects.

SmartUpdate

For developer-related issues regarding SmartUpdate and JAR files, see the release notes for the JAR Packager, which are at: http://developer.netscape.com/software/signedobj/relnotes.html

Known Problems

Java

• In the 16-bit product, Java is not enabled when running on a Windows NT platform.  It is enabled when running that product on a Windows 3.1 platform (the normal case), as well as on a Windows 95 platform.
• JSObject.getWindow requires an applet as an argument.
• toLocaleString()method in Date Class throws security exceptions.
• Classes loaded from CLASSPATH are no longer privileged.
• FileInputStream object's available method fails.
• JDK 1.1 packages missing in this beta include java.math and sun.rmi.
• The java.security package is unsupported.
• Signed Classes and the netscape.security.Target objects. Although the targets

"UniversalFileRead" and "UniversalFileWrite" are fully implemented for the signed classes and the netscape.security.Target objects, the paramater targets "FileRead" and "FileWrite," used for individual file access grants, are not supported in this release.

JavaScript

• New Behavior
• Multi-byte character-set encodings (such as Shift-JIS) can be passed through JavaScript either as string literals or with LiveConnect to and from Java, but manipulation within JavaScript is dangerous since built-in methods do not recognize multi-byte encodings.
• In a frame, history.back, history.forward, and history.go(n) manipulate the frame's local history, not the full history of the entire Navigator window that the Back button manipulates.
• In addition to loading system classes, JavaScript can now load Java classes located at the same URL as the page.
• Unload
• The unload event is not cancelable with a 'return false' from within the onUnload event handler.
• Closing a window does not send an unload event to that window.
• In nested frames, the unload event is handled only by the top-level window.
• Resizing of windows
• You can enter a race condition with JavaScript that is currently writing to the window.
• Plain text written using document.write() sometimes changes to HTML text on resize.
• Blur
• Using window.alert inside onBlur handlers can create infinite loops.
• After reloading a page, blur() on a field may not disable input to the field.
• Form elements
• When focus is given from a form field to the top level window, then back to the form element, the form's onFocus handler does not always get called.
• In scripts not tagged JavaScript1.2, hidden form elements may not reflect correctly in a page with hidden and visible elements, with and some without handlers.
• LiveConnect
• When JavaScript code called from Java encounters an error, the error may be reported  to Java in future calls to JavaScript.
• JavaScript can halt if it attempts to call a nonexistent Java method.
• The onSelect event handler is not working.
• The Image onAbort event handler does not work correctly in frames.
• You must include new when calling Java constructors from JavaScript. For example, var size = new java.awt.Dimension (...)
• document.write does not work correctly when used inside JavaScript entities. For example, & followed by {....}.
• SCRIPT tags inside FRAMESET tags are not executed.
• Scripts longer than 30,000 characters do not work on Win16. When a script outside the URL in the location object tries to call methods of the location object, access is always denied.
• On Win32 platforms, Number(x) incorrectly returns 0 when x is a string that does not contain a well-formed numeric literal. On other platforms, it correctly returns NaN.

Layering and absolute positioning

• Layer stacking order is not preserved across window/frame resize.
• Negative values for the Z-INDEX attribute on LAYER and ILAYER tags are not recognized.
• Clicking on a link in a SRC layer, where the link has no TARGET attribute, causes the target page to be loaded into the top-level  window,  instead of replacing the layer.  It is not possible to target URLs at layers as with frames and the back/forward buttons do not work with layers.
• It is not possible to use #URLs (named anchors) as the value for a LAYER's SRC attribute.  Also, links to named anchors from a link within a layer may not work properly.
• The new width and height properties added to the document object may conflict with user-defined variables of the same name. It is recommended that scripts containing these properties be modified to use differently-named variables or that the var keyword is used to declare such variables before they are used to eliminate the conflict.
• Changing the contents of a layer (calling the load method, setting the src property, calling document.open/write/close) has certain restrictions:
• They cannot be done while the main document is still loading.
• Only one layer can be changed at a given time. Changes to multiple layers must be done serially. You can use the onLoad event handler for layers to achieve the required serialization.
• The "Find in Page" feature does not work for layers.

Style Sheets

• The use of negative margins to overlap text can cause very unpredictable results and is not recommended.
• Use CSS positioning or layers to overlap text.
• Negative margin values are only allowed for margin-top and margin-bottom.
• Do not use pixel units. Because of variances of fonts among operating systems (PC, MAC and UNIX) most fonts will not have the exact same pixel dimensions.  The use of relative units, epecially EMs which are based on the current size of the font, regardless of which font actually gets selected, is highly recommended.
• Assigning styles to the <LI> tag only effect the bullet not the text as it should.  To work around the problem enclose the text with a <SPAN> tag or assign the style to the <UL> or <OL> tag.
• Sizing images using style sheets is disabled
• Following their original web design, tables do not inherit styles from the surrounding text or style sheet.
• You cannot assign most styles to the <TABLE> or <TR> elements. Use the <TD> element instead.  Exceptions are: background image and color on the <TABLE> tag which work as expected. For other styles, results may vary depending on the complexity of the table and their use is not recommended.
• Small-caps and obliqe font styles are not supported
• Postioning of empty tag elements (eg images) is not supported
• Dotted and dashed border styles are not supported.
• Border colors and styles can only be applied to all four sides at once via the border-color and border-style properties. They cannot be set on a per side basis.
• The vertical-align property only applies to replaced elements and does not support percentage units, sub, or super.
• The background property inherits into text elements.  Apply a "background-color : transparent" if you do no want inheritance.
• Unsupported CSS attributes include:
• word-spacing and letter-spacing
•  first-line and first-letter styles
• list-style-image and list-style-position
• white-space: no-wrap
• font-variant  (see small-caps above)
• !important
• background-attachment and background-position
• In order to make pixel units print sensibly when going to high resolution printers, pixel units are scaled to a virtual display resolution of  120dpi.  What this means is that when going to a 300dpi printer, fonts that are specified as being 12px high will be output as 30px or 7.2pts which is how they would appear on a screen with a 120dpi resolution.  This is consistant with how pixel units specified via HTML tags (for example <table width=100>) are scaled.  This scaling will not cause fonts to have jagged edges since the font will be printed at the full 300dpi resolution at 7.2pts.  All other related pixel units (line-height, margins, etc.) are scaled as well.

Browser

• Browsing or displaying Unicode pages/mail/news (UTF-7, UTF-8, UCS-2) is now supported for many languages. Communicator can use appropriate font glyphs matching the Unicode code points from the user's local fonts. New encoding menu items, UTF-7 and UTF-8 have been added. Though not in the encoding menus, UCS-2 auto detection is supported.
• Unicode support includes Western, Eastern European, Cyrillic, Greek, Chinese, Korean, Japanese, and Turkish. It does not include bi-directional and complex-ligature languages.
• Communicator supports official IANA MIME Charset names. Improperly labeled pages, e.g. 'euc-kr' as 'ks_c_5601-1987', 'big5' as 'x-x-big5', and 'gb2312' as 'gb_2312-80', may not display properly.
• US Windows 95/NT users can now display Chinese, Japanese, and Korean pages/mail/news if appropriate fonts are installed. A native OS (such as Japanese Windows 95) is not required for display. If you use native Windows 95/NT systems such as Japanese Windows 95, you can display other Asian languages, e.g. Chinese and Korean, with appropriate fonts.
• The input in CJK does require appropriate native OS's or equivalents.
• In Windows 95/NT, it is no longer necessary to make registry modifications to use Unicode fonts. Communicator can now use appropriate native or Unicode fonts automatically.
• Communicator can use many different language fonts as long as they adhere to TrueType font specifications. Some public domain fonts which do not follow them therefore may not work well with Communicator.
• Dynamic Fonts (Webfonts) can now display multi-byte languages. Dynamic fonts allow web page designers to create font objects from local fonts and use them to display prepared pages exactly as designed.
• Encoding menu names have been standardized across all platforms and products.
• All Unicode conversions are now based on Unicode Standard 2.0.
• NCR (Numeric Character References) and NE (Named Entities) display properly if the character in question is available in the chosen encoding. NCR's are interpreted as Unicode code points in the decimal format following the standards in RFC 2070. If the corresponding character does not exist in the chosen encoding, then "?" will be displayed.
• Many new languages have been added in the Accept-Language Preferences Window for convenience. Accept-Language option is used to indicate the user's preferred language(s) when sending requests to HTTP servers, which in turn can use this information to send back documents matching the user's preferences.
• Communicator now automatically sends out Accept-Charset indicating the user's system default character set and UTF-8 as 'minimally' acceptable character sets. Accept-Charset information may be used to improve communication between Communicator and directory servers by providing the servers the information on what character sets Communicator can accept from them. No UI is available to change this.
• Japanese automatic encoding detection has been improved, particularly for EUC.
• Korean browsing now features automatic encoding detection between ISO-2022-KR and EUC-KR.
• Users can now display all Cyrillic encodings with Windows Cyrillic (CP1251) fonts. (E.g. KOI8-R fonts are not needed to display KOI8-R pages.)

Composer

• The HTML Composer now automatically adds character set information to the edited document in the form of a Meta Charset attribute within the <HEAD> ... </HEAD> tags.
• By default the Composer preserves the existing character encoding when saving a document. However, the user can also change it if so desired. (For Japanese, saving into ISO-2022-JP (JIS) is not supported. For Korean, saving into ISO-2022-KR is not supported.)
• Multilingual UTF-8 pages can now be composed using Windows multilingual keyboard IME's and Asian IME's. Copy/paste and drag/drop from/to different encodings are possible between Composer and Browser windows. This editing function is currently not available between multiple Composer windows.

Messenger/Collabra Discussion Groups

• An encoding menu is now available in the new Mail Composer window. This convenient feature allows users to easily change the encoding for each message without going back to the Mail Folder window.
• You can now compose and send rich-text mail (HTML) in all the languages supported.
• Searching and filtering in European /Asian languages in the local Mail folders work properly except for European language search/filter in the body of HTML mail.
• Searching and filtering in European /Asian languages are not currently supported for directories in IMAP4 servers.
• Directory search with European/Asian strings is now supported.  Communicator converts the data sent to Directory Server to UTF-8 (Unicode), and converts data received back to the current encoding.
• All Address Book /vCard fields such as First Name, Last Name, Nickname, Company, etc. now accept input in European accented-characters and Chinese/Japanese/Korean 2-byte characters.
• You can enter European/Asian Nicknames or First Names in the "To: " field, and they will be resolved to e-mail addresses from the Address Book entries.
• Searching in European /Asian languages is also supported in the local Address Book.
• Korean mail messages are now transmitted using the 7-bit ISO-2022-KR encoding. News articles are posted using the EUC-KR encoding. Currently, the same message cannot be sent to both the mail and news servers except in the 8-bit EUC-KR. We recommend sending messages separately to the mail and news servers in such a case.
• Cyrillic mail is sent out using KOI8-R encoding.
• You can now create and delete IMAP4 folder names in European and Asian languages. There may still be a slight problem in handling certain CJK characters, however.
• On NT4/NT3.5x, Communicator used to incorrectly insert the PST/PDT Time Zone into the mail header when the user's Time Zone does not use Daylight/Summer Saving time. For example, most Asian countries would be affected. This problem is now fixed.
• Each folder within the Messenger Mailbox window or Collabra Discussion Groups window can have a different encoding setting. For example, the user may store mail messages in one language in one folder and those in another language in another folder. When the user opens a folder, Communicator will automatically switch to that folder's encoding. When multiple Mailbox/Newsgroup folders are opened from Discussion Groups window, each window can have its own encoding setting. For example, the user can have multiple Mail/Newsgroups windows open at the same time, all with different encodings, and Communicator will automatically switch the encoding setting to that of the current window.



Java/JavaScript

• Windows 95/NT Communicator can now display Chinese, Japanese, and Korean strings in Java applets if the appropriate fonts are available on the system. No registry changes are required to use Unicode fonts.
• Chinese, Japanese, and Korean input is now possible in Java AWT TextArea and TextField windows. Communicator does not provide its own input method, and so the user's system must have native input methods for these languages.
• All the JDK 1.1 internationalization classes have been incorporated into Communicator.
• Passing multi-byte text from Java to JavaScript and from JavaScript to Java now works if the document encoding is correctly set to the source encoding. JavaScript String functions do not handle multi-byte characters correctly.

Known Problems

• UTF-8 page display under US Windows 95 may not work properly when the Windows 95 system has been installed using the 'Custom Install' option. In such a case, re-installing the Windows 95 system under the "Typical" install option should eliminate the problem. We are currently working on a simpler solution.
• HTML Composer cannot save documents into ISO-2022-JP (Japanese) and ISO-2022-KR (Korean).
• On Windows NT, Cyrillic/Greek/Turkish/Central European characters may not display correctly in TextArea and Text Input for HTML FORM.
• When multi-frames are created by JavaScript, the 2nd or later pages may be assigned a wrong charset. For example, a search result page may be generated this way. In such a case, re-sizing the window or re-loading the frame restores the correct display. Page designers can avoid this problem by initially loading multi-frames using conventional HTML rather than by JavaScript.
• In cases where there is a mismatch between HTTP Charset from servers and the document's own Meta Charset , the document's Charset Tag will predominate when the document is re-loaded.
• Using View/Page Info may cause the original page to misdisplay when the Page Info window is closed.
• Communicator supports only 1 encoding for multiple layers.
• An Address Book/Mail Header name resolution may insert an equivalent of ASCII backslash "\" in the display of certain Japanese and Chinese characters. This is a cosmetic problem likely to occur only with Shift_JIS (Japanese) and Big5 (Taiwan) encodings. E-mail address resolution should work all right and messages can be sent.
• There may be a slight imperfection in the Address Book resolution when there are multi-byte language entries.

In using Japanese IME's for HTML Editing/HTML Mail, Shift+Right_Arrow key will not let users advance to the next parsing candidate. This is not a problem in plain (non-HTML) mail.