Checking analytics for Unicode compatibility

In addition to the required changes you need to make when upgrading to the Unicode version of ACL Analytics Exchange, you need to verify that any custom logic you have added to scripts will produce the same results when run against Unicode data. The following sections outline the areas where scripts may be affected when they are run against Unicode data.

Bit and Character functions

Each of the functions listed below returns values based on byte locations or byte counts. You need to check to ensure that these functions are still being used correctly when you move from the single-byte representation of characters used in the non-Unicode version to the double-byte character encoding used for Unicode data.

Byte length does not equal character length

You need to check the way the functions listed below are used in your scripts to ensure that they are not used in ways that assume a one-to-one correspondence between the number of characters in data and the number of bytes. If you find any instances where the logic assumes a one-to-one correspondence between characters and bytes, you must adjust the logic to work correctly with Unicode data, which uses two bytes to represent each character. Numbers specified as string function parameters, such as 4 in STRING(1000, 4) refer to the number of characters, so standard usage of these functions will not cause problems.

Conversion Functions

String Functions

Miscellaneous Functions

Substituting Unicode-specific functions

ACL Unicode products support six Unicode-specific functions that support conversions between non-Unicode and Unicode data. The following functions are available in ACL Unicode products:

You can learn more about these functions and their usage in the ACL Analytics help system.



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