Russian (original and up to date) version here

It is not a real english version but computer generated bastard with some minor manual corrections. Sorry. :-)

Languages, fonts and encodings. Russian and around

Edition from 05-may-1999, small corrections 09-feb-2000, 09-jan-2001 Updates of the last month.

Lingua latina non penis canina est. (Old scholar saying, to which there is comments)

• Codepages with cyrillic
  • KOI8-R and other encodings
  • Cyrillic Copepages Definitions
  • Code conversion programs and viewers
  • Religious wars
  
  
• True Type: documented and not documented
  • Specifications and sources
  • Character Sets, Fonts and FontSubstitutes
  • Tables of the TrueType font file and their role in Windows
    • Cmap table
    • Name table
    • OS/2 table
    • PANOSE table
    • Recognition of character sets in the font
  • Unicode and Postscript-fonts
  • Fonts and Unicode applications
    • Office-97
    • Internet Explorer 4
    • Internet Explorer 5 beta 2
    • Netscape Communicator 4
    • Adobe Photoshop 5 and Illustrator 7
  • Large fonts in Windows'95/NT4
    • Windows glyph list 4.0 (WGL4)
    • Euro and modification in Microsoft Codepages
    • Accessible multilingual fonts
  • Converters of the font encoding and other tools
  
  
• Multilangauge: the programs and examples
  • Around rusification
  • Multilingual programs
  • Fonts and font editors
  • Examples

Any comments, flame etc. by e-mail: shlimazl@mtu-net.ru (Konstantin Kazarnovsky) would be gratefully appreciated

KOI8-R and other codings

• 
  I with thanks and different warm feelings place the first reference to this, becoming canonical, Andrey Chernov's homepage about KOI-8 and rusification of the Internet. However devoted, as a whole, one theme, it is also some encyclopaedic, affecting or giving the references also on many adjacent themes and problems. For me it was a remarkable starting-point for understanding (at all not near to a completeness) structure of the Internet, and also principles of language support in Windows.
• Method of inclusion KOI8-R in number of languages Windows ' 95. A key place in ache's page, relating to Windows'95. An offered method, alas, hackerlike and not in all cases working. In particular, I did not meet a system of check of spelling under Windows, supporting KOI8-R. Nevertheless, it - best, that is, giving a possibility to use in large number Internet-programs multilingual fonts of the best font firms of the world:-) (Monotype, Bitstream etc.).

  In development of this method:

• The resource table of code conversion with support of control characters.
  My updating offered ache of the table (for Borland Resource Workshop), permitting to see graphics images of majority of control characters (codes less decimal 32). It, perhaps, unique under Windows a method of reading of FIDO-conferences through the Internet (almost:-) lost-free, with all by their pseudo-graphic (more or less artistic) features.
  Set-up Forte Agent, permitting to the full to use these possibilities, see on page with the programs and texts
  
  
• Electronic mail: look in the book, and see , or Notes about perversions. (in Russian)
  The HTML-version of the article about the Russian encodings in e-mail for the magazine Hard'n'Soft, NN 11'98 - 2'99.

From large variety of the codings of Russian, the majority from which in "of Russian part" is contained also by(with) the not Russian cyrillic letters, - more widespread and documentary variants are shown in the tables as pictures and documents WORD 6/'95:

• The cyrillic encodings as the graphic tables
• The cyrillic encodings
  The document Word 6.0/95. For reading the document in a system there should be standard "western" and russian fonts Times New Roman and Times New Roman Cyr (or appropriate logic sections of the font Times New Roman in Windows'95), and also standard fonts Symbol and MS LineDraw.
  
• The summary table of the most popular cyrillic encodings
  The document Word 6.0/95. In this table for each are placed their positions in various encodings, and also appropriate code and name in Unicode. If any character in the encoding is absent, whenever possible is underlined appropriate "similar" (such correspondences much less standard, than encodings).

Definitions of (cyrillic) code pages

• KOI8-R (RFC 1489) Main Russian encoding in the Internet.
• KOI8-U (RFC 2319) Ukrainian clone KOI8-R, in which in 8 items 4 Ukrainian letters are entered (Upper and Lower: UKRAINIAN IE, CYRILLIC SMALL LETTER BELORUSSIAN-UKRAINIAN I, UKRAINIAN YI, UKRAINIAN GHE WITH UPTURN).
• Codepage 1251 (MS Windows Cyrillic), ver. 2.01 (with Euro) Main cyrillic coding in all versions Microsoft Windows, becoming the most standard for WWW-pages.
• Codepage 866 (MS DOS Cyrillic) Main Russian encoding for MS DOS.
• Codepage 10007 (Mac Cyrillic)
• Mac OS Ukrainian Cyrillic     In two items differs from CP10007 (Upper and Lower GHE WITH UPTURN).
• ISO 8859-5
• Character sets and codepages Definitions of various character sets and code pages from Microsoft
• Definitions(determination) in Unicode of the codings from ISO 8859-1 up to ISO 8859-9
• UTF-7 (RFC 2152) 7-bit Unicode character set Transformation Format, 7-bit format of submission Unicode in e-mail.
• UTF-8 (RFC 2279) 8-bit Unicode character set Transformation Format, 8-bit format of submission Unicode in e-mail.
• Rosetta the Universal encoding, that is alternative to Unicode.

The programs for code conversion and viewers

• XCode converter or . The free universal program under DOS, that performs conversions between CP866, KOI8, CP1251, MAC and ISO8859-5, has also a possibility of auto recognition of the encoding and auto decoding, including for a number "perverted", i.e. "double" code conversions. Infortunately, code conversion CP866-KOI8 in it be incorrect (for what can not is called KOI8-R) outside the Russian letters. And it, in particular, does not allow the program to recognize some double code conversions, if among them there was a correct variant of code conversion CP866->KOI8 or KOI8->CP866.
• XCode converter with the fitted tables CP866- > KOI8-R and KOI8-R- > CP866. In such kind the program is suit and as standard decoder, and as a decoder in those cases, where while is powerless even
  
• Agama Mail Reader. The universal program under Windows'95, recognizing up to 4 (or even 5 with allowance for difference of initial and final code pages) stratifications of code conversions. I do not know, the truth, where it the authors such situation could find. Incorrectly will recode CP866-KOI8, accordingly will not recognize for this case multiple code conversions. The most interesting possibility - attempt of restoring (with use of the linguistic analysis, apparently, dictionary) text subjected "trimming of eighth bit in Compuserve style", when all latin letters with diacritical marks from uperr half of code table Latin-1 (CP1252) will be transformed in ASCII with loss of all diacritics. That for want of it happens to the Russian letters - it is possible to itself to present! Compuserve, like so to do has ceased, but here and there problem has remained. Unicode formats are not supported. Is requested $29 for the version 1.2 and $34 for a little more high-power version 1.5. Naturally, folk patch too is accessible. In same version 1.5 the hints on a possibility of creation of the tables of code conversion are made, but I have not found, where this possibility will be realized.
• TOT-Recode (Version 1.5). The charge-free program, which automatically selects the scheme of code conversion similarly Mail Reader (and as supports the coding Quoted-Printable), has a batch mode, but with restriction of a file size in 30 kb, without support "trimmings of eighth bit in Compuserver style" and without Unicode-support.
• Shtirlitz (version 3.0) . The universal program of code conversion and restoring of the text from Vsevolod Lukianin: works with schemes, understands win/koi/dos/iso/mac/lat, unicode; has a set of tunings, including amount of levels of code conversion (up to 10). Will decode Quoted-Printable, UUEncode, XXEncode, Base64, BinHex (Hqx7), and also similar Quoted-Printable Internet-format such as %C0%C1 and RTF-format (format \'c7). Works with the HTML-documents, which can recode in a text kind. Freeware.
• FROMDOS and TODOS - pair of the programs under DOS, distinguished only by titles, which correctly will recode from CP866 in KOI8-R and back. Naturally, freeware.
• Cifirica . Written by the Roman Koshelev intellectual transcoder (under Win32) into russian transliteration and from translit, with elements of the English-Russian interpreter and customized rules of a transliteration and translation. Freeware.
  Cifirica on-line. Same as web-service.
• CPAGE - macros for MultiEdit 7.0. . Written by Pasha Bizhan in a Xcode trend transcoder DOS - KOI8-R - WIN - ISO - MAC in the form of the macro for MultiEdit for version 7 DOS/Win (such has come), MEW8.0 and is more. On a comparison with a parent version I fit the tables of code conversion DOS - KOI8-R, and also are improved (as it seems) algorithms of code conversion in other code pages, where the one-to-one correspondence is impossible. In the last versions (jan-99) are added Unicode formats (UTF-7, UTF-8 and Unicode text; for all, at last, both encoder, and decoder). The heuristic possibilities XCode and work with double code conversions in this macros are absent. the previous version in case in last will be many errors.
• WPVIEW 4 patch Patch for WPVIEW from Norton Commander 4, substituting format XyWrite on Koi8-r with the correct table of code conversion. For want of it, the truth, in a title of the window is shown an incorrect format, but in remaining all works correctly.

  Religious wars

•  www.homepage.techno.ru/barsic/antikoi.htm "Snow Panther", "Movement Anti-KOI".
  
  
•   And it, on the contrary, is the movement for KOI-8 as the only correct encoding.
  

Specifications and sources

• TrueType 1.0 rev. 1.66 Specification. The main document in a format Word 6/'95, containing the last version of the specification TrueType from Microsoft (at least for Microsofts products).
• OpenType 1.2 Specification. Developed jointly Adobe and Microsoft OpenType Specification in HTML-format HTML (attempt of the uniform approach to PostScript and TrueType fonts). Includes the extension TrueType - TrueType Open, accessible also as the separate specification:
• TrueType Open rev. 1.0 Specification. The document in a format Word 6/'95.
  
  
• Unicode Inc. The server of the Unicode consortium, holder of the of the same name trademark and developer of the of the same name standard of the general coding (curent version 2.1.5).
• Code Chart and Names List. Compact (as far as it is possible) variant of Unicode character charts on the same server, recently completed under the new version Unicode.
• Microsoft Typography. Here is a lot of info about fonts and typography, including significant part of references on this page.

Character Sets, Fonts and FontSubstitutes

• Character Sets.
  The concept of a character set of majority (but not in all) cases is identical to much more clear concept of a Codepage. Unicode-definitions of codepages, that supported in (international-european) Windows, are contained in resources GDI.EXE (for the 16-bit programs and for work with fonts through scripts), and also (for 32-bit Unicode-programs) in files of National Language Support files (NLS), about the role NLS and their structure see notes concerning MSIE 4. The table with the review of known character sets is indicated below.
  The codes of character sets (1-st and 2 table columns) are not a part neither standard Unicode, nor specifications TrueType, they represent only program-internal labels, defined in header files of the programming languages.
  The codes for character sets Cyrillic, Central European and Baltic (CC, CE and BA accordingly) direct on an idea on an originally mnemonic character of these labels.
  The unique direct reference to codes of character sets I have found only in The specifications RTF in the description of performance of the font \fcharsetN:
  Specifies the character set of a font in the font table. Values for N are defined by Windows header files, and in the file RTFDEFS.H accompanying this document.
  In the file of the specification anything "accompanying" was not, however simbolical significances of these codes are determined, in particular, in the file WINGDI.H from a package Borland C ++ 5, see it's appropriate fragment wingdi_h.txt, including also simbolical label of a number of other performances of the font.
  In the last two table columns is indicated, whether there is in resources GDI.EXE Unicode table, defining given character set (given code page). The special case (in the different relations) represents charset Symbol, defining it the table is a continuous section of codes 0xF000-0xF0FF, by an obvious image it is not present at resources.
  Zero ("0") designates character sets, for which label and the code is present, but Unicode table is not present (it is necessary to consider, that for hieroglyphic languages the two-byte coding is always used and the concept of a code page loses a sense, if I here am not mistaken).
  

  Charsets, or character sets

  Code (hex)	Code (dec)	Name	Code Page	Font suffix	Win 3.1	Win 9x
  0x00	000	Western (Latin 1)	CP1252		+	+
  0x01	001	Unknown			0	0
  0x02	002	Symbol			+	+
  0x4D	077	Mac			- (?)	0
  0x80	128	Japanese			-	0
  0x81	129	Hangeul			-	0
  0x82	130	Hangeul (Johab)			-	0
  0x86	134	Chinese_GB2312			-	0
  0x88	136	Chinese_BIG5			-	0
  0xA1	161	Greek	CP1253	Greek	-	+
  0xA2	162	Turkish (Latin 5)	CP1254	Tur	+	+
  0xA3	163	Vietnamese	CP1258	Viet	-	-
  0xB1	177	Hebrew	CP1255	(Hebrew)	-	+
  0xB2	178	Arabic	CP1256	(Arabic)	-	+
  0xBA	186	Baltic	CP1257	Baltic	+	+
  0xCC	204	Cyrillic	CP1251	Cyr	+	+
  0xDE	222	Thai	CP874	Thai	-	-
  0xEE	238	Central (Eastern) European, (Latin 2)	CP1250	CE	+	+
  0xFF	255	OEM/DOS			0	0

   
   
• FON-Fonts.
  The fonts with such extension exist of two kinds - raster (bitmapped) and vectorial (scaled). The format of vectorial fonts is not known to me, them does not understand Borland Resource Workshop 4.5, in Windows 3.1* they are marked as fonts of a plotter and "all resolutions", and Windows'9x limits, similar, only last of these marks.
  Raster fonts with .fon extension actually (as well as writes Resource Workshop) represent library from several fonts for a number of sizes, for example, "8,10,12,14,18,24", and these numbers - some conditional significance describing a font size in items (the fixedwidth font Courier of a size 10 consists of signs by a size 8*13).
  Font header contain 2 fields of characteristics: Family (pale shadow from PANOSE characteristics in TrueType) and Char.Set.
  
  

  Values of a Family field (following Borland Resource Workshop)

  Value	Family Name	Description
  0		Not the alphabetic font
  1	Roman	The proportional font with serifs
  2	Swiss	The proportional sans-serif font
  3	Modern	The fixedwidth font
  4	Script	The italic or hand-written font
  5	Decorative	The decorative font

  
  The field Char.Set contains a code of a character set in the correspondence with the above-stated table of character sets. The fonts in Windows 3.1* contain in it a field 0, 2 or 255 (latter for fonts Terminal), irrespective of an actual code page of the font. In Windows ' 95 in it the field is underlined an actual code page, so that for compatibility with the programs under 3.1 it is required to insert appropriate lines (System,0=System,204 etc.) in WIN.INI into section FontSubstitutes.
  Generally speaking, the separate fonts of the file .FON can be marked as different character sets, but what will be Windows' behavior in this case, it is unknown.
  
  
• Installation of fonts and character sets.
  While installation of the font Windows determine it various characteristicss, in particular, character sets associated with the font (charsets). In Windows 3.* with TrueType font (and, most likely also with raster font .FON) the unique code of a character set (more often - 0, or western) is associated. In Windows'95 with TrueType font a number of character sets codes, or scripts, can be associated (more often among them is present 0, or western). The algorithm of such associations see lower. The result of font installation is named as the physical font.
  
  
• FontSubstitutes.
  Section in WIN.INI, appeared in Windows 3.1 for assuring compatibility with standard fonts in Windows 3.0 and in the complicated kind passed on into Windows'95 and (as section of the registry) in Windows NT. Each line in it looks like this
  FontLog=FontPhys Or (in Windows'95)
  FontLog, CharsetLog=FontPhys, CharsetPhys  .
  Here at the left there is a name of the logical font, and on the right - name of the physical font;
  CharsetLog and CharsetPhys - codes of character sets in the correspondence with the table of character sets.
  Despite of apparent intuitive clearness of font substitution, the details of its algorithm are rather obscure and at least documented not fully. The most in-depth article was found in MSDN section of a site Microsoft: Windows Font Mapping (Ron Gery, June 8, 1992). (Though the article is old, but the reference to it is included just now).
  From some portion of an approximation, all works as follows:
  In Windows 3.1* are not specified (and do not work) the codes of character sets, but - by all - code 0 everywhere is meant, anyway it was impossible to me in international Windows 3.1*, where the delivered fonts with the suffix Cyr have a character set code 204, to force to work lines of a type
  Arial=Arial Cyr.
  In remaining part the general scheme can be extended on Windows 3.1*.
  
  1. If in a system there is a physical font with the same characteristics, as the logical font, indicated in a line (FontLog, CharsetLog), a line of a font substitution does not work.
     If the same logical font occurs in section FontSubstitutes twice and more, second and further entry also do not work.
  2. If in a system there is no physical font with the characterisitcs, indicated in a line (FontPhys, CharsetPhys), the substitution on the font on general substitution rules of the font (fontmapping) is made, when the required font in a system is absent. The weight factors of "similarity" are used, from which greatest significance, and exceeding all remaining taken together, is attributed just to code of a character set.
  3. If the indicated logical font occurs for the first time and in a system there is an indicated physical font, then is crated logical font FontLog, CharsetLog so, that for it's request in a program, this program receives the physical font, indicated in a line. Generally not only the name of the given font will not coincide with requested, but will not coincide and charset.
  4. If for the given physical font with the given CharsetPhys for the first time appears a logic font, referring on it, (seems that only with CharsetLog=CharsetPhys), the logic font occurs also in font enumeration of 16-bit programs and such program, as character map. Such way in Windows'95 ensures compatibility on national fonts with Windows 3.1*. So standard fonts
     Arial Cyr, Courier New Cyr etc. (and also Arial Creek etc.) - as the logic fonts - is created in Windows'95 by lines of a type:
     Arial Cyr,204=Arial,204
     Arial Greek,161=Arial,161 .
     Such fonts take an intermediate position between physical and pure logical, sometimes them name emulated, I shall use more likely for them a label "fonts-sections of the multilingual font".
     
  5. Lines of the following kind do not work, though could work:
     FontLog, CharsetLog=FontPhys, 0
     If CharsetLog is not equal 0 and
     FontLog,0=FontPhys,255  .
     The latter could be applied to use of the font in DOS-encoding, that do Windows itself in DOS-window, but - alas - this possibility does not work, however, more or less in the accordance with the decribed scheme, since during installation of the font (distinct from raster Terminal) the character set with a code 255 (script OEM/DOS) never occurs in the list as allowable.
     
     
• The suffixes in a title of the font.
  The standardized suffixes, listed in table character sets, of the national versions of fonts (not being like mandatory) execute nevertheless 2 functions:
  
  • One function obvious enough - so is ensured compatibility with the programs using standard names of national fonts, first of all it concerns to fonts such as Arial Cyr, Courier New Cyr and Times New Roman Cyr.
    
  • Other function not only is not obvious, but also undocumented: Word-95 during switching of the keyboard (and by that language) is automatically switched to the font of the same title appropriate to selected language. And the correspondence it is determined just sewed rigidly up in Word-95 by the allowable suffixes of the national versions of fonts: <none>, Cyr, CE, Baltic, Greek and Tur. It is coordinated to the set of languages supported in Word-95, which paneuropean version (including Russian) don't support Hebrew and Arabic, despite of support of appropriate code pages by the module GDI.
    It is interesting, that such switching works fully for the "native" switcher, but not for all alternate programs of switching - 2 of 4 tested programs called switching the font only on the second entered character, and the first at once entered character was appeared in the incorrect font. Probably such behaviour is caused whether an error, whether an not documented function.
    
    

TrueType font tables and their role in Windows

• cmap table. This table determines encodings of the font and sets the correspondence between characters codes and their images (glyphs), is more point by indexes glyphs, which order is arbitrary.
  Generally speaking, the table cmap almost always consists of the several subtables, which determine the various encodings of the font. Each subtable is characterized by two numerical identifiers Platform ID (identifier of a platform) and Encoding ID (type of the encoding). Usually identifier of the table is noted as m.n. All really met TrueType in Windows, intended for european and middle East languages (about Chinese and that similar languages anything tell I can not), for a platform Microsoft contained equally one from the following two codings, which only and are recommended Microsoft for further use:
  

  Platform	The coding	Definition
  3		Microsoft
  	3.1	Microsoft UGL (Unicode Glyph List) - standard coding of text fonts in Windows
  	3.0	Microsoft unspecified (Symbol) encoding - standard encoding for non-text fonts in Windows.

  
  All known for me variants of identifiers are in the separate table of the codings TrueType, where the additional codings of a platform Microsoft are intended, most likely, for hieroglyphic languages (however, now there is also Unicode encoding of hieroglyphs).
  
  4 formats of the subtables cmap are described in the specification TrueType (Format 0, 2, 4 and 6), for want of it in the subtables for Windows (identifiers 3.0 and 3.1 are circumscribed, not confuse to the versions Windows:-) one should to be used only from these formats - Format 4. It is arranged rather smartly, but is logically equivalent simply to list allowable (two-byte) Unicodes and list of appropriate glyph indexes. The index 0 is intended for an image of an absent character (if those will be requested), in majority of fonts as an absent character the empty small square is used.
  The encoding 3.1 - Microsoft UGL is intended for majority (text) fonts in Windows, and the codes of characters in the cmap table, generally speaking, should correspond to the standard UNICODE. It is necessary to mark, that the specification does not limit neither number of characters in the font, nor the number of characters covered by the cmap table, bye maximal size of the single-byte encoding - by number 256 (and it is really 256-32=224), and in Windows'95 the large multilingual fonts with number of glyphs about 650 have appeared (and these glyphs are accessible for use through their Unicodes).
  On the other hand, the problems with so-called "non-Unicode" russian fonts are caused that Unicodes in these fonts appropriate to glyphs, representing the Russian letter, correspond for want of it to a latin code page CP1252, instead of cyrillic CP1251, though graphically to it and correspond. An apart from probablis semicompetence, the reason of emerging of such fonts was also impossibility of use in the USA-Canada versions Windows 3.1/3.11 correct cyrillic fonts - module GDI there supported a sole code page - CP1252. Besides down until appearance of strict Unicode systems or programs, such as Windows NT or Office - 97, the use of such fonts did not call any inconveniences.
  
  The encoding 3.0 - Microsoft Symbol Encoding is intended for non text fonts containing various design elements. Formally subtable cmap in such fonts also contains Unicodes of characters, but they are in so-called Unicode user area (Private Use Area), and really - in area U+F020 up to U+F0FF, being mapped by a natural image in single-byte codes 0x20... 0xFF.
  Above stated reason is invented at all not by me, but now I can not find a source in any way, where the format of the font in Symbol Encoding would be defined concretely. Similar, that it not the specification TrueType.
  Correct (or nearly so correct) the support of such fonts is carried out also for Unicode programs. So that in the certain period they could be considered most problemlos and the average generation of Russian fonts from Paragraph was such. However, the programs permitting to select for any purposes only text fonts, do not show fonts such as Symbol in the window of choice, and the Office-97 fails hyphenations and does not check up spelling for collected by them of the text.
  
  
• The table name. Table of names is contained a title of the font, family in which it enters, variation, Copyright and Trademark etc. (only 8 data types). These datas are specified for each encoding m.n of the font and are marked also by identifier of language Language ID, and languages can be a number for one coding. Lines of datas can be in the one-byte coding (for Macintosh, m=1 and ISO, m=2) and in UNICODE (for Apple Unicode, m=0 and Microsoft, m=3). From all these datas the title of the font in English is used only, and the other datas do not influence the interpretation of the font.
  
  
• The table OS/2. This table of font characteristics is contained 2 subtables, which relate to the encodings and can influence the interpretation of the font in a system.
  Within the specification TrueType 1.0 tables OS/2 have evolution from the version 0 to the version 1, and just at the expense of adding a mask of allowable code pages.
  The function Windows 95 font properties extension for the font with the table OS/2 of the version 0 in item Charset/Unicode in both windows (Supported Unicode Ranges and Supported Code Pages) writes: "Information not available in font".
  • version - 16-bit word containing a version number:
    0 (78 bytes) - up to TrueType v.1.0 rev.1.5
    1 (86 bytes) - up to TrueType v1.0 rev. 1.66
    2 (96 bytes) - under the specification OpenType v.1.*.
    (The fonts with the table OS/2 ver.2 yet did not come across to me.)
    
  • ulUnicodeRange - four 32-bit words containing a bit mask functional Unicode ranges in the font. A sense of this "functionality" Microsoft has appeared be unable to explain even in the specification TrueType. Besides this subtable, as well as specification as a whole, is guided by the standard Unicode of the version 1, whereas acting is the version 2. In this decoding of bits of the subtable ulUnicodeRange the attempt is made to arrange verbal labels from the specification TrueType and Unicode ranges from the standard Unicode 2.0, that gives some review of the standard Unicode generally.
    In the early specification TrueType, supposing the table OS/2 of the version 0, this subtable was present, but should be zero and was considered as a reserve for the future use.
    In multilingual fonts with a cyrillic Microsoft sets in this subtable bit 9 (0x00000200), though even in the full CP1251 there are representatives following Unicode ranges:
    

    Bit	Description	Unicode Range
    0	C0 Controls and Basic Latin	U+0000 to U+007F
    1	C1 Controls and Latin-1 Supplement	U+0080 to U+00FF
    9	Cyrillic	U+0400 to U+04FF
    35	Letterlike Symbols	U+2100 to U+214F

    
    However, this subtable nowhere is really used, though is deciphered during extended show of properties of the font.
    
    
  • ulCodePageRange - two 32-bit words containing a bit mask of code pages, covered by the font. The decoding of bits of the subtable ulCodePageRange is present, in particular, on a site at Microsoft.
    To cyrillic page CP1251 there corresponds(meets) bit 2 (0x00000004) in the first word ulCodePageRange.
    In the early specification TrueType, supposing the table OS/2 of the version 0, this subtable was absent.
    
    
• The table PANOSE.Developed by firm ElseWare (afterwards including in Hewlett-Packard) system of a classification of fonts realized as the 10-byte table and intended for definition of "similarity" of fonts (under the specification TrueType - only for not latin character sets). Each from bytes contains some value (not a bit mask). The following 2 field in the table are most important:
  • panose.bFamilyType - type of the font, it applicability, in the correspondence with the table:
    

    Value	Description
    0	Any
    1	No Fit
    2	Text and Display
    3	Script
    4	Decorative
    5	Pictorial (or Symbol)

    
    As has appeared, this field influences recognition of allowable character sets of the font.
    
    
  • panose.bProportion - proportion of the font in the correspondence with the table:
    

    Value	Description
    0	Any
    1	No Fit
    2	Old Style
    3	Modern
    4	Even Width
    5	Expanded
    6	Condensed
    7	Very Expanded
    8	Very Condensed
    9	Monospaced

    
    The value panose.bProportion=9 determines the font of fixed width. In the correspondence the choice of the font in the programs happens to this field, if they for any purposes need only monospaced font, irrespective of to what the font is "actually".
    However at very many old Russian fonts claiming for a fixed width, even this field of the table PANOSE, let alone other fields is not filled in.
  
  
• Recognition accessible of character sets of the font.
  For want of to installation of the font it "Unicodeness" and accessible the character sets are determined in Windows'95 approximately by the following not documented rules:
  1. The fonts with the table OS/2 ver.1 - allowable code pages (scripts) are determined by intersection of a set of allowable pages from a field ulCodepageRange (for script cyrillic bit 2 should be set) and set of character sets supported by GDI.
     The special case - support of a character set OEM/DOS (which generally defined values has no), used in DOS-window. Probably, in this case it is necessary to have in the mask of allowable codepages bit that corresponds to concrete language settings in Windows, for Russian settings it is CP866 (bit 49).
     
  2. (Multilingual) fonts with the table OS/2 ver.0 - allowable code pages (scripts) are determined (based on set of character sets supported by GDI) proceeding from actual availability of characters in the font, in particular for script cyrillic it is necessary and enough, that in the font the letter "£" (small cyrillic io, U+0451) is represented.
     (Recently I, have checked up it, at last, having made practically from one letter "£" the microfont onecyr.ttf, and also has found some documentary confirmation of this logic, see notes about Unicode in Postscript.)
     The special case - support of a character set OEM/DOS (which generally defined values has no), used in DOS-window. Most likely, such fonts are considered not supporting OEM/DOS-coding.
     
  3. The monolingual fonts from (inter)national ("localised") versions Win 3.1 - their sole code page is contained in higher byte of a field fsSelection, and it is a program-internal Microsoft-proprietary code of a character set (for script cyrillic - 204=0xCC). Such fonts will correctly be recognized as in the national versions Windows 3.1*, and in Windows'9x. However it is not only not documented, but also contradicts the specifications TrueType - as to the first issue rev. 1.0, and last revision rev. 1.66, where unequivocally it is required, that the unused bits of the fsSelection field should be equal to zero.
     I think, as such fonts are considered not supporting OEM/DOS-encoding.
     
  4. Monolingual fonts, in which the table cmap has the coding 3.1 - Microsoft UGL, and in the table PANOSE the type of the font panose.bFamilyType=5 (Pictorial) is indicated. Such fonts in Windows'95 by rather unexpected manner are treated as fonts with a character set Symbol and, for example, in Word-97 in the file are written Unicodes from range U+F020... U+F0FF, in the font at all absent.
     (Such russian and easterneuropean fonts are containing for example in multilingual products of Accentsoft.)

Unicode and Postscript-fonts

If the work with TruÅType by fonts (first of all in Windows) is based to taking characters on appropriate numerical value in Unicode, the work with Postscript fonts is based on names of characters in the font.
If it is necessary to take characters via Unicode (in Windows NT, in Word'97) so names of characters should be to deliver in the correspondence with Unicode values, that the manager of Postscript-fonts (Adobe Type Manager) should do. It is known that ATM/NT 4.0 can do such comparison, whereas ATM/95 4.0 - can't. The list of glyph names (Adobe Glyph List) and their Unicodes is contained in the documents from Adobe, in the main document Unicode and Glyph Names the algorithm of such comparison is defined and the references to the glyph lists are contained.

• It is interesting, that for want of solution of a particular problem - how to select the necessary Unicode value, if for some characters actually there are two possible values (for example, the Greek letter "mu" actually represented in two places: U+00B5 MICRO SIGN and U+03BC GREEK SMALL LETTER MU) - the important note about algorithm is made, on which the presence at the font of code pages 1250-1258 from Microsoft is determined. Affirms, that OpenType converter, and also ATM/NT and driver TrueType in GDI decide it on availability in the font of the following glyphs-markers:
  
  

  Glyph image	Glyph name	Unicode and Unicode name	Windows Code Page
  	ncaron	U+0148 LATIN SMALL LETTER N WITH CARON	1250: Windows Latin 2 (Central Europe)
  	afii10071	U+0451 CYRILLIC SMALL LETTER IO	1251: Windows Cyrillic (Slavic)
  	ecircumflex	U+00EA LATIN SMALL LETTER E WITH CIRCUMFLEX	1252: Windows Latin 1 (ANSI)
  	upsilondieresis	U+03CB GREEK SMALL LETTER UPSILON WITH DIALYTIKA	1253: Windows Greek
  	Idotaccent	U+0130 LATIN CAPITAL LETTER I WITH DOT ABOVE	1254: Windows Latin 5 (Turkish)
  	afii57664	U+05D0 HEBREW LETTER ALEF	1255: Windows Hebrew
  	afii57410	U+0622 ARABIC LETTER ALEF WITH MADDA ABOVE	1256: Windows Arabic
  	uogonek	U+0173 LATIN SMALL LETTER U WITH OGONEK	1257: Windows Baltic Rim
  	dong	U+20AB DONG SIGN	1258: Windows Vietnamese

  
  
• Quite recently Dmitry Yunov found a method to write character set into Type 1 PS-font under Windows'9x and ATM4 (is spoken, that it was by news to the experts from Adobe).
  A charset value (for a cyrillic 0xCC=204) should be written into PFM-file in byte with offset 0x55. It is possible also to add following lines at the end of the font INF-file:
  WindowsCharSet 204
  WindowsFirstChar 32
  WindowsLastChar 255
  Then during font installation ATM will create from a pair AFM + INF a correct PFM with a correct charset code.
  
  As a result in the system will appeare a font, which Windows designate as device (printer) font, with a sole charset (in our case with cyrillic).
  If we work with Russian or russian-tuned Windows'9x (main Codepage is CP1251), such fonts should correctly display in Office-97 on a screen correctly print on printer. Nevertheless Unicode character table for them is not shown correctly neither inBjondi Character Agent, nor in Word-97.
  As asserts Dmitry Yunov, in case of incongruity of main language in Windows and of font character set these fonts "will be on the screen in MSOffice-97 either with incorrect metric or with a lot of missing characters". Under Windows'98 I have not detected such effects in Word'97, but font with charset=2 (Symbol), in WordPad was displayed with incorrect metric.
  For editing fonts and INF-files it is possible to take advantage of the special program.

Fonts and Unicode applications

Office-97

The main feature of files and philosophy of Office-97, first of all Winword-97, - almost full transition to the coding Unicode, i.e. and in the documents Word-97 a text part represented in Unicode, and during fulfilment of the program - input and text processing - is used (here, certainly, the clause), on all probability is necessary, it is exclusively Unicode. However, as well as in the previous versions Word, for normal work with language it is necessary, that in Word'Å there was it a support, irrespective of Unicodeness of the font.

• Fonts. It are required Uicode fonts, in which letter of national languages have correct Unicodes, and Windows'9x sees in the font an appropriate character set.
  Fonts which are not have appropriate character set, is, as a rule, fonts have only script western or symbol encoding. Word-97 can, to some extent to use by a desirable art and such fonts, but with numerous inconveniences and restrictions. In particular, for want of switching of the keyboard with English on national (for example, Russian) will be switching the font happens on, where the necessary character set is (usually - Times New Roman). Still some features of a behaviour in these cases:
  
  • For want of use of the font have only script western, should mark the text as English. For want of it the russian checkspelling and hyphenation transpositions will not work (though if subsequently mark this text as Russian, even spellcheck works). The change of the font on an Unicode font will reduce in loss of "russian-features". The change of the font from Unicode on only western will convert russian etc. text into "small squares".
    Such russian font is possible convert to Unicode with the help of accessible converters from the section Converters of the font encoding and other tools.
    
  • A font that has symbol encoding, calls a little bit less problems. And in this case such language functions will not work, as check of spelling, and the hyphenation will be made in any place of a word. The change of this font can convert the text into "small squares" (that, probably, is explained by absence in Unicocde font of the Unicode range U+F020... U+F0FF), though a change from Unicode font on a symbol font and even the consequent return of the font passes correctly (that, probably, is explained by translation "alphabetic" Unicodes through a code page in "privat use" Unicode range of the font symbol).
    Such russian font is possible "convert to Unicode", perhaps, only with the help of programs from R.Kinch' ttf_edit from the section tools, as the apart from of a modification of Unicodes is required to change a label of the encoding - from 3.0 to 3.1 and in appropriate way to change name table.
• Printing. As was clarified, the correct look of a multilingual text on a screen in Word-97 is not yet warranty, that it will be correctly printed on the printer or sent by fax. Purely speaking, it is not an error of Word-97, but inferiority of majority (!) printers drivers: Unicode functions of printing in them in this or that measure work not properly. Though there are also exceptions, for example, Windows'95 built-in drivers of HPLaserJet4L printer. Other drivers can represent for want of printing small squares instead of the necessary characters. In the worse case even national letters (Russian, Greek etc.) from code pages supported both Windows and Word-97 are not represented. In the best case are not represented only characters, that are not included in Windows' standard character sets (charsets), in particular, pseudo-graphic (containing in all standard "large" fonts). The driver for HPLaserJet 5-6, offered now on the server Hewlett-Packard concerns to the last, best case, it can print all that can print with standard fonts Wordpad, but not all, that can extract from the font Word-97.
  Completely decide a problem can ony developers of drivers, but some partial solutions are possible and from the Word-97 side. They are offered on the server Microsoft in the article from a knowledge base Q159418:
  1. If is installed Word-97 Service Release 1 (SR-1), it is necessary to add in the system Registry the following key:
     REGEDIT4
     
     [HKEY_CURRENT_USER\Software\Microsoft\Office\8.0\Word\Options]
     "NoWideTextPrinting"="1"
     
  2. If earlier Word-97 (non-SR1) is installed, the Registry must be corrected with use of the exact printer name from a folder Printers, designated in an example as Printer_name:
     REGEDIT4
     
     [HKEY_CURRENT_USER\Software\Microsoft\Office\8.0\Word\Printer_name]
     "Flags"="8192"
     In this case will be printed the numerals from code pages, which are in "intersection" of knowledges Windows'9x and Word-97, i.e. will not be not only pseudo-graphic, but also not Hebrew and Arabic, but there will be a cyrillic and Greek, and also western and easteuropean diacritical marks.
     
  3. For some kinds of printers Hewlett-Packard in the article are indicated specific of set-up deciding (in what to measure?) problem. In particular above mentioned HPLaserJet4L begins correctly for all to print, only if the option "Print TrueType as graphics" is set.
     
  4. At last, if anything from above-stated does not help, a radical means sometimes can help: for all (used) Unicode fonts with Cyrillic one must enter by a hard hand in WIN.INI in section FontSubstitutes line such as following:
     Font,0=Font,204
     Then it is necessary to say goodbye to hope to print by this font not only on Hebrew and Arabic, but also in German, in French and, probably, on Greek, but on Russian-English all will be printed correctly.
     
     
• The converter for the documents created in earler versions Microsoft Word. Word-97 extension from Agama, changing in the not readable russian document fonts and language in the correspondence with requirements Word-97.
• MS Office'97 and Russian fonts a digest from Pavel Gorodjansky.
  
  

Internet Explorer 4

  Internet Explorer 4, including majority it of components: browser MSIE, mail&news Outlook Express, in some smaller degree HTML-editor Frontpage Express, uses Unicode as the main encoding for internal purposes and in input windows. As described in a number of articles in Microsoft Knowledge Base, in MSIE is realized the concept of "multilingual object" is realized: class and functions for working with it are defined. All this allows to support practically anyone encoding in the Internet, including Unicode-based (UTF-7 and UTF-8), and for an rendering of characters of language (character set), which is not supported by default font, is selected the font, where this language present. Such font substitution works for those Unicode's, which can be associated to the certain character set (problem similar to a problem of recognition accessible character sets of the font), and this substitution will not made, if the character set in the font present, but some characters from this set are absent - then they are represented by small squares.

• Wonderfully, that the multilingual support in MSIE4 can be controlled by user, it is based on files of national/native language support NLS and branch in the Registry
  [HKEY_CLASSES_ROOT\MIME\Database].
  The described schemes was valid until MSIE 5 beta 1, however in MSIE 5 beta 2 controllabilities of language support was reduced and is displaced in MLANG.DLL. Modifications in the Registry have ceased to work as necessary.
  The titles of files NLS look as CP_nnnn. NLS in Windows'95/'98 (in the Windows\System directory) and ó_nnnn. NLS in Windows NT (in the Windows\System32 directory), where nnnn - number of a code page (1251, 866 etc.)
  These files contain definitionof their code page via Unicode, table of mapping from Unicode in their code page and a number of some other tables. The approximate description of a NLS-file structure (CP_nnnn. NLS and C_nnnn. NLS) contains results of my observations, as official documentation to find it was not possible.
  (File LOCALE.NLS contains an information specific to languages of the world, in particular format of date, time, currency, information about the alphabetic order, title and capitals etc.)
  For encoding koi8-r is page number 20866 designated (ache asserts, that by IBM for koi8-r number 878 was already chosen, however Microsoft did not know about that or has that fact ignored). For ISO-8859-5 is designated 28595, and for koi8-ru - 21866 (it is the Ukrainian code page which was more known as koi8-u, and under this name in April, 1998 it is received the status RFC2319 and registered in IANA as MIME-charset).
  It is possible to find some files, absent in delivery, in particular CP_1255. NLS (Hebrew) and CP_1256.NLS (Arabic), in the national versions Windows and on the disk with VC ++ 5, and now and in the distribution kit with MSIE5.
  The indicated branch in the Registry is divided on four:
  
  • Content Type, where the correspondence of MIME-types and file extensions is set (there is no relation to multilingual support);
    
  • Codepage, where in keys the supported code pages are listed and is determined a "presence" of a code page in MSIE and Outlook Express:
    [HKEY_CLASSES_ROOT\MIME\Database\Codepage\nnnn]
    Variables:
    "Level":
    
    • 0-th bit in the first from four bytes answers for presence of the encoding in the Outlook Express encodings list;
      
    • 1-st bit of the same byte answers for presence of the encoding in the Internet Explorer encodings list.
      
    • The sense of 2nd bit in the first byte, and also of 2nd of four bytes (usually equally with first) is not clear to me (it seems that it plays any role for Unicode encodings and hieroglyphic languages);
      
    • Third and fourth byte are equal to zero, they are probably reserve.
      
    
    "Family" - code page, base for the given coding (1251 for a cyrillic);
    "Description" - verbal description of the encoding (for example, "Cyrillic (Windows)")
    "FixedWidthFont" - monospaced font;
    "ProportionalFont" - proportional font
    (Probably here is defined default fonts, choice of fonts fot MSIE and Outlook Express is specified in section "Internet Explorer" and "Outlook Express" of absolutely other Registry branch accordingly),
    "BodyCharset" - mayby the default encoding for e-mail.
    "WebCharset" - mayby the default encoding for WWW.
    "Encoding" - it is not known.
    
  • óharset - the definitions of allowed values for MIME-charset among which are main values and synonyms.
    • "Main" charset, variables:
      • "InternetEncoding" - encoding (code page) nnnn, defined in the above described branch Codepage;
      • "Codepage" - main Windows codepage for the given language (1251 for all Russian encodings).
    • "Synonyms" charset, variable:
      "AliasForCharSet" - name of the "main" charset, and synonym can be any, if only not conterminous with other.
  • Rfc1766 - here is contained list of hexadecimal codes of languages of the peoples in the world, in the correspondence with RFC1766, their mnemonic label and description (where it is used - is not clearly), approximately so:
    "043D"="ji;Yiddish"
    "0435"="zu;Zulu"
    
    
  
  
• It is possible to add support for Hebrew and Arabic in various components MSIE 4 and in Windows'9x as a whole. However to me is unknown a method to achieve the writing from right to left and bidirectionality aÅ all. I suspect, that it is impossible - otherwise there would be no necessary to develop hebrew- and arabic- "enabled" versions (Windows with English interface and support of bidirectionality and semitic languages). See detailed instructions for adding Hebrew and Arabic on broken English.
  
  
• Support of the perverted encodings: the attempt is made to learn Outlook Express (4 and 5beta1) for Windows'95/'98 and for Windows NT (NT is checked worse) to read the messages, former in koi8-r and recoded once more (by the server of the sender) from CP1251 in koi8-r. In archive file   cyrperv.zip files for Windows'95/'98 are in the subdirectory W95, and for Windows NT - in the subdirectory NT.
  For installation of the perverted encoding it is necessary the file CP_24866. NLS to place in Windows\System (for NT - C_24866. NLS in Windows\System32) and to execute the file PERVRS95.REG (for NT - PERVRSNT.REG).
  Then after reboot among the OE encodings will appear "CyrPerversion (Win to KOI)". If in the line with level to replace digits 1 with digits 3, the same encoding will appear and in browser, only what for?...
  I can not tell, that completely has understood, how it is all works, whether is not present at MS of the plans for number 24866 and what is the "correct" method of choice of number of a code page for own purposes. It would be desirable also to prohibit to send the messages in perverted (and some standardized encodings), but I do not know, how...
  
  
• Support of the "lower pseudo-graphic" (control characters with codes 0...31), popular in FIDO-conferences. In the file   ctrlnls.zip are contained modified NLS for koi8-r, with which it is necessary to replace initial (previously having saved old). In Win'9x it is necessary to copy the file CPA20866.NLS with replaced name CP_20866.NLS in the catalogue Windows\System (in "MS DOS mode"), in Windows NT - to copy file CA20866 with replaced name C_20866 in the catalogue Windows\System32. (The temporary name is specially made different to avoid casual damages.)
  
  
• FidoLook Express - modification of Outlook Express for more convenient work with echo-confereneces Fidonet (adding of a header X-Comment-To and other), where the above described support of the win-to-koi-perversion is inserted.
  
  
• Ukrainization of programs "Internet Explorer 4" and "Outlook Express". Th instruction on homepage from Valery Zhurachovsky on correct setup of the encoding koi8-u, page is in the Ukrainian language.

Internet Explorer 5 beta 2

• The support of the perverted encodings in Outlook Express 5beta2 is possible, but not by a so natural method, as it was made in Outlook Express 4 and 5beta1 (and is described too on the rights of a beta). It is easier to sacrifice all by one from the european encodings, for example turkish: Turkish (Windows). For this purpose it is necessary as before to locate in Windows\System the file CP_24866.NLS (for NT - C_24866.NLS in Windows\System32) from archive  cyrperv.zip, and then to interchange in the Registry values for Windows'9x:
  [HKEY_LOCAL_MACHINE\System\CurrentControlSet\control\Nls\Codepage]
  "1254"="cp_24866.nls"
  And for Windows NT:
  [HKEY_LOCAL_MACHINE\System\CurrentControlSet\control\Nls\Codepage]
  "1254"="c_24866.nls"
  
  After that for want of choice Turkish (Windows) win-to-koi-perversion becomes readable.

Netscape Communicator 4

• The possibilities of serios language support setup in Netscape are to me unknown.
  
• Cyrillic for MS Windows Netscape. Paul Gorodyansky Homepage about rusian adaptation of Netscape, or How to learn this program to correct handle with the Russian letters. In each version - their own highlights:-)
  

Adobe Photoshop 5 and Illustrator 7

Large fonts Windows'9x/NT4

• Glyph List WGL4
  The new True Type Specification is contained definition (through Unicode with the indication of Postscript Name) of the "paneuropean" character set with 652 glyphs, called Windows Glyph List 4, or WGL4.0. It covers codepages 1250, 1251, 1252, 1253 and 1254, i.e. contains a large part of the latin letters with various diacritical marks, Greek letters and Cyrillic, and also pseudo-graphical characters from codepages for DOS. However this glyph set does not include Hebrew and Arabic characters.
  In the specification it is compared to standard character sets of fonts for Windows 3.1, Macintosh and UGL (Unicode Glyph List) of vague purpose. However, is formal at all fonts under Windows the subtable cmap is used of a format 4, coding 3.1, also called UGL.
  Practically precisely correspond WGL4 main fonts in distribution of Windows'9x or NT4 - Arial, Courier New, Times New Roman also number of other fonts which have come from Microsoft and from other sources.
  
  
• Euro and modification in Microsoft codepages
  Association of Europe and the process of transition to the unified Euro-currency has brought in particular to the creation of a new character "Euro", included in Unicode as U+20AC, in spite of the fact that there already was a label for Euro-currency U+20A0. The character became popular (almost as the problem of year 2000), it have included in new fonts, and Microsoft even has made changes to code pages for Windows, it has added å×ÒÏ:
  In an item 0x80 (128) in Codepages 1250 Eastern European, 1252 Western, 1253 Greek, 1254 Turkish, 1257 Baltic, 1255 Hebrew, 1256 Arabic, 1258 Vietnamese, 874 Thai
  And in an item 0x88 (136) in Codepage 1251 Cyrillic.
  
  To the Codepage 1252 Western 2 more characters are added:
  In an item 0x9E - (U+017E) Latin Small Letter Z With Caron and
  In an item 0x8E - (U+017D) Latin Capital Letter Z With Caron.
  The computer- and publishing related public is perplexed, the truth, why two more inmportant ligatures are not included: fi and fl.
  It is offered patch for NT4, changing code pages and keyboard driver for providing of access to new characters. In Windows'98 and NT5 the support of new characters is included initially. It is a little bit more than details among problems and answers on a site Microsoft:
  http://www.microsoft.com/typography/faq/faq12.htm
  In Windows'95 it is possible to include support for Euro, if to patch the table, defining character sets in resources GDI.EXE, and also table for a code page 1252 (which also is contained in GDI.EXE, but in resources is absent). In the tables it is necessary to replace hexadeciaml bytes
  80 00 (for an item 0x80) on AC 20. It will enough for appearance Euro in Character Map and in majority of the programs working through font script.
  Advise also to make similar replacements in files kernel32.dll, unicode.bin and *.nls. It is possible to make by search of a hexadeciaml sequence
  80 00 81  00 and replacement it on AC 20  81  00. Maybe, then Euro will appear in Internet Explorer 4 and similar Unicode-aware programs.
  
  

  Character (GIF)	Character (in the form &#nnn;)	Title	Unicode
  	₠	Euro-currency, ECU old designation	U+20A0
  	€	Euro, Euro-currency new designation	U+20AC
  	Ž	Latin Capital Letter Z With Caron	U+017D
  	ž	Latin Small Letter Z With Caron	U+017E
  	fi	Latin Small Ligature fi	U+FB01
  	fl	Latin Small Ligature fl	U+FB02

  
  
  
• Accessible multilingual fonts
  The large fonts, that was near to me, represented in the table with the indication of their properties.

Converters of the font encoding and other tools

• True Type SDK.Some programs for the analysis and some updating TrueType fonts, mainly program ttfdump, for the font "decompiling". Archive is contained also programs flint (check of a correctness of the font file), addtable (adding of the table to the file of the font), sbit32 (adding of a raster image - "bitmap" - to the font), utilities for work with True Type Collections (libraries of fonts). Font editors among these programs are not present.
  
• Windows 95 font properties extensionHomepage of the Microsoft's program for extended displaying True Type font file properties, including contents of the language subtables in the OS/2 table, number of fields of the name table and some information about a history of the font and its title from the tables in the font (additional fields in the name table according TrueType Open Specification) or from an own data base.
  
• http://www.glasnet.ru/~kazarn/ttfconva.zip or
  ftp://kgb.quarta.com/WinUtil/ttfconv.zipConverter in Unicode of a cyrillic TrueType font: program for adding into encoding table (cmap table) of the Russian font, formally being only latin, also Unicode values of a cyrillic. Makes it almost completely correctly, only codes of the following 6 Serbian letters are not treated:
  

  Code in CP1251	Unicode	Title
  8A	U+0409	CYRILLIC CAPITAL LETTER LJE
  8C	U+040A	CYRILLIC CAPITAL LETTER NJE
  83	U+0453	CYRILLIC SMALL LETTER GJE
  9A	U+0459	CYRILLIC SMALL LETTER LJE
  9C	U+045A	CYRILLIC SMALL LETTER NJE
  9F	U+045F	CYRILLIC SMALL LETTER DZHE

  
  All remaining is treated correctly, in Windows-95 in the font appears script cyrillic (for want of it script western too remains), with such font correctly works Word-97.
• http://www.glasnet.ru/~kazarn/ttfconv.arj Earlier and more lame version of the Unicode font converters (will recode only 64 Russian letters, that for rigorous operation of the font in Windows-95 it is not enough), BUT containing source codes of.
  
• TrueTypeMap Version 2 of the converter of the font encoding (remapping) from Pyrus for popular Russian encodings (KOI-8, DOS 866, Windows 1251 with "unicodezationquot;), is possible use of the own table of code conversion for mapping Unicode into Codepage 1252 (script western). Shareware (without restrictions of functionality), for commercial applications - $ 49.
  It seems, however, that the program not so works...
  
• http://truetex.com .  Homepage from Richard J. Kinch, in main devoted to the project TrueTeX, on which there is a description and possibility of the request of the program ttf_edit - remarkable, most universal editor of the tables of the font TrueType, not affecting glyphs. An appropriate fragment:
  The ttf_edit TrueType font table editor available for free during a limited time to persons willing to serve as beta testers. NOTE: The ttf_edit tool provides you a programming language to edit encodings and names in TrueType fonts, not the character shapes. Look over the documentation first to see if it something you can understand and use, then send a message via e-mail simply stating (1) that you would like a copy, and (2) a one-sentence summary of your application. You will receive an e-mail reply containing a uuencoded ZIP file with versions for Windows, DOS, and Linux.
  
• CrossFont 1.2 is a Windows 95/98/NT utility for moving PostScript Type1 and TrueType fonts between Macintosh and PC platforms. Character outlines, metrics and hinting are not touched. Most known PC <-> Mac the converter of firm Acute Systems, shareware (2 weeks). Behind absence around Mac's about its work (except for the fact itself) I can not tell anything.
  
• FontMonster 3.5. One the best from font table editors old (1994) program, partly font manager. Allows to edit majority of fields in the OS/2 table and in the name table (number of fields are edited only in the registered version, however people has not disregarded this program, not supported more by the author). However it does not know how to edit the encoding table in cmap and about Unicode itself does not know.
  
• Character Agent 1.11 . The free program from Bjondi International, the advanced analog to the Unicode Character Map from Windows NT, working also under Win'9x, indicating and copying in the buffer (via Unicode) any characters from the installed font, shows Unicode ranges, names of character and other it features.

Around rusification

• Questions and answers (FAQ) from Russian Windows'95 support team, containing a technique of russian adaptation of USA-Canada versions OSR2, which practically completely works on any Win'9x.
  
• Cyrillic, Russian, Slavic and East European fonts and tools for Windows Christoph Singer's Homepage, in German, English and Russian languages on problems of cyrillization and ukrainization in Windows.
  
• Roman Czyborra Roman Czyborra Homepage, containing the historical review of Russian encodings and devoted to the encodings at all, Unicode and it support in Unix.
  
• Home Page of Grigory Naumovets This homepage is devoted to the rusification and (partly) to the ukrainization of internet programs.
  
• LOCALE AS IT IS Home page of Alexander Voropaev about internationalisation of Unix-systems.
  

  Multilingual programs

• Multilingual Internet Products
  
• Multilingual PC Directory Products
  

  Fonts and font editors

• Neofont Home Page. Neofont is a heir of "Plus technology", supporting a code page (and encoding of TrueType font), simultaneously including letters from English, Russian and Latvian languages. On the server it is possible to download English-Russian-Latvian and some Unicode (with encoding changes) fonts.
  
• TrueType Typography Tending to a completeness English page with lot of informations and references.
  
• Pyrus Digital Typography the Firm - developer of the editor TrueType and Postscript of fonts FontLab (has left ver. 3). Many consider(count) it as best.
  
• Macromedia Copyright holder on the font editor Fontographer (last ver. 4.1), and, seems, on FontMÏnger, which is not supported any more.
  
• Softy Rare case shareware TueType and raster fonts editor (ver. 1.07b), however, rather hardly making a concession to the commercial programs.
  It the author - Dave Emmett - recently has died of a pancreas cancer.
  
• Fonts links for WWW etc. on the server .ousia
  
• Phonetic fonts (transcription) on the server Summer Institute of Linguistics (SIL).
• Dr. Berlin's Foreign Font Archive. The references to fonts for eight tens languages and number of utilities. This reference here for a long time very much lacked...
  
• KOI8-R fonts   composed by me KOI8-R fonts, which encoding is made maximum universal: script western and script cyrillic look as KOI8-R (with some deviations for compatibility with Netscape), attention payed also to modifications of code pages in Windows'98 and NT5/2000. Into fonts are added also the last cool extensions of the name table with the description and references to the vendor/designer. The old version of these fonts is accessible also.
• Erfonts Russian fonts (TTF and FON) in the every possible encodings from Gavin Helf.
• CourierDOSCTT   Courier-like cyrillic fonts in DOS-encoding from Paratype, improved for compatibility with modification of code pages in Windows'98 and NT5/2000.

  Examples

• Ethymology of "abrakadabra". A small example of multilingual page in UTF-8.
  
• The table of not-ASCII characters in HTML, represented in an "ampersand" kind:
  &#<name> or &#<unicode>. Internet Explorer 4 and 5 with font  Lucida Sans Unicode shows in this table almost all.
  

  return to the contents