Converting analytics to Unicode

The information in this appendix is for organizations that have existing implementations of the non-Unicode ACL products, and are migrating to the Unicode edition of ACL Analytics Exchange. Existing analytics and scripts are automatically converted to Unicode, but you must ensure that the logic of the scripts remains the same when applied to Unicode data.

Unicode is a standard for encoding text that uses two bytes to represent each character, and characters for all languages are contained in a single character set. The Unicode editions of ACL products allow you to view and work with files and databases that contain Unicode-encoded data in all modern languages.


ACL Analytics and the ACL Analytic Engine support little-endian encoded Unicode data. These products cannot be used to analyze big-endian encoded data.

The following list outlines the key areas you should be aware of when you convert to the Unicode version of ACL Analytics Exchange:

  1. Encryption of Unicode scripts is not currently supported.

  2. ACL project files and log files are encoded as Unicode data (UTF-16) and cannot be used with any non-Unicode versions of ACL.

  3. When you use ACL to define print-image and delimited files that contain ASCII or EBCDIC-encoded text, the fields in the ACL table containing this data are assigned the Unicode data type by default.


The information in this document focus on the changes required to convert analytics to Unicode. You can find out more about the Unicode encoding standard, and Unicode-specific functions, in the help system for the Unicode version of ACL Analytics.

Section contents

(C) 2015 ACL Services Ltd. All Rights Reserved.