Introduction and Pre-Requisites
CopiaFacts version 8 applications are fully Unicode-enabled. With a few exceptions, all command files and text files may be encoded in the following formats:
•Unicode UTF-16 (Little-Endian or Big-Endian) with byte-order mark
•Unicode UTF-8 with byte-order mark
•The Windows System Default encoding (indicated by the absence of a byte-order mark)
CopiaFacts applications default to writing command files and other files in system default encoding. You can use the $unicode configuration command to change this default for different file types, after which the files will be written with the specified encoding. You should only do this after you have updated all machines and users to CopiaFacts version 8. Of course if you have written custom applications which process CopiaFacts files, you will also need to ensure that they can handle Unicode encodings.
Available encodings for writing files from CopiaFacts applications are:
•UNICODE (UTF-16 Little-Endian encoding)
•UTF8 (UTF-8 encoding)
•Default (Windows System Default encoding)
For an explanation of Unicode, Unicode encoding types and Byte-Order marks, visit www.unicode.org.
To display Unicode characters other than those included in the codepage for your system default encoding, you require Unicode font sets on the machine(s) you will be using. Many standard Windows fonts include a full set of Unicode glyphs. If you do not have font files installed for specific languages you wish to support, the procedure is as follows: open the Control Panel, double click on Regional and Language Option, go to the "Languages" Tab, and in the "Supplemental Language Support", select either or both checkboxes. Check the first one for Arabic, Armenian, Georgian, Hebrew, Indic, Thai, and Vietnamese, and the second one for Chinese, Japanese, and Korean. You may be asked to insert your Windows operating system media.
To enter Unicode text in command files, for example in COPIAEDIT, or to make Unicode annotations in FFVIEWER, you will also need to enable a suitable keyboard layout, for example for Cyrillic or Greek, or an Input Method Editor (IME), for example for Japanese.
Finally for CopiaFacts Console Mode applications which may output Unicode we recommend using a console font such as Lucida Console which includes Unicode Glyphs.
Updating from version 7 Unicode support
If you have been using the limited support for Unicode command files in CopiaFacts version 7, you must ensure that all Unicode files have a byte-order mark. The implementation in version 7 permitted some command files with UTF-8 encoding without a byte-order mark. Such files cannot be used with version 8 because they would be treated as having system default encoding.
The COPIAEDIT program allows editing of command files in all supported encodings. When you save a command file from COPIAEDIT, it will use the encoding specified on the $unicode command in FAXFACTS.CFG. If you edit FAXFACTS.CFG and change the value for the CFGfile keyword, the file will be saved with the specified encoding. The title bar of COPIAEDIT shows the encoding of the file.
Although UTF-8 command files can be edited in Word, we do not recommend this, because it is difficult to avoid Word appending an extra .TXT extension when saving the file.
We also strongly recommend not using Notepad to edit Unicode files, because it is capable of opening and creating UTF-8 files without a BOM and may therefore give you the incorrect impression that what you see in Notepad is valid for CopiaFacts.