16.20 - Checking UNICODE Normalization Form Translations - Advanced SQL Engine - Teradata Database

Teradata Vantage™ - SQL Functions, Expressions, and Predicates

Product
Advanced SQL Engine
Teradata Database
Release Number
16.20
Published
March 2019
Language
English (United States)
Last Update
2020-03-25
dita:mapPath
xzf1512079057909.ditamap
dita:ditavalPath
TD_DBS_16_20_Update1.ditaval
dita:id
kby1472250656485

When using TRANSLATE_CHK to verify UNICODE normalization form translations, any valid Unicode string can be translated to any of the normalization forms. A successful result (0) is expected unless the compatibility ideographs U+FA6C, U+FACF, U+FAD0, U+FAD1, U+FAD5, U+FAD6, or U+FAD7 are present, because these characters normalize outside the BMP, that is, outside the range U+10000 to U+10FFF.

For all normalization forms, these characters normalize as follows:

Ideograph Normalized Form
U+FA6C U+242EE
U+FACF, U+2284A
U+FAD0 U+22844
U+FAD1 U+233D5
U+FAD5 U+25249
U+FAD6 U+25CD0
U+FAD7 U+27ED3