********************************************

Common Desktop Environment News

Copyright (c) 1995 by Sun Microsystems, Inc.

********************************************

This document contains an Overview of CDE 1.0.1 features and other
important late-breaking information.

________________________________

Contents of the README Directory
________________________________

Aside from this document, four other documents (Bugs, PatchList,
Install_Notes, and InstallGuide.ps) are also located in the directory
/cdrom/<volume_id>/README.

o Bugs contains known problems and workarounds.

o PatchList contains a list of all the patches that are available
  on the CDE 1.0.1 CD-ROM disc, and those related to Solaris CDE 1.0.1
  that are available elsewhere.

o Install_Notes contains late-breaking information that is
  important to installation.

o InstallGuide.ps is a PostScript file of the manual _Solaris Common 
  Desktop Environment Installation and System Administration Guide_.

The AnswerBook online documentation is in the directory
/cdrom/<volume_id>/cde-min (the SUNWdta pkg).

__________________________
  
Sun Information on the Web 
__________________________
 
For information on Sun products, see Products & Solutions in: 
http://www.sun.com.

______________

Keyword Search
______________

The Keyword Search Index is a quick reference to locate keywords 
or specific subjects.  Use this list with your favorite text editor 
to facilitate your subject search:

APIs                 cursor               Lotus              project
AccessX              Data Type            Macintosh          Property Editor
Application Builder  Drag and Drop Editor MAE                sdt 
application names    features             man page           shell script
Applications         Front Panel          message catalog    Tab 
appointment          Icons	          MIME               text appointment
BIL                  Image Tool           minimized          ToolTalk
bil                  Image Viewer         module             Trash Can
bindings             icon 		  MOTIFHOME          two-button
bip                  implied apply	  Motif              UNIX keys
Buffer               internationalization mouse	             User Defined
buffer               interoperability     naming conventions user name
C++  	             LANG                 OpenWindows	     variable
Calendar             locale               OPENWINHOME	     widgets
CD Media	     login		  password	     XPG4

________________________

Overview of New Features 
________________________

Keywords: features

Here are some of the features available to you within CDE:

o Desktop tools available from the Front Panel, such as File Manager, 
  Calendar, Mailer, Text Editor, Application Manager, Style Manager, 
  Printer, Terminal Emulator, Icon Editor, Image Viewer, Workspace menus,
  and online help.

o The CDE Developer Environment is included as an optionally
  installable package for software development in CDE.  These 
  packages contain Application Builder, a tool for creating 
  graphical user interfaces that use CDE APIs; demonstration programs
  in source form for Motif, ToolTalk, and other CDE services; 
  and utility applications, man pages, and header files to help you 
  develop in CDE.


========================
CDE End-User Information 
========================

Keyboard Functions in the Login Screen 
************************************** 
Keywords: cursor, login, password, Tab, user name
 
In the CDE 1.0 login screen, if you press the Tab character in either 
the user name or the password field, the cursor moves to the next 
field -- in this case, the OK button.  This behavior renders your 
user name or password invalid if they contain the Tab key. 
 
In CDE 1.0.1, you can use Tab as part of your user name or password. 
To move the cursor focus to the next field, press Control+Tab 
instead. 
 
To move the cursor to the previous field, press Control+Shift+Tab or 
simply Shift+Tab. 
 

Image Viewer
************
Keywords: Image Viewer, Image Tool

Image Viewer, located in the Personal Application subpanel, is a
Solaris CDE application that you can use to view multiple-page
documents and single-page image files.  Refer to the online help for
complete documentation information.  The functionality is similar to
the OpenWindows Image Tool application.


AccessX
*******
Keywords: AccessX

AccessX is a set of Solaris keyboard enhancements that provides basic
X Window System accessibility to users with physical disabilities.
With AccessX, you can:

o Perform complicated key sequences serially, for example, Control-C
o Control the mouse pointer and buttons from the keyboard
o Set the key repeat and acceptance rates

Specific functions that are provided in AccessX are:

StickyKeys   	Provides locking or latching of modifier keys, such as Shift
	        and Control, so that they can be used without simultaneously 
                pressing the keys being modified.  Hence, you can perform 
                single-finger operation of multiple key combinations.

MouseKeys   	Provides keyboard-based explicit control of cursor movement
		and all mouse button press and release events as an 
                alternative to the mouse.

RepeatKeys   	Delays the onset of key repeat, so users with limited
		coordination capability can release keys before multiple
		characters are sent.

SlowKeys     	Requires a key to be held down for a set period before
		keypress acceptance, so users with limited coordination 
		capability who accidentally press keys can avoid sending 
		unintentional keypress events.

ToggleKeys   	Indicates the state of a locking key, for example, Caps Lock, 
                with a tone when pressed.

BounceKeys   	Requires a delay between keystrokes before accepting
		the next keypress, so users with tremors can prevent the
		system from accepting inadvertent keypresses.


Optional UNIX Key Bindings
**************************
Keywords: UNIX keys, bindings

Refer to Chapter 10 in _Common Desktop Environment User's Guide_
for information on how to enable UNIX key bindings.


Diskettes and CD Media
**********************
Keywords: diskettes, CD Media

CDE File Manager does not support volume management.  Use OpenWindows 
File Manager to access diskette or CD media.


Diskettes and CD Media In the Macintosh Application Environment (MAE)
*********************************************************************
Keywords: MAE, Macintosh, diskettes

Refer to _Solaris Common Desktop Environment Installation and System
Administration Guide_ located in /cdrom/<volume_id>/README.


The Two-Button Mouse Device
***************************
Keywords: mouse, two-button 

CDE supports both two- and three-button mouse devices.  The functions
bound to each mouse button change, depending on the mouse being used.

Three-button mouse bindings are:

	Mouse button 1	Select and Transfer
	Mouse button 2	Transfer or Adjust
	Mouse button 3	Menu

Two-button mouse bindings are:

	Mouse button 1	Select and Transfer
	Mouse button 2	Menu (can also be Transfer)

Some of the special Transfer functionality, such as Primary-Copy and
Quick-Copy, is not available in a two-button mouse.  You can
substitute Copy and Paste with keyboard accelerators and pop-up
menus.

Applications
------------
CDE applications that have pop-up menus use mouse button 2 on a
two-button mouse to display the menu attached to an object, for 
example, an icon in the File Manager window.

Many existing Motif applications that do not have pop-up menus or
have pop-up menus that are duplicated in menu bars can continue to
use mouse button 2 as Transfer.

OpenWindows applications use the same mouse button bindings as
described previously.  On a two-button mouse, mouse button 2 displays
a pop-up menu where a pop-up is available.

The Style Manager Mouse dialog box changes depending on whether a
two- or three-button mouse is being used.  On a three-button mouse,
mouse button 2 can be set to either Transfer or Adjust.  On a
two-button mouse, mouse button 2 is always Menu.

Help Volumes
------------
Most of the help volumes were written assuming a three-button mouse, and
reference the mouse buttons as mouse button 1, mouse button 2, and mouse
button 3.  When using a two-button mouse:

o Use mouse button 1 as described.
o Assume mouse button 2 does not exist.
o Use mouse button 2 as if it were mouse button 3 on a three-button mouse.


LANG Environment Variable
*************************
Keywords: locale, LANG, variable

Solaris CDE now adopts the system default locale from the LANG variable
that is set in the file, /etc/default/init.

Other CDE settings can override this variable, however.  For
information on the localized session configuration files, see the
section, "LANG Environment variable and Session Configuration," in
Chapter 16 of _Common Desktop Environment Advanced User's and System
Administrator's Guide_.


Startup of Solaris CDE Applications from the Terminal Window
************************************************************
Keywords: application names, file names

You typically access Solaris CDE applications from the Front Panel or the 
Workspace menu.  You can also start any CDE or OpenWindows applications
from the Terminal window by typing the file name.  The OpenWindows file
names are the same for these applications.  The CDE applications are:

		File Manager	    dtfile&
		Calendar 	    dtcm&
		Text Editor	    dtpad&
		Mailer		    dtmail&
		Printer		    dtprintinfo&
		Style Manager	    dtstyle&
		App Builder	    dtbuilder&
		App Manager	    dtaction Dtappmgr&
		Terminal	    dtterm&
		Image Viewer	    sdtimage&
		Create Action	    Dtcreate
		Console		    dtterm -C&
		Calculator	    dtcalc&
		AnswerBook	    answerbook&
		Icon Editor	    dticon&
 

Certain Application Icons Appear as Generic Icons
*************************************************
Keywords: MIME, FrameMaker, Icons

If Mailer has an attachment (for example, MIME type), or a file is
being viewed in File Manager, but the system cannot locate the file
or format type, the default generic document icon is assigned to it.

For example, since the FrameMaker icon is not in the default
configuration, this icon shows up as a generic icon.  If you
double-click the icon to open it, it opens in Text Editor.

To send such a file type by email, send the name and type of the
attachment in the body of the email message.  The recipient then
knows what the attachment is, can save it to the file system, and can
view it with the appropriate application.

If you are familiar with data types and would like to create some to
work with certain applications, see the following section.


Data-Type Definitions to Achieve Interoperability with OpenWindows Applications
*******************************************************************************
Keywords: data type, interoperability, OpenWindows, FrameMaker, Lotus

CDE does not include any vendor-specific data-type definitions.
Therefore, you do not see the same data-type definitions that are in
OpenWindows.  Some common data types that may affect you are
FrameMaker and Lotus.

For example, you cannot double-click to open a FrameMaker file in
CDE, which does not recognize the FrameMaker data type.  You can add
your own definition for the FrameMaker data type, however.

CDE requires an action that associates icons and data types with an
executable.  Use Create Action in the Desktop_Apps folder in
Application Manager to define the action and data type for the
utility application and its associated documents.  For complete
information, see _Advanced User's and System Administrator's Guide_.
You can also specify the icons used and help text associated with the
files.

Follow these steps to define an action and data type for FrameMaker:

1.  In the Create Action main window, type:

    Frame

    in the Action Name (Icon Label) text field.

2.  Specify the action icon to be used by clicking on Find Set or Edit
    Icon to either choose an icon file or use Icon Editor to edit the
    generic action icon provided, respectively. 

3.  In the text field for Command When Action Is Opened (Double-clicked),
    type in the command to invoke the action.  For FrameMaker, the command is:

    % /<path>/maker -f $1

    FrameMaker uses the -f option to define a file to open; Create Action
    uses the $1 option for the file name.

4.  Pull down the Window Type menu and choose Terminal (Manual) because 
    FrameMaker is usually started with a script.

5.  Click on the Advanced button to expand the Create Action main window.

6.  Click on the Add button to open the Add Datatype dialog box, then
    on the Edit button that is located to the right of the
    Identifying Characteristics text area in that dialog box.

    A separate Identifying Characteristics dialog box then pops up.
 
7.  Click the check box under Contents.  In the Pattern text field,
    input the characteristics.  For FrameMaker, type:

    <Maker

    Be sure to include the angle bracket.

8.  Given that FrameMaker documents start with a string at byte offset 0:

    o  Under Type, leave String checked as the default
    o  In the Start Byte text field, type in: 0
    
9.  Under Datatype Icons in the Add Datatype box, if you want to use
    a different icon than the default (document-shaped) icon as shown,
    click on either Find Set or Edit Icon to specify the icon.

10. Click OK in both the Identifying Characteristics and Add Datatype 
    dialog boxes to apply the changes and quit.

11. In the Create Action main window, save your settings, then exit.

These steps create:

o  A FrameMaker action in your home directory

o  A *.dt file in your .dt/types directory with the name you selected
   for the FrameMaker action

All your FrameMaker documents now have the identifying icon.
FrameMaker opens the document when you double-click that icon or
drag it to the Frame action.

You can also modify the *.dt file manually to enhance the action.

Here is a sample file:

######################################################################
#
#    Common Desktop Environment (CDE)
#
#    Action and Data-Type Definition File
#
#      Generated by the Create Action tool
#
#      $Revision: 1.0
#
#      $KEY: 1941  
#
######################################################################
#
#    WARNING:
#
#    This file was generated by the CDE Create Action tool.
#    If this file is modified by some other tool, such as vi,
#    the Create Action tool will no longer be able to load and
#    update this file.  For this reason, changes to this file
#    should be handled through Create Action whenever possible.
#
######################################################################

ACTION Frame
{
     LABEL         Frame
     TYPE          COMMAND
     EXEC_STRING   /<path>/maker -f %Arg_1%
     ICON          <icon you selected>
     WINDOW_TYPE   TERMINAL
}

DATA_ATTRIBUTES Frame_FILE_1
{
     ACTIONS       Open
     ICON          <icon you selected>
}

DATA_CRITERIA Frame_FILE_1A
{
     DATA_ATTRIBUTES_NAME Frame_FILE_1
     MODE          !d
     CONTENT       0 string <Maker 
}

ACTION Open
{
     ARG_TYPE      Frame_FILE_1
     TYPE          MAP
     MAP_ACTION    Frame
     LABEL         Open
}


Drag-and-Drop of Objects onto a Minimized Icon
**********************************************
Keywords: drag, drop, Calendar, appointment, icon, minimized,
          control, Front Panel

Due to a limitation in the CDE 1.0.1 drag-and-drop protocol, you cannot
drop objects, such as calendar appointments, onto a minimized icon in 
CDE, such as the Calendar Manager icon.

Workaround: Drop files, messages, or appointments on an open
application or on a control in the Front Panel.


Deletion of Calendar Appointments in Trash Can 
**********************************************
Keywords: Calendar, appointment, Trash Can, buffer, file, delete
 
If you drag an appointment from Calendar Manager to the Trash Can on 
the Front Panel, Trash Can appears to accept the appointment, but does 
not delete it.  Trash Can deletes only files; appointments are buffers.

Workaround: Delete a Calendar appointment by selecting it in Calendar
and clicking the Delete button.


Dropping of Text Appointments on Calendar 
*****************************************
Keywords: Calendar, text appointment, drop

Dropping text versions of appointments on Calendar is possible, but
not recommended, because even very minor variations from the standard
appointment template format prevent the appointment from being
accepted by Calendar.  For instance, if an extra space is inserted in
the "** Calendar Appointment **" line, Calendar does not accept the
appointment.

The preferred method of dropping appointments on Calendar is to drop
appointment *objects* instead of textual representations of
appointments.  You can drag appointment objects from either the
standalone appointment editor (dtcm_editor), or from the appointment
editor that is part of Calendar (dtcm).


=========================
CDE Developer Information 
=========================

CDE Naming Conventions
**********************
Keywords: naming conventions, dt, sdt

Solaris CDE 1.0.1 uses the prefixes DT and SDT in uppercase and lowercase 
combinations, in names for desktop clients, desktop libraries, and so on.
Do not use these prefixes in your application code.


Motif Applications and Color
****************************
Keywords: Motif, color, OpenWindows

The CDE environment changes the color threshold values for Motif;
hence, Motif applications may have different colors under Solaris CDE
from those in the OpenWindows environment.


CDE Applications Development
****************************
Keywords: applications, development

Solaris CDE shared libraries are built with the latest Solaris loader
technology to optimize their interfaces and performance.  This
technology conflicts with debuggers that were released prior to
SPARCworks version 3.0.1.  Therefore, we recommend that you use
SPARCworks version 3.0.1 or later when developing and debugging
applications in CDE.

Installing Solaris CDE on Solaris 2.4 overwrites any earlier version 
of the Motif library present in /usr/dt.  The new Motif library is 
among the libraries built using the new Solaris loader technology.  
For this reason, an application linked with this new version of Motif 
should be debugged with the SPARCworks 3.0.1 (or later) debugger, even 
if the application does not use any CDE-specific features or link with
any other CDE libraries.  A patched version of the 2.0.1 debugger is
provided if you are still using SPARCworks 2.0.1.  For information on
how to install the debugger (dbx) patch, see /cdrom/<volume_id>/README/PatchList.


Developing an Application Using XPG4 APIs
*****************************************
Keywords: XPG4, APIs

X/Open Portability Guide, issue 3(XPG3), is the default support for
Solaris 2.4.  To build a CDE application using the XPG4 APIs, you
must define the following C preprocessor tokens when you compile your
application:

_XOPEN_VERSION=4
_XOPEN_SOURCE
_EXTENSIONS_

Typically, you can do so in a Makefile by specifying a value for the
CPPFLAGS macro.  For example:

CPPFLAGS=-D_XOPEN_VERSION=4 -D_XOPEN_SOURCE -D__EXTENSIONS__

CDE requires no additional C preprocessor tokens to enable XPG4
behavior in your application.  If you do follow a standard, such as
POSIX, you may need to compile with additional standard-specific
flags.  Read about the standard to find out if it includes special
compiler considerations.

You must link your application with:

/usr/ccs/lib/values-xpg4.o

and install Solaris 2.4 patch #101925-02.  For information on how 
to install the patch, see /cdrom/<volume_id>/README/PatchList.


Frequently Asked Questions about Application Builder
****************************************************
Keywords: Application Builder, BIL, C++, CDE Motif

Is there some way to use my Devguide application with App Builder?
-----------------------------------------------------------------
Yes.  App Builder comes with a converter that can transform Devguide
GIL files into App Builder's equivalent Builder Interface Language
(BIL).  The resulting BIL files can then be edited by App Builder,
and new code generated.  However, you probably have some OPEN LOOK
code in the stub files of your Devguide application that must be
manually transformed to work with CDE Motif.

Does App Builder generate C++ code?
----------------------------------
Not in the 1.0.1 release.  CDE 1.0.1 provides only C language bindings
for all its widgets and desktop integration libraries, but not full
C++ support.  Nonetheless, the App Builder code generator produces C
code that can be incorporated into a C++ application, and we have
worked with projects that make use of this functionality.

Does code built with App Builder run in a Motif-only environment?
----------------------------------------------------------------
App Builder is designed on the assumption that code produced by it is
used in a full CDE environment, not where only Motif is available.
However, depending on the application, you may be able to work
selectively with App Builder and generate code that can be modified
to run on top of Motif.  We have not had a chance to investigate
this method yet, but would appreciate hearing from anyone who has
tried it, or is interested in doing so.


Application Builder: Drag and Drop Editor Changes
*************************************************
Keywords: Application Builder, Drag and Drop Editor, Data Type, 
          User Defined, Buffer

In CDE 1.0.1, the Appl Builder Drag and Drop Editor has been
modified to make it more consistent with the CDE Drag and Drop API.
We have documented the new interface in the App Builder help volume.

Note, however, that _Common Desktop Environment Application Builder
User's Guide_ still describes the previous version of the Drag and
Drop Editor.

The changes in the Drag and Drop Editor are as follows:

o The drag "Data Type" control has been changed from a check
  box (n of many) to a set of radio buttons (one of many).
        
o The "User Defined" data type for both Drag and Drop sections
  has been changed to "Buffer" to be consistent with the
  terminology used in the CDE Drag and Drop API documentation.
  
o The drop "Data Types" item, "Any Other Type," has been
  removed because it does not map to any valid type.

Additionally, the help volume documentation has been revised as follows: 

o The "Cursor Filename" and "Cursor Mask Filename" descriptions include 
  a note that explains that you need not make an entry in these
  fields, and that default icons are used in the absence of an entry.

o The description of the "Drop on Children" check box has been modified.


Application Builder: Changed Default Names for Projects and Modules 
*******************************************************************
Keywords: Application Builder, project, module, bip, bil

The default name for a new project is now "project.bip," previously
"Untitled.bip" and documented as such.  The original name violated
the rule that, to prevent a conflict between the names of the
automatically generated resource files and the name of the
automatically generated executable file, project file names should
not start with a capital letter.  For consistency, the default name
for a new module is now "module.bil."


Application Builder: Implied Apply in Property Editor 
*****************************************************
Keywords: Application Builder, Property Editor, implied apply

By default, if you make an edit in a Property Editor and select a
different object or object type without clicking the Apply button, a
dialog box is displayed with the question: should the pending changes
be applied, or should the change-object operation be cancelled?

If you always want pending changes to be applied when you select a
different object or object type, there are two methods to turn on
"implied apply:"

Method 1:
--------
Start App Builder as follows: 

% dtbuilder -xrm '*impliedApply: True'&

Method 2:
--------
Set the application resource "impliedApply" to True, as follows:

1.  Add the following line to the resource file (~/.Xdefaults):

    Dtbuilder*impliedApply: True

2.  Type at the system prompt:

    % xrdb -merge ~/.Xdefaults 

    This command merges what is in the .Xdefaults file with the current 
    X settings.

3.  Start App Builder.

You can reset implied apply to False by editing the .Xdefaults file
and executing "xrdb -merge" again.


Compiling ToolTalk Demos
************************
Keywords: ToolTalk, demo programs, OPENWINHOME, MOTIFHOME

To compile the demos in /usr/dt/share/examples/tt/demo, set the
environment variable OPENWINHOME to /usr/openwin, and the environment
variable MOTIFHOME to /usr/dt.


dspmsg Utility for Shell Scripts and Internationalization
*********************************************************
Keywords: shell script, internationalization, man page, message catalog

The dspmsg utility is useful for internationalizing shell scripts.
The dspmsg command displays a selected message from a message
catalog.  See the dspmsg man page for details.


DtComboBox Behavior
*******************
Keywords: DtComboBox, widget

The DtComboBox custom widget calls the Selection Callback of the
Combo Box widget, instead of the List widget, when the
browseSelectCallback or the defaultActionCallback is triggered for
the List widget of a Combo Box.

This action may cause failure for applications that rely on the List
widget Selection callback to be called when the List widget's
browseSelectCallback or defaultActionCallback is triggered.


___________________________

Summary of Major Bugs Fixed 
___________________________

Bug ID  Synopsis
=============================================================================
Actions
-------
1206351 Cannot launch File Manager from Application Manager.
1217603 The "dtaction -user <user_name> <action_name>" command should work 
          for all users.
1216240 Many actions do not support files that contain spaces in their names.

Application Builder
-------------------
1215625  The generated code for DroppedOn and DraggedFrom connections does
           not contain adequate comments about where to make modifications.
1215640  The Drag and Drop Editor allows multiple drag data types to be 
           selected; includes misleading drag-and-drop data types.  
1215653  Applications that use the Drag and Drop Editor to configure their 
           drag sites do not support drags with Button2.
1214793  The label strings assigned to objects dragged off the palette are
           defaulted to English -- a bug that is noticeable in the ja locale.
           When you drag a button off the palette, the localization string 
           changes to "Button" when you drop the object.
1213734  sdtgilcvt converts drop targets to labels set to nothing.  The
           Interface label displays the object name, which can be long 
           enough to overlap other objects.
1210296  sdtgilcvt does not convert Devguide messages objects properly:
           They should be converted to labels in App Builder, but are  
           translated into editable text fields.
1213740  sdtgilcvt does not convert items correctly: List items are lost;
           selected choice items are not selected. 
1213735  sdtgilcvt converts menu buttons into push buttons.
1213738  sdtgilcvt duplicates connections; generated code duplicates the
           functions, which result in uncompilable code.
1213741  sdtgilcvt loses scrollbars on text panes.
1213732  sdtgilcvt makes a large as-is group in the generated BIL file;
           the group covers other objects in the interface.
1209130  sdtgilcvt converts layered pane objects into a single radio box.

Calendar
--------
1213660 Cannot localize the date format in the Month/Year view. 
1213649 Cannot set appointments in the ja locale if the frequency is "Forever."
1213659 The Reminder field in the Appointment Editor is garbled in the 
          ja locale.
1207944 Cannot add an appointment in zh and ko locales.  
1216452 Cannot add an appointment when the start time is "No Time" in 
          zh and ko locales. 
1214899 The message format in the Reminder window is incorrect in the ja locale.
1213705 Selecting an appointment before expanding the Appointment Editor 
          produces an incorrect frequency value in the "Occurs" field in 
          the Appointment Editor.

Custom Widgets
--------------
1209578 The DtEditorGetContents() function is too slow in a multibyte 
          char locale. 
1206856 Mailer inserts the "End Forwarded Message" tag to the middle 
          of a mail message in error in the ja locale.

Data Typing
-----------
1212275 The action for AccessX is incorrect for the ja locale.
1205872 Actions are typed incorrectly in nonASCII locales.

File Manager
------------
1206252 File Manager does not save the information for the current session.

Help Viewer
-----------
1205012 In the ja locale, the text in a bulleted list is not printed when 
        you print the current topic. 

I18N
----
1204162 SunOS.lcx needs other locale entries.

Icon Editor
-----------
1210443 Starting Icon Editor with the "dticon -f" command causes that
          tool to crash when you choose Save As from the File menu. 

Install
-------
1218755 /usr/dt must be a relative link when you install in an alternative 
          location.
1212139 Need mechanism to specify more than one locale during installation.
1215890 The install-cde process should allow either "End-User Distribution
          [size]" or "Developer Distribution [size]" only.
1203831 Wrong permissions exist for /usr/dt/lib/libDtHelp.so.1, 
          libUil_d.so.3, and libMrm_d.so.3.
1208324 A SUNWdtcor problem prevents Solstice to convert a standalone
           machine to a diskless client server.
1217401 The install-cde process replies in the positive to a failed
           installpatch.
1214593 The configuration information for package sizes is confusing.


Interoperability
----------------
1211177 A Mailer message that is dropped onto an OpenWindows tool
          produces an extraneous NULL character at the end.
        
Login
-----
1214981 Login Manager does not accept the Tab key in a password.
1192556 Need reorganization of locale names in the second-level submenu 
          under Languages.
1214707 The IM server is executed twice when you choose OpenWindows as 
          the desktop.
1207458 Solaris CDE should reflect the system default locale from
          /etc/default/init.
1215038 The Chooser screen may not run if the server and client clusters 
          are different.
1211910 The Chooser screen does not work with some locales.
1216302 A slow server could cause timeout in the Languages submenu, leaving 
          C locale as the only choice.

Mailer
------
1212023 Dragging and dropping multiple attachments from Mailer to another tool
          results in duplicate copies of the first attachment.
1206590 Mailer shows menu items incorrectly if the menu label is in 
          Asian characters.
1205002 Printing Mailer messages in Asian locales results in garbled text.
1206978 Pressing the F3 key repeatedly while the Compose window is open causes
          Mailer to crash.
1219076 An irrelevant error message pops up after you open Mailer from 
          File Manager and exit.
1218579 Choosing Save As Text from the Message menu for a long mail message 
          causes Mailer to crash.
1218488 If the last message in a mailbox contains attachments and is incomplete,
          Mailer crashes.
1194932 ToolTalk should be the default Open action when you open mailboxes.
1215472 Mailer turns off auto-saving if you close all the Compose windows.
1219507 Mailer has large memory leaks.
1214672 Mailer issues incorrect error messages if it cannot find or open the
          .mailrc file.
1194811 When a new mail message arrives, Mailer does not scroll down the 
          header list and display the new message header.
1199047 You cannot provide defaults for predefined headers in the 
          Compose window. 
1216671 Mailer does not display an error message if the .mailrc file 
          is corrupted.
1206837 Mailer incorrectly displays custom header fields in the Compose Window 
          menu when the default values are in multibyte or 8-bit characters.
1209390 You cannot change the default of word wrap in the Mailer view windows.

Motif
-----
1206049 The TextField widget does not correctly render the character in 
          the ja locale.  

Terminal
--------
1204685 Terminal does not display localized messages.

Text Editor
-----------
1183443 The XIM session does not close when you quit Text Editor.
1214049 The geometry resource does not work.
        
Window Manager
-------------- 
1215437 Improperly installed locales can cause Window Manager to crash.
1202378 Deleting a modified subpanel can cause Window Manager to crash.
1198825 Window Manager does not support the Kana locking modifier key.
