Table of Contents

Search

  1. Preface
  2. Getting Started with Informatica Address Verification (On-Premises)
  3. General Settings
  4. Input Parameters
  5. Process Parameters
  6. Address Enrichments
  7. Result Parameters
  8. Output Fields
  9. Assessment Codes and Return Codes
  10. Frequently Asked Questions
  11. Appendix A: Geocode Countries
  12. Appendix B: CASS Return Codes

Developer Guide (On-Premises)

Developer Guide (On-Premises)

Transliteration Limitations

Transliteration Limitations

If the source language has fewer syllables and does not have exact matches in other languages, transliteration becomes difficult. Japanese is an example for languages that are difficult to transliterate.
Most languages use a subset of the sounds a person could produce. Different languages use different subsets. If a sound used by one language cannot be represented correctly in a different script, then it needs to be approximated. This approximation might be inaccurate if the sounds in the source and destination languages are significantly different.
The following table shows how transliteration can be inaccurate when the words are transliterated from English to Kana and then back to English:
Original
Japanese
Transliterated
Philippines
フィリピン
Firipin
Düsseldorf
ヂュッセルドルフ
Dyusserudorufu
Beethoven
ベートーベン
Betoben
Some Kanji characters in the first name of the contact in Japan addresses are incorrectly transliterated into Arabic numerals instead of Latin alphabets.
The following table shows the Kanji numerals that Informatica Address Verification might incorrectly translate into Arabic numerals instead of Latin alphabets:
Kanji Numeral
Arabic Equivalent
Latin Transliteration
1
ichi
2
ni
3
san
4
yon
5
go
6
roku
7
nana
8
hachi
9
kyū
10

0 COMMENTS

We’d like to hear from you!