Product

This is a revision of the Developer's Toolkit for HP-UX 11i.

Audio Server

With 11i, the audio server and the audio library use DCE to communicate with each other. This change is transparent to audio clients due to the use of shared libraries. Audio clients built on 10.* systems using the audio shared library will work on 11i systems, though they will now be using DCE instead of NCS. The 11i audio server will be able to communicate with DCE and NCS audio clients on other systems. However, DCE clients on 11i will not be able to connect to NCS audio servers on 10.* systems.

xterm Superseded by dtterm

This release of HP-UX includes both the X11 Release 5 and Release 6 versions of xterm, delivered in the following directories as unsupported software:

R5: /usr/bin/X11/xterm
R6: /usr/contrib/bin/X11/xterm

The functionality of xterm is superceded by the industry-standard dtterm terminal emulator, making xterm redundant. The Release 5 version of xterm will not be shipped with the next release of HP-UX; it is being provided with this release to facilitate the transition of users from xterm to dtterm.

VueHelp Libraries Removed

The HP VUE Help Developer's Kit was removed from the HP-UX 10.30 Developer's Toolkit. The VueHelp library (libXvh) is supported only for use with the X11 Release 5 development environment.

Application developers using VueHelp will need to port their applications to utilize the industry-standard CDE Help API, libDtHelp, which is supported for use with both Release 5 and Release 6 of the X11 development environment.

Digital Video DevKit Removed

The HP Digital Video DevKit product has been removed from the HP-UX Developer's Toolkit (11.0 onwards).

Technical Print Service Components

The components delivered as part of the Technical Print Service are distributed in the filesets for X, Motif, and CDE.

Obsolete Functions

XHP functions for internationalized keyboard input have been removed. These HP proprietary functions are no longer needed since X11R5 and R6 provide public, standard APIs that provide equivalent functionality. Specifically, the following functions have been removed:

XHPConvertLookup()
XHPGetEurasianCvt()
XHPInputChinese_s()
XHPInputChinese_t()
XHPInputJapanese()
XHPInputKorean()
XHPInputRoman8()
XHPInputISO7sub()
XHPNlioctl()

Instead, applications should use the following X11R6 routines:

XOpenIM()
XCloseIM()
XGetIMValues()
XCreateIC()
XDestroyIC()
XSetICFocus()
XUnsetICFocus()
XmbResetIC()
XIMOfIC()
XSetICValues()
XGetICValues()

The new X11R6 functionality gives applications greater control and more flexibility than the HP proprietary functions.

Changes in Keyboard Functionality

XHPSetKeyboardMapping() and two related functions, XHPRefreshKeyboardMapping() and XHPSetKbdMapInit(), are obsolete. These functions were used to change an application's local copy of the keymap in order to emulate a particular national language keyboard. These functions only worked for HP HIL keyboards. Although the functionality has been removed, stub APIs are provided so that older applications may still compile.

In HP-UX 9.*, many applications (such as vuepad and hpterm) use XHPSetKeyboardMapping() to set the keyboard language by passing the value of the KBD_LANG environment variable. As of 10.0, HP VUE no longer sets the KBD_LANG environment variable. Clients and libraries have removed the call to XHPSetKeyboardMapping() since its behavior is not reliable in a mixed DIN and HIL keyboard environment.

Rendering International Characters

In X11R3 and X11R4, support for rendering Asian characters was done through a proprietary mechanism called the associate font mechanism. In HP-UX 9.*, rendering of Asian character data requires that two fonts be opened to correctly render all Asian characters. When an Asian font was opened with XLoadFont() or XLoadQueryFont(), the font was checked for the existence of an associate font property. If this property existed, an additional font was opened and maintained transparent to the application. All calls to calculate metrics or to perform rendering with the font caused the implementation to also use the associate font when present.

With support for 3-byte EUC and 4-byte EUC with HP-UX 10.0, rendering Asian character data often requires that more than two fonts be opened and used when rendering Asian character data. The old associate font mechanism could not be reliably expanded to handle these cases. In addition, X11R5 and Motif 1.2 provide alternate, standard mechanisms for rendering internationalized text data. The associated font mechanism won't be supported on future releases of X11R5 and not at all in X11R6.

Applications directly calling the X library to render international text should replace their calculation of font metrics and their calls to XDraw*, XLoadFont(), and XLoadQueryFont() with the following:

XCreateFontSet()
XExtentsOfFontSet()
XmbDrawString(), XwcDrawString()
XmbDrawImageString(), XwcDrawImageString()
XmbDrawText(), XwcDrawText()
XmbTextEscapement(), XwcTextEscapement()
XmbTextExtents(), XwcTextExtents()
XmbTextPerCharExtents(),XwcTextPerCharExtents()

Applications and users that set Motif fontList resources to obtain internationalized text data should modify those font resources to specify font sets. As of Motif 1.2, a fontList resource can contain any combination of font structs and font sets. A font set is specified in a fontList resource by adding a ":" to the end of the fontList entry. For a font set, a fontList entry can be one or more ";" separated base names. A base name is either a font name (such as jpn.8x18) or an X Logical Font Description (XLFD). A typical fontList setting for Japanese might be:

app_name*Text.fontList: *-mincho-*-18-*:

The ":" character at the end of the fontList resource specification is mandatory to use font set technology.

For Motif to use font sets correctly in an application, either setlocale() or XtSetLanguageProc() must be called prior to initializing the toolkit.