/vivoManagement/app/Plugin/CakePdf/Vendor/dompdf/lib/ttf2ufm/ttf2ufm-src/encodings/README.html

https://bitbucket.org/vsposato/vivo-tools · HTML · 81 lines · 69 code · 12 blank · 0 comment · 0 complexity · 81bca04962d31b4d35f9c0c1af2ab359 MD5 · raw file 

    

  1. <HTML>
    2. 

  2. <HEAD>
    3. 

  3. <TITLE>
    4. 

  4. The INSTALLATION GUIDE 
    5. 

  5. </TITLE>
    6. 

  6. </HEAD>
    7. 

  7. <BODY>
    8. 

  8. Sergey A. Babkin
    9. 

  9. <br>
    10. 

  10. <A HREF="mailto:babkin@bellatlantic.net">
    11. 

  11. &lt;babkin@bellatlantic.net&gt;</A> or <A HREF="mailto:sab123@hotmail.com">&lt;sab123@hotmail.com&gt;</A>
    12. 

  12. <p>
    13. 

  13. <! 
    14. 

  14. (Do not edit this file, it is generated from README.html!!!)
    15. 

  15. >
    16. 

  16. 

  17. <H3>
    18. 

  18. The Translation Tables
    19. 

  19. </H3>
    20. 

  20. <!
    21. 

  21. ----------------------
    22. 

  22. >
    23. 

  23. 

  24. These translation tables are used to translate the Type 1 fonts between
    25. 

  25. different encodings of the same language.
    26. 

  26. <p>
    27. 

  27. 

  28. The file names are supposed to have the suffix <tt>.tbl</tt>. Each file
    29. 

  29. describes one encoding, and all the tables for a given language
    30. 

  30. are stored in the same directory.
    31. 

  31. <p>
    32. 

  32. 

  33. The file format is quite simple: just a sequence of rows in
    34. 

  34. format
    35. 

  35. <p>
    36. 

  36. 

  37. <tt>
    38. 

  38. &lt;name&gt; &lt;decimal code&gt;
    39. 

  39. </tt>
    40. 

  40. <p>
    41. 

  41. 

  42. The names do not have to conform to any standard, just the same
    43. 

  43. glyph must have the same name in all the files for a given language.
    44. 

  44. <p>
    45. 

  45. 

  46. Not all the codes need to be described in the tables, the codes that
    47. 

  47. are not mentioned in the tables are left untranslated. So a file
    48. 

  48. of zero length may be used in case when no translation is neccessary.
    49. 

  49. <p>
    50. 

  50. 

  51. The translation changes only the encoding table of the font and does not 
    52. 

  52. rename the glyphs in the font file.
    53. 

  53. <p>
    54. 

  54. 

  55. <H3>
    56. 

  56. Examples
    57. 

  57. </H3>
    58. 

  58. <!
    59. 

  59. --------
    60. 

  60. >
    61. 

  61. 

  62. The directory `russian' contains the tables for some encodings of the 
    63. 

  63. Russian language: KOI-8, IBM CP-866, IBM CP-1251 and just for fun
    64. 

  64. ISO-8859/5 (nobody uses it anyways). The tables describe both russian
    65. 

  65. letters and table graphics characters (except for CP-1251 for which
    66. 

  66. the table graphics is not defined, so the table graphics portion for
    67. 

  67. it is just copied from KOI-8). 
    68. 

  68. <p>
    69. 

    70. 

  70. The file for ISO-8859/1 is just a copy of file for KOI-8. It is neccessary
    71. 

  71. because Netscape has rather weird ideas about the documents in
    72. 

  72. KOI-8 encoding. The common way to fool Netscape is to set the KOI-8
    73. 

  73. fonts for the ISO-8859/1 encoding and set the default encoding
    74. 

  74. in Netscape to 8859/1.
    75. 

  75. <p>
    76. 

    77. 

  77. The directory `latin1' contains an empty table for ISO-8859/1
    78. 

  78. because it does not need any translation.
    79. 

  79. <p>
    80. 

  80. </BODY>
    81. 

  81. </HTML>
    82.