Omni Systems, Inc. Mif2Go User's Guide, Version 55

<< Prev | Next >>

> 13 Converting to HTML/XHTML > 13.4 Supplying values for the <head> element > 13.4.3 Specifying character encoding for HTML > 13.4.3.2 Selecting a Windows code page for single-byte character sets

#### 13.4.3.2 Selecting a Windows code page for single-byte character sets

According to Microsoft, a code page is “an ordered set of characters of a given script in which a numeric index (code-point value) is associated with each character”. Mif2Go supports fonts that use the following SBCS (Single Byte Character Set) Windows code pages:

1250 Slovenian and other Eastern European and Central European scripts

1251 Cyrillic

1252 Latin I (standard FrameMaker code page)

1253 Greek

1254 Turkish

To specify a Windows code page for your document:

[HTMLOptions]

; Ansi = Windows code page to use for FrameMaker font, default 1252

Ansi=1252

Use the Ansi option to specify character encoding other than the standard FrameMaker encoding, which uses Windows code page 1252.

Set the code page in a marker

If you need a different encoding for only parts of your document, you can set the code page in a marker of type Ansi, or in a marker that is mapped in [MarkerTypes] to Ansi. The marker should contain only the code-page number. See §29.2.1 Identifying dedicated custom marker types.

FrameMaker 8 uses Unicode, not code pages

If you are using FrameMaker version 8, you are using the Unicode character set internally. Times New Roman, and most other standard Microsoft fonts, support Unicode. However, fonts that use a different character set do not. For example, the font “Caecilia LT CE 55 Roman” uses code page 1250; that is what the CE in its name means. For certain characters such as “small a macron”, which is U+0101, there is no mapping in code page 1250; so you would not get “small a macron” in this font, because it is not there.

Your best bet is to stick with Unicode fonts, and not try to use others that are CE, CYR, GRK, and so forth. The code-page system was made to provide access to characters within an 8-bit space, and it required remapping of various groups of Unicode characters to fit into that space. FrameMaker 7 and earlier versions support this remapping, but FrameMaker 8 does not. Even if you have to replace some fonts, it is best to move on.