User Guide

Editing Fonts
79
Because the Unicode character identification standard covers most
languages it is usually used as the destination information in the codepage
tables. Here is an example of fragments from two different codepages that
map the same codes to different Unicode indexes:
MS Windows 1252 Latin 1 MS Windows 1251 Cyrillic
0xC0 0x00C0
0xC1 0x00C1
0xC2 0x00C2
0xC3 0x00C3
0xC4 0x00C4
0xC5 0x00C5
0xC6 0x00C6
0xC7 0x00C7
0xC8 0x00C8
0xC9 0x00C9
0xCA 0x00CA
0xCB 0x00CB
0xCC 0x00CC
0xC0 0x0410
0xC1 0x0411
0xC2 0x0412
0xC3 0x0413
0xC4 0x0414
0xC5 0x0415
0xC6 0x0416
0xC7 0x0417
0xC8 0x0418
0xC9 0x0419
0xCA 0x041A
0xCB 0x041B
0xCC 0x041C
Many different codepages have been defined for many languages and
different operating systems. FontLab 4.6 includes descriptions for 124
codepages — all the known Windows, OS/2, MS DOS, Mac OS codepages
plus a few others like the Polytonal Greek, Russian KOI-8 and NeXT Step
codepages.
In FontLab a codepage is a filter through which you can “look” at your font
to see how it will work in different environments. For example, you might
include many Unicode characters in your font and see how it would work if
it was installed in OS/2 with the Arabic language selected. This gives you
the opportunity to easily create fonts that will be properly encoded and will
always work correctly.