PayloadZipBean and file encoding ISO-8859-1

Hi,
I'm a scenario with a receiver file zipped in target side.
I've tryed with
Message protocol --> FILE
Transfer mode --> binary
File type --> TEXT
FILE encoding --> ISO-8859-1
and with StrictXml2PlainBean and target file is correct.
But when i add PayloadZipBean, then target file seems to be incorrect. When i try to unzip it, becames an error because of the zip file seems to be created or transferred without the appropriate BINARY mode .
If I change file type to Binary, then zip file is correctly created, but spanish characters are not correctly inserted when I unzip the file.
How to solve this?
Thanks, in advance,
Carme

This is a little bit tricky.
check this blog:
/people/stefan.grube/blog/2007/02/20/working-with-the-payloadzipbean-module-of-the-xi-adapter-framework
You need two modules just for changing the encoding.

Similar Messages

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>

I need encoding='ISO-8859-1? in my xlm-file

Hi
Today I get <?xml version='1.0?> on top of my xml-file when using getXML() function in OracleXMLQuery. I need <?xml version='1.0' encoding='ISO-8859-1'?> instead.
Any tip?
/christer
null

You can't use System.out.println(). You need to use an output
stream which is encoding aware (Ex.OutputStreamWriter). You can
construct an outputstreamwrite and use the
write(char[], int, int) method to print.
Ex:
OutputStreamWriter out = new OutputStreamWriter
(System.out, "8859_1");
/* Java enc string for ISO8859-1*/
Oracle XML Team
http://technet.oracle.com
Oracle Technology Network
Hans Christian Pahlig (guest) wrote:
: Dear all,
: I've got some XML-Documents with encoding="iso-8859-1"
: and try to parse this with xmlparser-1.0.1.4's
: SAX API.
: In characters( char[], int, int) I would like to
: output the content in iso-8859-1 (Latin1) too.
: With System.out.println() it doesn't work correctly.
: German umlauts result in '?' in the output stream.
: Internally ,w,,},Y,, are stored as
: 65508,65526,65532,65476,65494,65500,65503 respective.
: What do I have to do to get output in Latin1?
: Host system here is a SPARC Solaris 2.6.
: Thanks a lot,
: HC
null

Use encode ISO-8859-7

Hi All,
     I'm new on this Forums and I want tell thanks to all for the help (I'm sorry if my english is not beatiful or correct)
     I'm using Flex on the last year and I have a web application for manage data arrive from file ASP.
     I need now to make a change on my application for read greek language. I set on my ASP the ISO for the language and all run well..
     But when I open a answer from ASP in Flex with mx:HTTPService the string on asp with greek symbol became in europe encode ISO-8859-1
     I try to change the setting of my pc to Greek but nothing change.
     Somebody know what is need to change for retrive this string in flex ?
     An other thing.. If I write in greek on a label in flex I saw the carachater without problem.
Please help me
Thank a lot for the helpand happy new year
Danny

b = GrammarText.getBytes(LastEncoding);
String strTemp = new String(b,EncodingType);Here you take a String (which is in Unicode) and convert it to bytes, using "LastEncoding". Next you take those bytes and convert them back to a String, assuming that they were encoded using "EncodingType". But they weren't, so at best this will do nothing and at worst it will produce garbage. It certainly won't do anything useful.
As I said all Java strings are in Unicode. If you want to convert something from one encoding to another encoding, you can only convert an array of bytes to a String using the first encoding, then convert that back to bytes using the second encoding. Converting a String to a String just makes no sense.

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();
}

Encoding ISO-8859-1 does not work on linux machine

Hi all
I have an xsl with encoding ISO-8859-1 .So in this xsl I put special character like € that rappresent the Euro (money) symbol.
So when I use that xsl on a window machine everithing is all right.When I use a Linux machine that code are not correctly mapped..
Why?
Help
Regards

actually I have a different mapping for �....on
window it maps the space...on linux it maps A^....
Any idea?How exactly are you determining that it is not working?
Are you printing it to the screen? Are you using String.getBytes() and then printing the byte value? What are you doing?

SSIS 2008 R2 : XML issue with ?xml version="1.0" encoding="iso-8859-1"?

hi Friends,
Please help me in below error , I am using XML data source with below encoding
<?xml version="1.0" encoding="iso-8859-1"?>
While generating xsd, i am getting below error.
'.', hexadecimal value 0x00, is an invalid character. Line 2, position 1.
the xml is parsing correctly as i am using XML spy to check the xml.
Any help is appritiated.
Thanks in advance,
Pari

I think XMLSpy does something to swallow the null char.
I'd inspect this file in a professional editor to determine whether (likely) a hex 0x00 is in the file.
Arthur
MyBlog
Twitter

Character Encoding and File Encoding issue

Hi,
I have a file which has a data encoded using default locale.
I start jvm in same default locale and try to red the file.
I took 2 approaches :
1. Read the file using InputStreamReader() without specifying the encoding, so that default one based on locale will be picked up.
-- This apprach worked fine.
-- I also printed system property "file.encoding" which matched with current locales encoding (on unix cooand to get this is "locale charmap").
2. In this approach, I read the file using InputStream as an array of raw bytes, and passed it to String contructor to convert bytes to String.
-- The String contained garbled data, meaning encoding failed.
I tried printing encoding used by JVM using internal class, and "file.encoding" property as well.
These 2 values do not match, there is weird difference.
For e.g. for locale ja_JP.eucjp on linux box :
byte-character uses EUC_JP_LINUX encoding
file.encoding system property is EUC-JP-LINUX
To get byte to character encoding, I used following methods (sun.io.*):
ByteToCharConverter btc = ByteToCharConverter.getDefault();
System.out.println("BTC uses " + btc.getCharacterEncoding());
Do you have any idea why is it failing ?
My understanding was, file encoding and character encoding should always be same by default.
But, because of this behaviour, I am little perplexed.

But there's no character encoding set for this operation:baos.write("��".getBytes());

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).

Mail Receiver - Send file in ISO-8859-1 encoding

Hi,
I'm sending mail with an attachment using mail adapter, but instead of specified ISO-8859-1 it is converted to UTF-8 no BOM,. Because of that, some characters (ñ,ç, etc) are not transferred properly.
Settings:
Message protocol: XIPAYLOAD
No mail package.
Transform.ContentType: multipart/mixed; boundary=--AaZz; charset=ISO-8859-1
Payload:
multipart/mixed; boundary=AaZz; charset=ISO-8859-1</Content_Type><Content>--AaZz
Content-Type: text/plain; charset=ISO-8859-1
Content-Disposition: inline
File attachment
AaZz
Content-Type: text/plain; charset= ISO-8859-1
Content-Disposition: attachment; filename=TestFile
iso-8859 characters ñ ç ñ ñ
AaZz--
</Content></ns:Mail>
I need advice in how to force the file to be created with ISO-8859-1 enconding.
Thanks in advance.
Regards,
Iván.

Hi Jean-Philippe,
Yes, please check my first post, if you use same settings, and create message as mine, it should work, the TestFile is created as an attachment.
Include this line in the module configuration with transform key:
Transform.ContentType: multipart/mixed; boundary=--AaZz;
If you still have issues, please give me a description of the error.
Regards,
Ivan.

XML data encoding iso-8859-1 . Currently utf-16 is default encoding

Hello ABAP Gurus ,
Need a help from you .
Scenario : We have SAP4.7 enterprise version which we have now converted to Unicode system . There is a BSP application which talks to an external web application (Non Unicode) thru HTTP protocol and sends data thru XML.
Problem : Problem is at the time when BSP application prepares the XML While preparing XML data , before converting to Unicode environment the encoding was "iso-8859-1" . But now after Unicode conversion , the encoding is "UTF-16".
The XML data looks like
<?xml version="1.0" encoding="utf-16"?><DATA><ACTION>CREATE_TICKET</ACTION><CRI
I have tried replacing "utf-16" by "iso-8859-1 " . The interface works . But at the recieving end , ie external web application , the German umlauts appear as some garbage values .
I know we need to enforce encoding . I have tried with the following code but could not suceed . The encoding appears as "utf-16".
Following is the section of code which I have written in BSP application.
Daten in DOM-Baum wandeln
    CALL FUNCTION 'SDIXML_DATA_TO_DOM'
      EXPORTING
        name        = 'DATA'
        dataobject = ls_cr_xml
      IMPORTING
        data_as_dom = if_dom
      CHANGING
        document    = if_document
      EXCEPTIONS
        OTHERS      = 1.
    IF sy-subrc NE 0.
      error_out text-f47 text-f48 space space.
    ENDIF.
DOM-Baum in Character-Stream wandeln
    if_pixml = cl_ixml=>create( ).
    IF if_pixml IS INITIAL.
      error_out text-f50 text-f53 space space.
    ENDIF.
    if_pstreamfact = if_pixml->create_stream_factory( ).
    IF if_pstreamfact IS INITIAL.
      error_out text-f51 text-f53 space space.
    ENDIF.
    if_postream = if_pstreamfact->create_ostream_cstring( string = xml_doc ).
    IF if_pstreamfact IS INITIAL.
      error_out text-f52 text-f53 space space.
    ENDIF.
--Encoding--
data: gv_str type string.
data: gv_l_xml_encoding type ref to if_ixml_encoding.
data gv_l_resultb type boolean.
gv_str = 'ISO-8859-1' .
clear gv_l_xml_encoding.
      call method if_pixml->create_encoding
        EXPORTING
          byte_order    = 0
          character_set = gv_str
        RECEIVING
          rval          = gv_l_xml_encoding.
      clear gv_l_resultb.
      call method gv_l_xml_encoding->set_character_set
        EXPORTING
          charset = gv_str
        RECEIVING
          rval    = gv_l_resultb.
        call method if_document->set_encoding
        EXPORTING
          encoding = gv_l_xml_encoding.
----Append child -
CALL METHOD if_document->append_child
      EXPORTING
        new_child = if_dom
      RECEIVING
        rval      = lv_return.
    IF lv_return NE 0.
      error_out text-f47 text-f49 space space.
    ENDIF.
--Render the XML data to output stream--
    CALL METHOD if_document->render
      EXPORTING
        ostream = if_postream.
After this section of code is executed , the variable xml_doc gets filled up with XML data .
<?xml version="1.0" encoding="utf-16"?><DATA><ACTION>CREATE_TICKET</ACTION><CRI
Can anybody help how to enforce encoding ?
Regards,
Laxman Nayak.

Hi Aslam Riaz,
Did you find any solution..?
Kindly help me on this issue.
Thanks and Regards,
Shailaja Chityala

Conversion ISO-8859-7- UTF-8 and UTF-8 - ISO-8859-7

Hi, I written this function to do a Charset conversion
from ISO-8859-7 to UTF-8 and vice versa
void ChangeChersetEncoding(String EncodingType)
String GrammarText;
try
GrammarText = Editor.getText();
b = GrammarText.getBytes(LastEncoding);
String strTemp = new String(b,EncodingType);
Editor.setText(strTemp);
LastEncoding = EncodingType;
catch (UnsupportedEncodingException e)
JOptionPane.showMessageDialog(this, "Error: " + e.getMessage
() , "Error", JOptionPane.ERROR_MESSAGE);
The steps followed are:
1)I initialize Editor (that is a JEditorPane) with a InputStreamReader, that use by default "CP1252"(window - latin1) charset encoding.
2)When I call the function the first time with EncodingType = "ISO-8859-7" and LastEncoding = "CP1252"(window - latin1), Editor shows greek character as I aspected.
3)When I call the function the second time with EncodingType = "UTF-8" and LastEncoding = "ISO-8859-7", Editor shows unknown character ('�') as I aspected.
4)The problem is when I call the function the third time with EncodingType = "ISO-8859-7" and LastEncoding = "UTF-8" Editor don't show the original greek text, as I didn't aspect.
Thank you for all.

b = GrammarText.getBytes(LastEncoding);
String strTemp = new String(b,EncodingType);Here you take a String (which is in Unicode) and convert it to bytes, using "LastEncoding". Next you take those bytes and convert them back to a String, assuming that they were encoded using "EncodingType". But they weren't, so at best this will do nothing and at worst it will produce garbage. It certainly won't do anything useful.
As I said all Java strings are in Unicode. If you want to convert something from one encoding to another encoding, you can only convert an array of bytes to a String using the first encoding, then convert that back to bytes using the second encoding. Converting a String to a String just makes no sense.

Url and File Encoding

I have the following scenario:
I have a directory which has directory names and filenames encoded in what I believe is utf-8 (the content is html). The files are derivates of DMOZ/World so they are in various languages. I can see accent marks and cryllic/greek, etc in the windows file explorer.
I need to zip this directory up (using java) and then upload it to a server and then unzip it using php. I am uncertain what encoding the server is using.
Do I UTF-8 Urlencode the file names and file paths and then zip and upload?
If so then do I need to also urlencode the links within the html?
thanks

It's not a bug, it's a lack of a feature.
The design of the Zip format requires a filename to be stored as bytes in the archive, but doesn't specify what encoding should be used to do that. Back in the days when the format was invented, that didn't matter because you could only use ASCII characters in filenames anyway.
Then when Unicode started infiltrating file systems, there was nobody powerful enough to fix the format by specifying an encoding, and the big players in the archiving field didn't care because the way they did it was de facto correct anyway as far as they were concerned.
I don't know how Microsoft and WinZip encode their filenames these days, but at any rate Java's zip classes don't even provide the option to specify an encoding. I am pretty sure that several bug reports have been filed in regard to this missing feature but I don't believe anything has been done yet.

Encoding ISO-8859-1 String

I have a code, i want to decode iso88591string, but i got a $=�?=f?se;�rng;�?;�
Is any sugestions how to convert iso8859-1 to windows 1257, Thanks
public static void main(String[] args)
String isoString= new String("$=�Ū=fżse;�rng;�Ż;�");
byte[] stringBytesIso;
     try
          stringBytesIso = isoString.getBytes("ISO-8859-1");
               String utf8String = new String(stringBytesIso, "windows-1257");
                    System.out.print(stringBytesIso+" "+utf8String);
     catch (UnsupportedEncodingException e) { e.printStackTrace();}
}

Were you expecting Java to magically convert "Ū" into some character?
Doesn't work that way.I agreed. What you need is a diacritic mapping. Unfortunately, there's no easy way of doing the mapping.
on solution is to have a HashMap where
key = character above 256
value=similiar character to Window ASCII extended
anything less than 256, you don't need to convert
also, looks for patterns to reduce the diacritic mapping hashmap.

File encoding in sender file comunication channel

hello everyboy,
i have a strange situation.
2 PI 7.0 installation: develop and production. Identical. Same SP level, java vm, etc etc
I have a interface file to idoc.
File sender comunication channel are FTP and with content conversion.
They are identical!!!!!!
but....
in production i added parameter File Encoding = ISO-8859-1 because if i have presence of strange characters....it work better.
the same files...in develop installation, they work without this parameter.
why?
there are a place maybe in Config Tool or j2ee admin tool where is set this parameter?
thanks in advance
Edited by: apederiva on Mar 12, 2010 3:55 PM

Hi,
Make sure your both the systems are unicode so that you will not have any issues. Also please see this document for how to work with character encodings in PI. Also we dont have any special config in j2ee admin tool.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/502991a2-45d9-2910-d99f-8aba5d79fb42?quicklink=index&overridelayout=true
Regards,
---Satish

PayloadZipBean and file encoding ISO-8859-1

Similar Messages

Maybe you are looking for