How to set codepage iso-8859-1 in output XML?

Dear experts,
I want to create an XML file with codepage "iso-8859-1" from PI 7.11.
I have already tried to put the filetype to TEXT and ISO-8859-1 in the File Encoding field of my receiving CC (using the FTP adapter), but I still get an xml in codepage UTF-8.
It should also be possible to realise this via an XSL mapping, but where do I have to do this? Or is there any other way to use codepage ISO-8859-1?
Thanks in advance,
William

Hi
You can do this change at Visual Administrator level. There are some parameters you need to edit and add IS0-8859, so that Integration engine will set for that encode.
So, you can ask the Basis guys to perform this.
This would certainly works out for you.
Regards
Pothana

Similar Messages

How to determine codepage ISO-8859-1 for my output XML?

Dear experts,
I want to create an XML file with codepage "iso-8859-1" from PI 7.11.
I have already tried to put the filetype to TEXT and ISO-8859-1 in the File Encoding field of my receiving CC (using the FTP adapter), but I still get an xml in codepage UTF-8.
It should also be possible to realise this via an XSL mapping, but where do I have to do this? Or is there any other way to use codepage ISO-8859-1?
Thanks in advance,
William

Hi William,
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.
Here is 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>
Hope you can solve now ...if not pls let us know !
cheers,
Ram.

Problems creating mail attachment in codepage ISO-8859-1

Hi,
i'm sending emails from PI tom our customers. Some of them cannot read the attachements that are created in codepage utf-8.
Can anyone tell me how to create an attachment in codepage ISO-8859-1.
Thanky
BR
Ralf

Hi Ralf,
I create plain text files.
also
actually i´m using an own local ejb to create a nice looking html-email.
Can u please specify whether the attachment is going as a simple txt file or as HTML....
if it is a text file.. then the things are very simple.
From inbound XML,use the MessageTransformationBean,and specify the FCC(File content conversion)how u want the text file.
If it is a HTML or XML u can create the payload from the Mapping itself and send it to adapter.
But make sure that the attachment name is having .htm or .html and content_type is text/html
Babu

Codepage Conversionerror UTF-8 from System-Codepage to Codepage iso-8859-1

Hello,
we have on SAP PI 7.1 the problem that we can't process a IDOC to Plain HTTP.
The channel throws "Codepage Conversionerror UTF-8 from System-Codepage to Codepage iso-8859-1".
The IDOC is 25 MB. Does anybody have a idea how we can find out what is wrong with the IDOC?
Thanks in advance.

In java strings are always unicode i.e. utf16. Its the byte arrays that are encoded. So use the following codeString iso,utf,temp = "�� ";
byte b8859[] = temp.getBytes("ISO-8859-1");
byte butf8= temp.getBytes("utf8");
try{
iso = new String(b8859,"ISO-8859-1");
utf = new String(butf8,"UTF-8");
System.out.println("ISO-8859-1:"+iso);
System.out.println("UTF-8:"+utf);
System.out.println("UTF to ISO-8859-1:"+new String(utf.getBytes("iso8859_1"),"ISO-8859-1"));
System.out.println(utf);
System.out.println(iso);
}catch(Exception e){ }Also keep in mind that DOS window doesnot support international characters so write it to a file

How to set the selectedIndex when dataProvider is an XML object in DropDownList?

dataProvider was an XML object
How to set the selectedIndex when dataProvider is an XML object in DropDownList?
I do this:
<s:DropDownList id="dropDownList" requireSelection="true" selectedIndex="2"
                labelField="lastName" dataProvider="{employeeService.lastResult.employees.employee}"/>
But always the first item is selected whatever the value of selectedIndex equals to.

if i understand correctly, you want the selectedindex to be 2 when the DropDownList displays.
It might be the case that the dataprovider is being sought after it's already selected its index (as the dataprovider isn't already determined to begin with), so currently it's
     - setting the selected index to default
     - setting the selected index to 2 (your command)
     - getting the dataprovider
     - setting the selected index to default
try writing a function to set the DropDownList's selected index after it's received the information, or even just attach it to the employeeService result handler.
for quick testing sake you could just add
<s:DropDownList id="dropDownList" requireSelection="true" updateComplete="dropDownList.selectedIndex = 2"
                labelField="lastName" dataProvider="{employeeService.lastResult.employees.employee}"/>
to see if my theory is correct.

How to set the margins for the pdf output in BI Publisher

Hi There,
When we view a report in PDF format in BI Publisher, we get pdf output in an iframe.
There are two scroll bars on the right side. When we scroll down the outer scrollbar to the bottom, there is a white space between the bottom border of the pdf report and bottom portion of the window.
We are calling BI report from apex by passing the url of the report. In this case the white space at the bottom is quite evident and seems that lot of space is being wasted.
Can somebody help me, how to remove or minimize this white space.
Thanks
Krishna
Edited by: Yogi on Aug 30, 2010 5:41 PM

Hello,
open your report for editing, so you see the page with your layouts. Then click on the Link "Show as List" on the upper right. In the List of the output formats select "FO Formatted XML". This enables FO Export.
Then execute your report, click on the small menu item at the upper right. The Menu opens, select Export -> FO.
Hope that helps.
Greetimgs,
Sascha

How to convert an ISO 8583 message format to XML and vice versa within OSB.

Hi Guys,
Can anyone help me out with this problem.
ISO8583 message is used in bank or financial institutes for card-originated transactions
Example of an ISO8583 message:
02004200040000000002161234567890123456060
9173030123456789ABC1000123456789012345678
90123456789012345678901234567890123456789
0123456789012345678901234567890123456789
Where:
0200 - MTI (Message Type Indicator),
4200040000000002 - primary bitmap,
1234567890123456 - field 2,
0609173030 - field 7,
123456789ABC - field 22,
012345678901234567890123456789012345678901234567890\
1234567890123456789012345678901234567890123456789 - field 63.

Hi guys,
I was trying to do this transformation(ISO8583-XML). But I am stuck in the process of creating the MFL file. Can somebody help me with the details.
Can somebody help me with the following.
Field Type:
Field Occurance:
Field Attributes:
Termination:
Code Page:
salil

How to set minimum height size for an empty XML Form iview

Hi,
I'm trying to configure the minimum height size of an XML Form iview without sucess. Even when there is no content to show, iview height size is around 80 pixels. When there is content the automatic configuration works fine and the iview is resized properly.
The iview has automatic size and the minimum size for automatic is with 5 pixels...
Any ideas?
Thanks,
Marcelo

Hi,
I'm trying to configure the minimum height size of an XML Form iview without sucess. Even when there is no content to show, iview height size is around 80 pixels. When there is content the automatic configuration works fine and the iview is resized properly.
The iview has automatic size and the minimum size for automatic is with 5 pixels...
Any ideas?
Thanks,
Marcelo

How to set the Xml Encoding ISO-8859-1 to Transformer or DOMSource

I have a xml string and it already contains an xml declaration with encoding="ISO-8859-1". (In my real product, since some of the element/attribute value contains a Spanish character, I need to use this encoding instead of UTF-8.) Also, in my program, I need to add more attributes or manipulate the xml string dynamically, so I create a DOM Document object for that. And, then, I use Transformer to convert this Document to a stream.
My problme is: Firstly, once converted through the Transformer, the xml encoding changed to default UTF-8, Secondly, I wanted to check whether the DOM Document created with the xml string maintains the Xml Encoding of ISO-8859-1 or not. So, I called Document.getXmlEncoding(), but it is throwing a runtime error - unknown method.
Is there any way I can maintain the original Xml Encoding of ISO-8859-1 when I use either the DOMSource or Transformer? I am using JDK1.5.0-12.
Following is my sample program you can use.
I would appreciate any help, because so far, I cannot find any answer to this using the JDK documentation at all.
Thanks,
Jin Kim
import java.io.*;
import org.w3c.dom.Document;
import org.w3c.dom.Element;
import org.w3c.dom.Node;
import org.w3c.dom.NodeList;
import org.w3c.dom.Attr;
import org.xml.sax.InputSource;
import javax.xml.parsers.DocumentBuilder;
import javax.xml.parsers.DocumentBuilderFactory;
import javax.xml.transform.Templates;
import javax.xml.transform.Transformer;
import javax.xml.transform.TransformerException;
import javax.xml.transform.TransformerFactory;
import javax.xml.transform.TransformerConfigurationException;
import javax.xml.transform.dom.DOMSource;
import javax.xml.transform.Source;
import javax.xml.transform.stream.StreamSource;
import javax.xml.transform.stream.StreamResult;
public class XmlEncodingTest
    StringBuffer xmlStrBuf = new StringBuffer();
    TransformerFactory tFactory = null;
    Transformer transformer = null;
    Document document = null;
    public void performTest()
        xmlStrBuf.append("<?xml version=\"1.0\" encoding=\"iso-8859-1\"?>\n")
                 .append("<TESTXML>\n")
                 .append("<ELEM ATT1=\"Yes\" />\n")
                 .append("</TESTXML>\n");
        // the encoding is set to iso-8859-1 in the xml declaration.
        System.out.println("initial xml = \n" + xmlStrBuf.toString());
        try
            //Test1: Use the transformer to ouput the xmlStrBuf.
            // This shows the xml encoding result from the transformer which will change to UTF-8
            tFactory = TransformerFactory.newInstance();
            transformer = tFactory.newTransformer();
            StreamSource ss = new StreamSource( new StringBufferInputStream( xmlStrBuf.toString()));
            System.out.println("Test1 result = ");
            transformer.transform( ss, new StreamResult(System.out));
            //Test2: Create a DOM document object for xmlStrBuf and manipulate it by adding an attribute ATT2="No"
            DocumentBuilderFactory dfactory = DocumentBuilderFactory.newInstance();
            DocumentBuilder builder = dfactory.newDocumentBuilder();
            document = builder.parse( new StringBufferInputStream( xmlStrBuf.toString()));
            // skip adding attribute since it does not affect the test result
            // Use a Transformer to output the DOM document. the encoding becomes UTF-8
            DOMSource source = new DOMSource(document);
            StreamResult result = new StreamResult(System.out);
            System.out.println("\n\nTest2 result = ");
            transformer.transform(source, result);
        catch (Exception e)
            System.out.println("<performTest> Exception caught. " + e.toString());
    public static void main( String arg[])
        XmlEncodingTest xmlTest = new XmlEncodingTest();
        xmlTest.performTest();
}

Thanks DrClap for your answer. With your information, I rewrote the sample program as in the following, and it works well now as I intended! About the UTF-8 and Spanish charaters, I think you are right. It looks like there can be many factors involved on this subject though - for example, the real character sets used to create an xml document, and the xml encoding information declared will matter. The special character I had a trouble was u00F3, and somehow, I found out that Sax Parser or even Document Builder parser does not like this character when encoding is set to "UTF-8" in the Xml document. My sample program below may not be a perfect example, but if you replaces ISO-8859-1 with UTF-8, and not setting the encoding property to the transfermer, you may notice that the special character in my example is broken in Test1 and Test2. In my sample, I decided to use ByteArrayInputStream instead of StringBufferInpuptStream because the documentation says StringBufferInputStream may have a problem with converting characters into bytes.
Thanks again for your help!
Jin Kim
import java.io.*;
import java.util.*;
import org.w3c.dom.Document;
import org.w3c.dom.Element;
import org.w3c.dom.Node;
import org.w3c.dom.NodeList;
import org.w3c.dom.Attr;
import org.xml.sax.InputSource;
import javax.xml.parsers.DocumentBuilder;
import javax.xml.parsers.DocumentBuilderFactory;
import javax.xml.transform.Templates;
import javax.xml.transform.Transformer;
import javax.xml.transform.TransformerException;
import javax.xml.transform.TransformerFactory;
import javax.xml.transform.TransformerConfigurationException;
import javax.xml.transform.dom.DOMSource;
import javax.xml.transform.Source;
import javax.xml.transform.stream.StreamSource;
import javax.xml.transform.stream.StreamResult;
* XML encoding test for Transformer
public class XmlEncodingTest2
    StringBuffer xmlStrBuf = new StringBuffer();
    TransformerFactory tFactory = null;
    Document document = null;
    public void performTest()
        xmlStrBuf.append("<?xml version=\"1.0\" encoding=\"iso-8859-1\"?>\n")
                 .append("<TESTXML>\n")
                 .append("<ELEM ATT1=\"Resoluci�n\">\n")
                 .append("Special charatered attribute test")
                 .append("\n</ELEM>")
                 .append("\n</TESTXML>\n");
        // the encoding is set to iso-8859-1 in the xml declaration.
        System.out.println("**** Initial xml = \n" + xmlStrBuf.toString());
        try
            //TransformerFactoryImpl transformerFactory = new TransformerFactoryImpl();
            //Test1: Use the transformer to ouput the xmlStrBuf.
            tFactory = TransformerFactory.newInstance();
            Transformer transformer = tFactory.newTransformer();
            byte xmlbytes[] = xmlStrBuf.toString().getBytes("ISO-8859-1");
            StreamSource streamSource = new StreamSource( new ByteArrayInputStream( xmlbytes ));
            ByteArrayOutputStream xmlBaos = new ByteArrayOutputStream();
            Properties transProperties = transformer.getOutputProperties();
            transProperties.list( System.out); // prints out current transformer properties
            System.out.println("**** setting the transformer's encoding property to ISO-8859-1.");
            transformer.setOutputProperty("encoding", "ISO-8859-1");
            transformer.transform( streamSource, new StreamResult( xmlBaos));
            System.out.println("**** Test1 result = ");
            System.out.println(xmlBaos.toString("ISO-8859-1"));
            //Test2: Create a DOM document object for xmlStrBuf to add a new attribute ATT2="No"
            DocumentBuilderFactory dfactory = DocumentBuilderFactory.newInstance();
            DocumentBuilder builder = dfactory.newDocumentBuilder();
            document = builder.parse( new ByteArrayInputStream( xmlbytes));
            // skip adding attribute since it does not affect the test result
            // Use a Transformer to output the DOM document.
            DOMSource source = new DOMSource(document);
            xmlBaos.reset();
            transformer.transform( source, new StreamResult( xmlBaos));
            System.out.println("\n\n****Test2 result = ");
            System.out.println(xmlBaos.toString("ISO-8859-1"));
            //xmlBaos.flush();
            //xmlBaos.close();
        catch (Exception e)
            System.out.println("<performTest> Exception caught. " + e.toString());
        finally
    public static void main( String arg[])
        XmlEncodingTest2 xmlTest = new XmlEncodingTest2();
        xmlTest.performTest();
}

Replies are sometimes using ISO-8859-1character set

Hello,
I am using iCloud - and iCloud Mail - in OSX 10.10.2 Yosemite on Macs (several different Macs).
Sometimes -- rarely -- when I do a reply to all and I look at the reply I mailed out under the "Sent" tab, I see that the whole reply is "garbled".
Loads of A's and 0's.
The actual reply is preceded with a text that resembles this (the numbers change from reply to reply):
Quote
--Apple-Webmail-42--c10907ed-7ae8-475d-80.....followed by more numbers
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=ISO-8859-1;
format=flowed
Unquote
The above "header" is followed by my reply that is completely garbled up too.
How can I avoid this formatting from happening?
Thanks in advance for your help.

LDAP is UTF-8 and Oracle is set to ISO-8859-1. Now
the problem is user info goes Oracle first and is
being validated by another UTF-8 based application
and then goes to LDAP. You are lucky things start in ISO-8859-1, because it encodes a proper subset of UTF-8. However, for characters beyond 127, UTF-8 encodes the character differently than ISO. Consequently, on the transition between Oracle and the UTF-8 based application, characters need to be recoded. Similarly, when characters come out of LDAP in UTF-8, they must be recoded to ISO if this is the encoding of your pages.
In this process all the
characters are getting distorted and I cannot change
LDAP and Oracle default charsets.Well, then there is no way around a recode. You cannot even try to trick the UTF-8 based application if it is slightly picky, because some ISO codes are simply illegal in UTF-8. The other way round would work: store UTF-8 in an ISO based application without recoding. At some point the ISO based application would just see two funny characters where there is only one, but as long as this does not distort any alphabetical sorting or even presentation to a user, you would just not care.
Harald.

Problems with reading XML files with ISO-8859-1 encoding

Hi!
I try to read a RSS file. The script below works with XML files with UTF-8 encoding but not ISO-8859-1. How to fix so it work with booth?
Here's the code:
import java.io.File;
import javax.xml.parsers.*;
import org.w3c.dom.*;
import java.net.*;
* @author gustav
public class RSSDocument {
    /** Creates a new instance of RSSDocument */
    public RSSDocument(String inurl) {
        String url = new String(inurl);
        try{
            DocumentBuilder builder = DocumentBuilderFactory.newInstance().newDocumentBuilder();
            Document doc = builder.parse(url);
            NodeList nodes = doc.getElementsByTagName("item");
            for (int i = 0; i < nodes.getLength(); i++) {
                Element element = (Element) nodes.item(i);
                NodeList title = element.getElementsByTagName("title");
                Element line = (Element) title.item(0);
                System.out.println("Title: " + getCharacterDataFromElement(line));
                NodeList des = element.getElementsByTagName("description");
                line = (Element) des.item(0);
                System.out.println("Des: " + getCharacterDataFromElement(line));
        } catch (Exception e) {
            e.printStackTrace();
    public String getCharacterDataFromElement(Element e) {
        Node child = e.getFirstChild();
        if (child instanceof CharacterData) {
            CharacterData cd = (CharacterData) child;
            return cd.getData();
        return "?";
}And here's the error message:
org.xml.sax.SAXParseException: Teckenkonverteringsfel: "Malformed UTF-8 char -- is an XML encoding declaration missing?" (radnumret kan vara f�r l�gt).
    at org.apache.crimson.parser.InputEntity.fatal(InputEntity.java:1100)
    at org.apache.crimson.parser.InputEntity.fillbuf(InputEntity.java:1072)
    at org.apache.crimson.parser.InputEntity.isXmlDeclOrTextDeclPrefix(InputEntity.java:914)
    at org.apache.crimson.parser.Parser2.maybeXmlDecl(Parser2.java:1183)
    at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:653)
    at org.apache.crimson.parser.Parser2.parse(Parser2.java:337)
    at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:448)
    at org.apache.crimson.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:185)
    at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:124)
    at getrss.RSSDocument.<init>(RSSDocument.java:25)
    at getrss.Main.main(Main.java:25)

I read files from the web, but there is a XML tag
with the encoding attribute in the RSS file.If you are quite sure that you have an encoding attribute set to ISO-8859-1 then I expect that your RSS file has non-ISO-8859-1 character though I thought all bytes -128 to 127 were valid ISO-8859-1 characters!
Many years ago I had a problem with an XML file with invalid characters. I wrote a simple filter (using FilterInputStream) that made sure that all the byes it processed were ASCII. My problem turned out to be characters with value zero which the Microsoft XML parser failed to process. It put the parser in an infinite loop!
In the filter, as each byte is read you could write out the Hex value. That way you should be able to find the offending character(s).

HTTP adapter - change encoding from UTF-8 to ISO-8859-1

Hi,
I am trying to change the encoding used by the HTTP sender adapter in a scenario.
However, when I enter ISO-8859-1 in the XML Code under XI Payload Manipulation on the comms channel it has no effect - the paylad still shows as UTF-8 in SXI_MONITOR.
Am I missing a step or entering the field incorrectly ??
Thanks
Colin.

Hi,
From help
Enhancing the Payload
Some external systems, for example, Web servers in marketplaces, can only process data if it is sent as an HTML form using HTTP.
A typical HTML form comprises named fields. When transferring a completed form to the server or a CGI program, the data must be transferred in such a way that the CGI script can recognize the fields that make up the form, and which data was entered in which field.
The plain HTTP adapter constructs this format using a prolog and an epilog. Therefore, there is a particular code method that separates form fields and their data from each other. This code method uses the following rules:
     Individual form elements, including their data, are separated from each other by the character &.
     The name and data of a form element are separated from each other by an equals sign (=).
     Blanks in the entered data (for example, in multiple words) are replaced by a plus sign (+).
    All characters with the (enhanced) ASCII values 128 to 255 (hexadecimal 80 to FF) are transcribed using a hexadecimal sequence, beginning with a percentage sign (%) followed by the hexadecimal value of the character (for example, the German umlaut ö in the character set ISO-8859-1 is transcribed as %F6).
   All characters that occur in these rules as control characters (&, +, =, and %) are also transcribed hexadecimally in the same way as high value ASCII characters
http://help.sap.com/saphelp_nw2004s/helpdata/en/44/79973cc73af456e10000000a114084/content.htm
Regards
Chilla

File adapter ISO-8859-1 encoding problems in XI 3.0

We are using the XI 3.0 file adapter and are experiencing some XML encoding troubles.
A SAP R/3 system is delivering an IDoc outbound. XI picks up the IDoc and converts it to an external defined .xml file. The .xml file is send to a connected ftp-server. At the remote FTP server the file is generating an error, as it is expected to arrive in ISO-8859-1 encoding. The Transfer Mode is set to Binary, File Type Text, and Encoding ISO-8859-1.
The .xml file is encoded correctly in ISO-8859-1, but the problem is that the XML encoding declaration has the wrong value 'UTF-8'.
Does anybody know of a work around, to change the encoding declaration to ISO-8859-1 in the message mapping program?

An example of the XSL code might be as follow:
<?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>

Reverting from UTF-8 to ISO-8859-1

Hi,
i have a database installed in UTF-8, it´s a new instalation and the guides i had didnt mention any restrictions on characterset for the teams that were migrating.
Well the problem is some teams are moving some of their projects to the new server and can´t insert in a VARCHAR2 (3), for example the word "não".
My question is: Can i change the whole database to ISO-8859-1 instead of UTF-8 in order to have words like "não" inserted correctly? If so, is it a simple alter database or a more complicated operation?
Another question, is there any possibility of letting the database as is and make it work without expanding the fields value restriction?
Alx

You can't change a database character set from ISO-8859-1 to UTF8. You can only move from one character set to a strict superset, which doesn't apply here. The supported way to change the character set here would be to create a new database with the ISO-8859-1 character set, export the existing data, and import it into the new system. That assumes, of course, that all the existing characters have an ISO-8859-1 representation (characters like the Euro symbol or Microsoft's curly quotes do not).
By default, a VARCHAR2(3) allocates 3 bytes of space for data. That gets complicated when you use a multi-byte character set like UTF-8 where a character like 'ã' requires 2 bytes of storage. You can define the columns as VARCHAR2(3 CHAR) to allocate 3 characters of storage regardless of the character set. You can also set the parameter NLS_LENGTH_SEMANTICS to CHAR to make the default when you create a table that character rather than byte length semantics are set. Personally, if I'm creating a UTF8 database, I'd want to set NLS_LENGTH_SEMANTICS to CHAR.
Justin

Xml Parse throws SaxParseException.Encoding is UTF-8 insteadof ISO-8859-1 ?

Hi All,
I'm having some korean characters in my xml. when i tried to parse the xml i'm getting SaxParseException .
<?xml version="1.0" encoding="UTF-8"?> --- Throwing Exception
<?xml version="1.0" encoding="ISO-8859-1"?> --- No Exception, successfully parsed
I'm not sure why UTF-8 is failing and ISO is passing. But I'm always getting xml with UTF-8 format? Can anyone know the reason?
I also like to know the differences between UTF-8 and ISO, i don't find any good article/document for this.
Thanks,
J.Kathir

When SAX throws an exception when the encoding is set to UTF-8, then the XML contains something that is not a valid UTF-8 code (i.e. your source file is not encoded using UTF-8). Also: whenever you ask about an exception you should definitely post the entire exception, including message and stack trace.
If it doesn't throw an exception when it is set to ISO-8859-1, then it does not mean that this is the correct choice. ISO-8859-1 is defined from 0 up to 255, so any byte stream is correct in that encoding ('though not necessarily meaninful).
You absolutely have to find out which encoding the file really is, before you can parse it. If it should contain Korean characters then it is definitely not ISO-8859-1 (or any other encoding from the ISO-8859 family), as those only support latin, cyrillic and similar scripts.

How to set codepage iso-8859-1 in output XML?

Similar Messages

Maybe you are looking for