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)

XML Encoding

XML Encoding

Character encoding defines unique binary codes for the different characters used in a document. In XML files, XML header tag <?xml ...?> contains the encoding information. Informatica Address Verification supports multiple encoding types for input and output.
In the
SetConfig.xml
file, you can specify the XML encoding type for the
GetConfig.xml
file that Address Verification generates.
When you use the XML API and you do not specify an encoding type in
SetConfig.xml
, Address Verification sets the encoding to UTF-8 or UTF-16 based on whether you use 8-bit or 16-bit API functions. For direct API implementations, the default value is ISO-8859-1.
For C-based APIs, you can use either 8-bit or 16-bit functions. A
W
suffix in the function name, such as
AD_SetInputDataElementW(),
identifies a 16-bit function. If you use 16-bit functions, you must set the encoding to a 16-bit encoding. If you use a 16-bit function when the encoding is set to 8-bit, Address Verification returns an encoding error. If you are using Java APIs, you must set the encoding to UTF-16 as Java supports only 16-bit input and output.