HP OpenVMS Systems Documentation

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 2-3 shows the logical names and associated encoding values.

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

2.5.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 2.5.2.1.1 and Section 2.5.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 2-4 shows the languages and their associated basic fonts.

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.

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

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

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

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.

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

V1.2

The WRITE$FONTS logical name references an initialization file used to provide font definitions to the CDA Viewer.

The default location for the WRITE$FONTS.INI file is SYS$LIBRARY, but, if the logical name WRITE$FONTS is defined, the CDA Viewer uses the logical name definition to search for the WRITE$FONTS.INI file.

Full path support is included, so any of the following definitions are valid:

This section describes features that pertain to the Clock application.

2.5.3.1 DECsound Alarm Capability

V1.2

The Clock application includes an alarm feature that can be used if your system supports DECsound. On systems without sound capabilities, you can select only the keyboard bell. When you choose Alarm from the Options menu, a pop-up window appears. This pop-up window allows you to set the alarm time, choose the sound to be played, and indicate an alarm message. To see if your system supports this feature, invoke one of the sounds located in the DECW$EXAMPLES directory (for example, BELLS.AUD).

2.5.4 DECterm

V1.2--3

The latest version of the Window Manager (MWM) supports overlays and utilizes additional planes of memory, which are available on some 3D graphics accelerators. The Window Manager places borders and banners for all the windows into these extra planes of memory and thereby reduces the number of expose events for your applications that use overlays.

You may need to modify your existing applications that use overlays to avoid potential problems with the colormap. HP recommends that you set up your system to share the overlay colormap with the Window Manager, as the hardware supports only one colormap for the overlay planes.

See the associated documentation for your 3D graphic accelerator to determine if overlays are supported.

Setting Up the Overlay Colormap

To modify your applications to share the overlay colormap with the Window Manager, query the server property name SERVER_OVERLAY_COLORMAPS. When you make the query, the server returns the 32-bit value for the overlay Colormap ID.

To set up your system to share the overlay colormap with the Window Manager, edit the files SYS$COMMON:[VUE$LIBRARY.SYSTEM]VUE$MWM.COM and SYS$COMMON:[SYSMGR]DECW$MWM.COM. Change the following line in each file:

 $ mwm -multiscreen

Edit this line by adding the -Overlay command-line option as follows:

 $ mwm -multiscreen "-Overlay"

Note that if you create and install your own colormap, the following problems can result:

• Colors flash on the screen when the colormap is changed.
• Border and banner colors also change when you change the colors of your colormap.

Restrictions

The following restrictions apply when you enable the Window Manager to use overlays:

• The Window Manager supports only single-screen systems and does not function correctly with multiple graphics devices (multihead).
• If you select a Matte Size value other than "None" from the Window Manager options list, the Matte color may not be correct; that is, the color does not match the selection and is occasionally transparent.
• If you select "Show feedback when moving or resizing windows" from the Workspace Options menu, the window with the feedback information causes expose events.

• When you move windows by showing the outline of the window, the outline appears to go below the window borders and banners.
• Window borders are occasionally and randomly displayed in clear or black. If this problem occurs, select the restart option from the Workspace menu to restart the Window Manager.

V1.2--4

In previous releases, the default DECterm font size for the "big" and "little" fonts were chosen by point size. This depended on whether 75 or 100 dpi fonts were installed first in the font path. Starting with DECwindows Motif for OpenVMS Version 1.2--4, DECterm chooses its default fonts by pixel size. The following table shows the two behaviors.

In addition, on 100-dpi displays DECterm now uses the big font by default. This results in DECterm using the same font size (18 pixels) on 100-dpi displays as it did in prior releases. On displays that are less than 325 mm wide, DECterm also now uses a bigger default font.

Follow these steps to use the same font as in previous releases (14 pixels):

1. From the Options menu, select the Window... item.
2. Choose Little Font. Click on Apply.
3. If the new default font is too small, click on the Big Font button and change the pixel size in the Other text entry field from 18 to 25.

V1.2--3

You can now scroll through text using the keyboard by pressing the Ctrl key and arrow keys or by pressing the Prev or Next key on the editing keypad.

2.5.4.4 ReGIS Input Cursors and Escape Sequences

V1.2--3

The DECterm application supports all ReGIS input cursors:

• Crosshair
• Diamond
• Rubber-band line
• Rubber-band rectangle

For a shape other than the diamond cursor when n is equal to 1, define the logical name DECW$TERM_REGIS_CURSOR as one of the numbers defined in the SYS$LIBRARY:DECW$CURSOR file.

V1.2

The following escape sequences are supported by DECterm:

• All page movement sequences (NP, PP, PPA, PPB, and PPR).
• One rectangular area operation sequence (DECCRA).
• The DECLFKC sequence.
• The ReGIS command S(C(In)) supports the rubber-band rectangle cursor and the diamond cursor.

See Section 4.7.3.1, ReGIS Input Cursors for additional information about escape sequences in DECwindows Motif software. See HP DECwindows Motif for OpenVMS Alpha Release Notes for details and restrictions on the use of these sequences.

2.5.4.5 Support for Local Echo Mode

V1.2

DECterm supports a local echo mode. In the Options/General dialog box, select Local Echo, which causes all character sequences generated locally to be echoed on the display and passed to the remote host. This feature is useful when connected to a host that does not echo typed characters.

2.5.4.6 Answerback Message Support

V1.2

A user interface is available to enter answerback messages. This answerback message field is for compatibility with HP terminals.

The answerback field is a buffer that contains up to thirty characters. The answerback field in earlier HP terminals contained a message used to identify itself to the host system. For DECterm windows, the answerback field can be used to store a sequence of characters that you can use for any repetitive purpose.

A field is provided in the Options/General dialog box to enter answerback text. Click on the answerback field and enter your text. To enter control characters, encode the control character as a two-digit hex ASCII code, preceded by a number sign (#).

For example, when you enter #0D in the answerback field, DECterm responds with a carriage return.

If two consecutive number sign characters are entered (##), a single number sign is transmitted.

If anything other than a valid two-digit hex code or another number sign is detected after an initial number sign, the number sign is treated as a normal text character. Refer to any ASCII table for a complete list of characters.

The answerback text can also be concealed. When the Conceal Answerback button is enabled, the answerback message is concealed. To deselect the Conceal Answerback button, click on the answerback text field, which erases the previous answerback message.