V1.2--5

You can graphically select the screen on which a new application is displayed when launched from either the Front Panel, the File Manager, or the Application Manager. By default, the new application appears on the current screen (that is, the screen containing the mouse pointer). The feature allows you to drop an application icon from the File Manager or Application Manager onto one of the numbered screen controls of the Set Default Screen window. This starts the application on the selected screen without changing the current screen.

The Set Default Screen window is activated by selecting the "Set Default Screen" application in the Application Manager's Desktop Tools folder. You can start a separate instance of the Set Default Screen window on each screen. The highlighting of the default screen is synchronized across all instances of the Set Default Screen window.

4.2.4 Front Panel Icons Support MB3 Operations

V1.2--4

The New Desktop Front Panel supports mouse button 3 (MB3) operations. When the cursor is placed over a Front Panel icon and you press MB3, a subpanel or menu appears. The menu items are as follows:

• Top item--The label of the menu.
• Second item--The application that starts if you single click on the icon.
• Third item--Add or delete a subpanel, depending on whether a subpanel already exists for the control panel.

  Caution If the third item is "Delete Subpanel", this change is difficult to reverse without reinstalling the kit.

V1.2--4

When you start an application (from the Front Panel or dtfile), a new detached process is created with a process name constructed from the user name, $CDE, and a three-digit numeric identifier.

For example, user SMITH starts an application whose process name is SMITH$CDE001. The next assigned process name would be SMITH$CDE002, unless SMITH$CDE001 has already terminated and is available for reuse.

4.2.6 Viewing Reference Pages

V1.2--4

DECwindows contains a collection of help files for the New Desktop called reference pages (also known as manpages). Reference pages are divided into sections and, on OpenVMS, the file extension indicates the section. Sections distributed with the release include the following:

Section	Purpose	Extension
1	Applications	filename.1
3	Libraries/programming	filename.3
4	Programming	filename.4
5	Include file formats	filename.5

A version of dthelpview has been set up with the appropriate action definition for manpage viewing. The process logical MANPATH has been defined to point to the CDE$SYSTEM_DEFAULTS:[MAN] directory that contains all of the reference page files.

You can use either of the following methods to start dthelpview and display reference pages:

Method 1

To start dthelpview from DECterm and view a reference page called dtaction.1:

1. At the DCL level or in a LOGIN.COM file, define dthelpview as a foreign command by entering the following:

   $ dthelpview :== - _"$ sys$sysdevice:[sys0.syscommon.cde$defaults.system.bin]dthelpview.exe"

2. At the DCL level, enter:

   $ dthelpview -"manPage" dtaction.1

Method 2

To start dthelpview from Application Manager and view the reference page called dtaction.1:

1. Start Application Manager.
2. Double click on the Man Page Viewer icon located in the Desktop Apps application group. A dialog box appears.
3. Enter the reference page to be viewed and click on OK.

This section describes new features related to the traditional DECwindows desktop environment.

4.3.1 Resource Added for DECwindows XUI Applications

V1.0

The resource Mwm*useDECMode has been added to allow previous versions of DECwindows XUI applications to behave correctly with the Motif Window Manager. In particular, this resource is used to control focus, window placement, multiline icons, and the window's initial state (normal or minimized).

4.4 Applications

This section describes features related to the Bookreader application.

4.4.1.1 Bookreader Printing Improved

V1.2--4

The Bookreader application allows only draft-quality printing for books or topics. However, the Bookreader print function has been improved to eliminate such problems as missing lines and words, figures being overwritten by text, and poor leading of lines.

4.4.2 CDA Viewer

This section describes features related to the Compound Document Architecture (CDA) Viewer application.

4.4.2.1 Using the CDA Viewer to View Asian-Language Text

V1.2--3

You can use the CDA Viewer in two ways to view text files that contain Asian characters:

• Specify an options file to the CDA Viewer application.
• Define logical names at the DCL command level or in a LOGIN.COM file.

Refer to the DECwindows Motif for OpenVMS Applications Guide for information about using the CDA Viewer.

4.4.2.1.1 Specifying an Options File

Specify an options file by including a one-line entry in the file in the following format:

TEXT TEXT_ENCODING text_encoding_value

• TEXT is the format.
• TEXT_ENCODING is the option you specify to CDA.
• text_encoding_value is the value of the codeset. (See Table 4-1 for a list of values.)

Table 4-1 shows the languages, codesets, and text-encoding values.

Table 4-1 Asian Language Codes for Options Files

Language	Codeset	Text Encoding Value
Japanese	DEC Kanji	DEC_KANJI
Japanese	Super DEC Kanji	SDECKANJI
Traditional Chinese	DEC Hanyu	DEC_HANYU
Simplified Chinese	DEC Hanzi	DEC_HANZI
Korean	DEC Korean	DEC_HANGUL

The following table shows examples of one-line entries.

Options File	One-Line Entry
HANYU.CDA$OPTIONS	TEXT TEXT_ENCODING DEC_HANYU
HANZI.CDA$OPTIONS	TEXT TEXT_ENCODING DEC_HANZI
HANGUL.CDA$OPTIONS	TEXT TEXT_ENCODING DEC_HANGUL

To view the EXAMPLES_CUSTOMERS.TXT file that contains Japanese text in DEC Kanji, use your editor to create an options file called KANJI.CDA$OPTIONS. Add the following one-line entry to the file:

TEXT TEXT_ENCODING DEC_KANJI

When you access the file through the Options File dialog box with the CDA Viewer, the EXAMPLES_CUSTOMERS.TXT file is viewable in the DEC Kanji codeset (Japanese language).

4.4.2.1.2 Defining Logical Names

The second option to enable viewing files in Asian languages is to specify the text file and encoding value by defining two logical names:

• DDIF$READ_TEXT_GL
• DDIF$READ_TEXT_GR

Table 4-2 shows the logical names and associated encoding values.

Table 4-2 Logical Names for Specifying Text Encoding

DDIF$READ_TEXT_GL	DDIF$READ_TEXT_GR	Encoding Value
LATIN1	MCS	MCS
LATIN1	LATIN1	ISO Latin--1
LATIN1	KATAKANA	ASCII--Kana
LATIN1	KANJI	DEC Kanji
ROMAN	MCS	Roman--MCS
ROMAN	LATIN1	Roman
ROMAN	KANJI	Roman--Kanji
ROMAN	KATAKANA	Roman--Kana
LATIN1	HANZI	DEC Hanzi
LATIN1	HANGUL	DEC Hangul
LATIN1	HANYU	DEC Hanyu

You can define the logical names on the DCL command line or in your LOGIN.COM file. For example:

$ DEFINE DDIF$READ_TEXT_GL LATIN1 $ DEFINE DDIF$READ_TEXT_GR KANJI

Note that this example defines the text encoding for DEC Kanji (see Table 4-2).

4.4.2.2 Converting Files That Contain Asian-Language Characters

V1.2--3

You can convert an Asian-language text file to another format by specifying an options file or by defining the logical names DDIF$READ_TEXT_GL and DDIF$READ_TEXT_GR as discussed in Section 4.4.2.1.1 and Section 4.4.2.1.2.

The format for converting a document from TEXT to another format is as follows:

$ CONVERT/DOCUMENT/OPTION=language.CDA$OPTIONS filename.TXT/FORMAT=TEXT - _$ filename.output_extension/FORMAT=output_format

For example, to convert a traditional Chinese language text file to a DDIF file, enter the following command line:

$ CONVERT/DOCUMENT/OPTION=HANYU.CDA$OPTIONS - _$ GUIDELINES_PERSONNEL.TXT/FORMAT=TEXT GUIDELINES_PERSONNEL.DDIF

Note that this command line does not include the /FORMAT=DDIF qualifier; DDIF is the default.

The output file, GUIDELINES_PERSONNEL.DDIF, contains language data.

You can also create Asian language PostScript files from a DDIF, DTIF, or text (ASCII) file. For example, to convert a DDIF file to PostScript (.PS) format, enter the following command:

$ CONVERT/DOCUMENT filename.DDIF filename.PS/FORMAT=PS

When you print an Asian language PostScript file on a PostScript printer, ensure that the required language fonts are available on the printer. Otherwise, the PostScript file defaults to a basic set of fonts. If these fonts do not exist, the PostScript file defaults to Courier fonts. Table 4-3 shows the languages and their associated basic fonts.

Table 4-3 Languages and Associated Basic Fonts

Language	Basic Fonts
Japanese	Ryumin-Light-EUC-H or Ryumin-Light-Hankaku
Hanyu	Sung-Light-CNS11643, Sung-Light-DTSCS
Hangul	Munjo
Hanzi	XiSong-GB2312-80

V1.2

As well as supporting a static-table for the fonts supported by the DECfonts Typeface Collection Version 1.2, the CDA Run-Time Services includes support for dynamic font lookup. This enables the CDA Viewer to use new fonts as they are installed on the system.

Dynamic font support is implemented using the WRITE$FONTS.INI file, which you can maintain using the Font utility provided with either DECwrite or DECpresent. If a document contains a font not found in the static tables, the CDA Viewer tries to open the WRITE$FONTS.INI file and search for the font. If the font is not found or if the system does not contain a WRITE$FONTS.INI file, the viewer uses a fallback font.

4.4.2.4 Enhanced Display Performance

V1.2

The current version of CDA Run-Time Services includes a performance enhancement that decreases the time it takes to display the first page of a CDA document. Other applications that use the CDA Viewer to view documents (for example, DECwindows Mail) also benefit from this enhancement.

The CDA Viewer enables this performance enhancement feature by default. You can disable the feature as follows:

$ DEFINE CDA_QUICK_FIRST_PAGE FALSE

The CDA Viewer might not display some documents correctly when this feature is enabled. If you encounter such a problem, disable the feature and invoke the CDA Viewer again.

4.4.2.5 Pack and Unpack Applications

V1.2

CDA Run-Time Services includes two standalone applications that can be used for transferring CDA documents across a network. The CDA Pack application packages a CDA document along with all of its externally referenced files into a single file that can be copied between systems or mailed to other users. The CDA Unpack application reads a file that is packaged by the CDA Pack application and creates a copy of the original document file and all its externally referenced files.

These applications allow you to copy CDA documents between systems without copying externally referenced files separately or correcting external file reference information after copying documents.

To use these applications, add the following lines to your LOGIN.COM file (or add the lines to the SYS$MANAGER:SYLOGIN.COM file):

$ PACK == "$SYS$SYSTEM:CDA$PACK.EXE" $ UNPACK == "$SYS$SYSTEM:CDA$UNPACK.EXE"

These lines enable you to use the symbols PACK and UNPACK to invoke the Pack and Unpack applications, respectively.

4.4.2.5.1 Pack Application Syntax

The CDA Pack application creates a single output file that contains the contents of a .DDIF or .DTIF input file. The single output file also includes the files that are referenced by the .DDIF or .DTIF input file.

The format of the PACK command is as follows:

$ PACK input-file-spec output-file-spec

The following sections explain the format of the PACK command.

input-file-spec

Specifies the name of the primary .DDIF or .DTIF input file.

output-file-spec

Specifies the name of the output file that is created by the PACK application. If you do not specify a device or directory, the output file is created in the current default directory.

Qualifiers:

/[NO]SKIP_MISSING

Controls whether the Pack application continues processing if it cannot find one or more of the files that are listed as external references in the input file. The names of any missing files are sent to SYS$ERROR when the Pack application is completed. If you specify /NOSKIP_MISSING, the Pack application does not create an output file if any of the externally referenced files are missing. The default is /SKIP_MISSING.

/[NO]CONTROLLED_COPY

Controls whether the output file includes only those external references that specify COPY_REFERENCE as the value of the ERF_CONTROL item in the input file. If you specify /NOCONTROLLED_COPY, the Pack application includes all referenced files, regardless of the value of the ERF_CONTROL item. The default is /NOCONTROLLED_COPY.

/ALWAYS_ENCODE

Controls whether an output file is created when there are no external references in the input file, or if none of the externally referenced files are found. The default is not to create an output file in these cases. If an output file is not created for these reasons, the Pack application returns the CDA_W_NOOUTFIL status code.

For example:

$ PACK MYFILE.DDIF TEST.PACK

4.4.2.5.2 Unpack Application Syntax

The CDA Unpack application unpacks an input file created by the Pack application. The output files are the .DDIF or .DTIF file that is packed by the Pack application, as well as a file for each external reference in the .DDIF or .DTIF file. The Unpack application sends a list of created files to SYS$ERROR.

The format of the UNPACK command is as follows:

$ UNPACK input-file-spec

The following sections explain the format of the UNPACK command.

input-file-spec

Specifies the name of the input file that is created by the Pack application.

Qualifier:

/OUTPUT=output-file-spec

Specifies the file name and location of the files created by the Unpack application.

If you specify an output file name without a directory name, the Unpack application creates the main .DDIF or .DTIF file with the file name you specify in the current default directory. It also creates all externally referenced files in the current default directory.

If you specify a directory name without a file name, the Unpack application creates the main .DDIF or .DTIF file and all externally referenced files in the specified directory. The main .DDIF or .DTIF file has the same name as the file packed by the Pack application.

If you specify a directory name and a file name, the Unpack application creates the main .DDIF or .DTIF file and all the externally referenced files, in the specified directory. The main .DDIF or .DTIF file has the file name you specify.

For example:

$ UNPACK TEST.PACK Output file DISK$:[SMITH]MYFILE.DDIF created. Output file DISK$:[SMITH]FIGURE_1.DDIF created. $ UNPACK TEST.PACK/OUTPUT=[SMITH.UNPACK] Output file DISK$:[SMITH.UNPACK]MYFILE.DDIF created. Output file DISK$:[SMITH.UNPACK]FIGURE_1.DDIF created. $ UNPACK TEST.PACK/OUTPUT=[SMITH.UNPACK]NEW_FILE.DDIF Output file DISK$:[SMITH.UNPACK]MYFILE.DDIF renamed NEW_FILE.DDIF Output file DISK$:[SMITH.UNPACK]FIGURE_1.DDIF created.

4.4.2.5.3 Error Messages

This section describes messages associated with the CDA Pack and Unpack applications.

FILESPEC, Missing filespec: file-name

NOOUTFIL, No output file was created.

OUTFILE, Output file created: file-name

V1.2

The CDA Viewer issues the following message if it is unable to create the application context:

DRMCTXFAIL, DVR could not create application context, aborting