Home Forums XMetaL Tips and Tricks Script Example: Custom Special Characters Form (XFT) Reply To: Script Example: Custom Special Characters Form (XFT)

Derek Read

Reply to: Script Example: Custom Special Characters Form (XFT)

OK, a quick test shows that this isn't too hard to figure out.

With a default installation prior to DITA OT deployment you need to modify the following three files:

C:Program FilesCommon FilesXMetaL SharedRenderXxep.xml

Uncomment the section that enables the Windows font mappings to the fonts “Arial”, “Times New Roman”, “Courier New”, “Tahoma”, “Verdana” and “Palatino”. The line just before that section of the file has the following comment:

C:Program FilesCommon FilesXMetaL SharedDITA_OTdemoxmfocfgfofont-mappings.xml

Add a new 'physical font' section inside each of the 'logical font' sections in that file to specify that Greek characters should be treated specially. You can call the 'char-set' anything you like provided it matches the setting in the next file (below). Note: If you prefer to use other fonts (perhaps you have a fancy one that you like to use just for Greek) you would first need to add a new section telling XEP where that font is in the previous file (above).

Here are the new 'physical font' sections I've added to font-mappings.xml:
                        …leave existing settings…

                        …leave existing settings…
                                                        Times New Roman

                        …leave existing settings…
                                                        Courier New

C:Program FilesCommon FilesXMetaL SharedDITA_OTdemoxmfocfgfoi18nen_US.xml (or the actual file being used if you are using xml:lang)

Add a new 'alphabet' section with a 'char-set' value that is the same as you used in the previous file above. Here's mine:




Note that these values represent the main section for Greek characters defined in Unicode 5. If you use other characters that should be in there you'll need to expand that section. The ja_JP.xml file is perhaps a better example to look at as it is more complex than the default en_US.xml file.