Association Section

The association section of the mp.conf file associates each font with the shared object that maps the intermediate code points to the presentation forms in the fonts encoding. Each line in this section is as follows.

keyword

CnvCode2Font.

font alias name

The alias name defined for the font.

mapping function

Takes in the intermediate code and returns presentation forms in fonts encoding, which is in turn used to get the glyph index, and draw the glyph.

file path having mapping function

The .so file name that contains the mapping function. You can use the utility in dumpcs to find out the intermediate codeset for EUC locales.

---

Note –

The current TrueType engine used by mp (1) can deal only with format 4 and PlatformID 3 cmap. That is, you can only configure Microsoft .ttf files. Additionally, the character map encoding has to be Unicode or Symbol for the TrueType font engine to work correctly. Because most of the .ttf fonts in the Solaris environment obey these restrictions, you can map all TrueType fonts in Solaris software within the mp.conf file.

---

When you create a shared object for mapping a font that corresponds to a PCF type1 X Logical Fonts Description (XLFD), then create the shared object that maps from the intermediate code range to the encoding specified by XLFD. For example:

-monotype-arial-bold-r-normal-bitmap-10-100-75-75-p-54-iso8859-8

The corresponding PCF font is:

/usr/openwin/lib/locale/iso_8859_8/X11/fonts/75dpi/ariabd10.pcf.Z

This font is encoded in isoISO 8859-8, so shared objects have to map between intermediate code and corresponding ISO 8859-8 code points.

If a TrueType font with XLFD:

-monotype-arial-medium-r-normal--0-0-0-0-p-0-iso8859-8

has the corresponding font:

/usr/openwin/lib/locale/iso_8859_8/X11/fonts/TrueType/arial__h.ttf

you should map between the intermediate code and Unicode, because the cmap encoding for the previous TrueType font is in Unicode. In the example of this TrueType font, suppose a sample intermediate code in the en_US.UTF-8 locale that corresponds to a Hebrew character (produced by the PLS layer) is 0xe50000e9. Because the font is Unicode encoded, design the function within the corresponding .so module in such a way that when you are passing 0xe50000e9, the output corresponds to presentation form in Unicode. The example here is 0x000005d9.

The function prototype for the mapping function should be:

unsigned int function(unsigned int inter_code_pt)

The following are optional keyword/value pairs that you can use in mp.conf:

PresentationForm        WC/PLSOutput

The default value is PLSOutput. If the user specifies WC, then the intermediate code points that are generated are wide characters. For CTL printing, this default value should be used.

If the locale is a non-CTL locale and has the keyboard value is PLSOutput, that value is ignored and the mp(1) generates wide-character codes instead.

You can use the optional keyword/value pairs listed in the following table if the locale supports CTL. These variables can assume any of the possible values given in the middle column of the table.

Table 7–1 Optional Keyword/Value Pairs

Optional Keyword	Optional Value	Default
Orientation	ORIENTATION_LTR/ ORIENTATION_RTL/ ORIENTATION_CONTEXTUAL	ORIENTATION_LTR
Numerals	NUMERALS_NOMINAL/ NUMERALS_NATIONAL/ NUMERALS_CONTEXTUAL	NUMERALS_NOMINAL
TextShaping	TEXT_SHAPED/ TEXT_NOMINAL/ TEXT_SHFORM1/ TEXT_SHFORM2/ TEXT_SHFORM3/ TEXT_SHFORM4	TEXT_SHAPED