Transliteration - Dealing with Global Unicode data

The 360Science Matching Engine delivers the ability to easily process worldwide global data and supports *all* character sets and *all* worldwide languages (even Klingon – no kidding).

(UTF8 or UTF16) Unicode input data is processed by the core engine, and transliterated into English Latin characters (ISO 8859-1) (Windows-1252) Latin1 code page. So, whether your data is Latin (Worldwide/Localized), Cyrillic Россия, Hellenic Ελλάδα, Hebrew ישראל, KANJI 日本, Simplified Chinese 中国, Arabic العربية, Thai ประเทศไทย, Hangul 대한민국, or yes, even Klingon - ˈt͡ɬɪŋɑn, the 360Science Matching Engine has you covered. 

 

Did you know... Transliteration is not the same as translation. Transliteration is to transcribe a word in one alphabet into corresponding letters of another alphabet: For example, the Chinese character 昌 means “prosperous” and is pronounced “chang”. The Chinese character 李 means “plum” and is pronounced “li”. Transliteration converts the Chinese name 昌李 into “chang li”. Translation would convert this to “prosperous plum”.

DaH DaSov (And now you know - Klingon)

Note: Transliteration is supported by the underlying 360Science Matching Engine found within mSQL, mHUB API, and Alteryx360. however, transliteration is not available on our mDesktop Windows workstation platform.