Converting to Unicode
Checklist for converting to use Unicode
•If you are upgrading from an earlier CopiaFacts release, make sure you have successfully converted to version 8 and run with this release for a while before attempting to use Unicode. However if version 8 is your first CopiaFacts version and you need Unicode capability, it is much better to implement Unicode from the start.
•Note that upgrading to version 8 may involve some minor changes if your own applications are using Copia dynamic-link libraries such as the job administration DLL. If so, you may want to consider supporting Unicode at the same time you make these changes.
•Check all your own applications and make sure that if they read CopiaFacts files, they can handle Unicode-encoded files. If not, it may be possible to retain some file types which are not to Unicode-encoded, but this may be limiting.
•Check that you are not using CopiaFacts custom features or legacy options which have been excluded from Unicode support.
•Make sure that you are not using older CopiaFacts programs which are installed other than in Program Files\COPIA. Some older installations may have executable files or DLLs in the main FAXFACTS folder - make sure these are removed.
•Review the settings on the $unicode command and decide whether to retain any file types as default encoding.
•When you are ready, shut down all CopiaFacts programs and change the FAXFACTS.CFG file to specify the appropriate encodings.
Choosing between UTF-8 and Unicode
Our benchmarking indicates a slight performance advantage for UTF-8 over Unicode for reading and writing command files, mainly because of the extra time to read and write more data outweighs the overhead of converting data between formats. In addition some parts of the CopiaFacts system use UTF-8 internally and for these there is also a small saving which results from using UTF-8 files.
If you stay with command files in system default encoding, the processing times are comparable with those for UTF-8. The support for files in system default encoding is optimized for files using the standard Windows code page 1252 (Latin 1; Western European).