Mira,<br /><br />Thomas explained it better than I could. FrameMaker 7.2 and earlier used <br />OTF fonts, but the applications were not unicode aware. It displayed all <br />fonts as intended in their first 128 (or even first 256) ASCII coded <br />character set.<br /><br />FrameMaker 8 is not only unicode aware, it insists that the fonts it <br />uses be proper unicoded fonts and treats all fonts as if they were---it <br />does make a few exceptions for the symbol font when opening earlier <br />Frame and Word files and perhaps a few others.<br /><br />The first part of any font is assumed to be a standard ASCII attributed <br />character, if the font you are using uses a non-standard latin alphabet, <br />it will not appear correctly ---if at all.<br /><br />This is a royal pain for everyone used to the old way of creating <br />multilingual documents. However, unicode handling of documents in other <br />languages allows people to search Frame and better yet PDF files created <br />in Frame in the language of choice and not have to wonder about how the <br />alphabet was encoded. After all, there was no internationally accepted <br />way to encode Czech, Greek, Latvian, Chinese, or Korean as ASCII characters.<br /><br />The transition may be painful, but it will hopefully be worth it. How <br />much worse than the transition from EBCDIC to ASCII can it be?<br /><g, r, & d><br /><br />...Mike