Table of Contents

Search

  1. Preface
  2. Introduction to Transformations
  3. Transformation Ports
  4. Transformation Caches
  5. Address Validator Transformation
  6. Aggregator Transformation
  7. Association Transformation
  8. Bad Record Exception Transformation
  9. Case Converter Transformation
  10. Classifier Transformation
  11. Comparison Transformation
  12. Consolidation Transformation
  13. Data Masking Transformation
  14. Data Processor Transformation
  15. Decision Transformation
  16. Duplicate Record Exception Transformation
  17. Expression Transformation
  18. Filter Transformation
  19. Hierarchical to Relational Transformation
  20. Java Transformation
  21. Java Transformation API Reference
  22. Java Expressions
  23. Joiner Transformation
  24. Key Generator Transformation
  25. Labeler Transformation
  26. Lookup Transformation
  27. Lookup Caches
  28. Dynamic Lookup Cache
  29. Macro Transformation
  30. Match Transformation
  31. Match Transformations in Field Analysis
  32. Match Transformations in Identity Analysis
  33. Normalizer Transformation
  34. Merge Transformation
  35. Parser Transformation
  36. Python Transformation
  37. Rank Transformation
  38. Read Transformation
  39. Relational to Hierarchical Transformation
  40. REST Web Service Consumer Transformation
  41. Router Transformation
  42. Sequence Generator Transformation
  43. Sorter Transformation
  44. SQL Transformation
  45. Standardizer Transformation
  46. Union Transformation
  47. Update Strategy Transformation
  48. Web Service Consumer Transformation
  49. Parsing Web Service SOAP Messages
  50. Generating Web Service SOAP Messages
  51. Weighted Average Transformation
  52. Window Transformation
  53. Write Transformation
  54. Appendix A: Transformation Delimiters

Developer Transformation Guide

Developer Transformation Guide

Character Encoding

Character Encoding

A character encoding is a mapping of the characters from a language or group of languages to hexadecimal code.
When you design a Script, you define the encoding of the input documents and the encoding of the output documents. Define the working encoding to define how the IntelliScript editor displays characters and how the Data Processor transformation processes the characters.

Working Encoding

The working encoding is the code page for the data in memory and the code page for the data that appears in the user interface and work files. You must select a working encoding that is compatible with the encoding of the schemas that you reference in the Data Processor transformation.
The following table shows the working encoding settings:
Setting
Description
Use the Data Processor Default Code Page
Uses the default encoding from the Data Processor transformation.
Other
Select the encoding from the list.
XML Special Characters Encoding
Determines the representation of XML special characters. You can select
None
or
XML.
  • None.
    Leave as & < > " '
    Entity references for XML special characters are interpreted as text. For example, the character
    >
    appears as
    >
    Default is none.
  • XML
    . Convert to & < > " '
    Entity references for XML special characters are interpreted as regular characters. For example, &gt; appears as the following character:
    >

Input Encoding

The input encoding determines how character data is encoded in input documents. You can configure the encoding for additional input ports in a Script.
The following table describes the encoding settings in the
Input
area:
Setting
Description
Use Encoding Specified in Input Document
Use the codepage that the source document defines, such as the encoding attribute of an XML document.
If the source document does not have an encoding specification, the Data Processor transfomation uses the encoding settings from the
Settings
view.
Use Working Encoding
Use the same encoding as the working encoding.
Other
Select the input encoding from a drop-down list.
XML Special Characters Encoding
Determines the representation of XML special characters. You can select
None
or
XML.
  • None.
    Leave as &amp; &lt; &gt; &quot; &apos;
    Entity references for XML special characters are interpreted as text, for example, the character
    >
    appears as
    &gt;
    Default in None.
  • XML
    . Convert to & < > " '
    Entity references for XML special characters are interpreted as regular characters. For example, &gt; appears as the following character:
    >
Byte Order
Describes how multi-byte characters appear in the input document. You can select the following options:
  • Little-endian. The least significant byte appears first. Default.
  • Big-endian. The most significant byte appears first.
  • No binary conversion.

Output Encoding

The output encoding determines how character data is encoded in the main output document.
The following table describes the encoding settings in the
Output
area:
Setting
Description
Use Working Encoding
The output encoding is the same as the working encoding.
Other
The user selects the output encoding from the list.
XML Special Characters Encoding
Determines the representation of XML special characters. You can select
None
or
XML.
  • None.
    Leave as &amp; &lt; &gt; &quot; &apos;
    Entity references for XML special characters are interpreted as text, for example, the character
    >
    appears as
    &gt;
    Default.
  • XML
    . Convert to & < > " '
    Entity references for XML special characters are interpreted as regular characters. For example, &gt; appears as the following character:
    >
Same as Input Encoding
The output encoding is the same as the input encoding.
Byte order
Describes how multi-byte characters appear in the input document. You can select the following options:
  • Little-endian. The least significant byte appears first. Default.
  • Big-endian. The most significant byte appears first.
  • No binary conversion.

0 COMMENTS

We’d like to hear from you!