cancel
Showing results for 
Search instead for 
Did you mean: 

File sender adapter and content conversion with polish character

Former Member
0 Kudos

We are loading a csv file with PI 7.0 file sender adapter using "content conversion" - all fields go through EXCEPT a special character hex '208C' (space in front) looks like "Æ" is converted to hex 'C28C'.

We are using code page UTF8

We are using:

enclosuresign "

enclosuresignescape ""

fieldcontentformatting nothing

enclosureconversion NO

Hope some one can help

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hi Bohamo,

Hope you have set the following for your file sender adapter :

1. Transfer Mode is set to Binary,

2. File Type Text,

3. Encoding ISO-8859-1( for Western European Latin ).

Inorder to recognize Polish Character, try as follows :

Your sender file after coming into Pi has XML encoding declaration 'UTF-8'.

Write a simple XSLT mapping to change the value of the attribute "encoding" to "ISO-8859-1" in the output XML of message mapping . Include this XSLT map as the second mapping step in your interface mapping.

First step in your interface mapping will be your already existing message mapping.

An example of the XSL code :

<?xml version='1.0'?>

<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform">

<xsl:output method='xml' encoding='ISO-8859-1' />

<xsl:template match="/">

<xsl:copy-of select="*" />

</xsl:template>

</xsl:stylesheet>

or you can also do java mapping if you are comfortable with java code !

Cheers,

Ram.

Former Member
0 Kudos

Hope you have set the following for your file sender adapter :

1. Transfer Mode is set to Binary,

2. File Type Text,

3. Encoding ISO-8859-1( for Western European Latin ).

Inorder to recognize Polish Character, try as follows :

Your sender file after coming into Pi has XML encoding declaration 'UTF-8'.

Write a simple XSLT mapping to change the value of the attribute "encoding" to "ISO-8859-1" in the output XML of message mapping . Include this XSLT map as the second mapping step in your interface mapping.

First step in your interface mapping will be your already existing message mapping.

An example of the XSL code :

<?xml version='1.0'?>

<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform">

<xsl:output method='xml' encoding='ISO-8859-1' />

<xsl:template match="/">

<xsl:copy-of select="*" />

</xsl:template>

</xsl:stylesheet>

or you can also do java mapping if you are comfortable with java code !

Cheers,

Ram.

stefan_grube
Active Contributor
0 Kudos

Nice idea,

but: for polish you should use: ISO-8859-2 (Eastern European Latin)

hex 8C is not part of the ISO-8859 family.

So I suppose that the character is accidentially in the source.

stefan_grube
Active Contributor
0 Kudos

We are loading a csv file with PI 7.0 file sender adapter using "content conversion" - all fields go through EXCEPT a special character hex '208C' (space in front) looks like "Æ" is converted to hex 'C28C'.

8C starts a two-byte character. 20 might be trimmed by FCC.

Confirm that your inbound file is really UTF-8. Check what character you have in fact.