Changing character encoding in ps xml pub. from utf-8 to iso-8859-1

I am using xml publisher to generate a report in a pdf format, now my problem is user has entered a comment which is not supported by utf but in iso-8559-1 its working fine,
I tried to change the encoding in people code, xml doc file ,schema and xliff file but still the old formatting exist,should I change somewhere else.
Following the error i get when trying to generate pdf:"Error generating report output: (235,2309)Error occurred during the process of generating the output file from template file, XML data file, and translation XLIFF file.".The parser is not able to recognise with utf-8 encoding.

I had the same issue. I created the xml through rowset and used string substitute function and its working.
Sample:
&inXMLDoc = CreateXmlDoc("");
&ret = &inXMLDoc.CopyRowset(&rsHdr);
&sXMLString = &inXMLDoc.GenFormattedXmlString();
&sXMLString = Substitute(&sXMLString, "<?xml version=""1.0""?>", "<?xml version=""1.0"" encoding=""ISO-8859-1""?>");
hope this helps!
GN.

Similar Messages

Mail Sender - Encoding (I need to change from UTF-8 to ISO-8859-1)

Hi,
I'm getting data from email (in ms exchange) using the Mail Sender Adapter.
In the e-mails exists characters as ç (ccedil), ã (atilde), õ (otilde) and others. The XI cannot read this characters because the encode in XML is UTF-8.
How I do to change the encode in XI from UTF-8 to ISO-8859-1 ?
Thank you!

Unfortunately most mail server do not apply the codepage to the content type of a mail.
In this case you have to set the content type with help of the MessageTransformBean:
Transform.ContentType text/plain;charset="ISO-8859-1"
Regards
Stefan

HTTP-Receiver: Code page conversion error from UTF-8 to ISO-8859-1

Hello experts,
In one of our interfaces we are using the payload manipulation of the HTTP receiver channel to change the payload code page from UTF-8 to ISO-8859-1. And from time to time we are facing the following error:
u201CCode page conversion error UTF-8 from system code page to code page ISO-8859-1u201D
Iu2019m quite sure that this error occurs because of non-ISO-8859-1 characters in the processed message. And here comes my question:
Is it possible to change the error behaviour of the code page converter, so that the error will be ignored?
Perhaps the converter could replace the disruptive character with e.g. u201C#u201D?
Thank you in advance.
Best regards,
Thomas

Hello.
I'm not 100% sure if this will help, but it's a good Reading material on the subject (:
[How to Work with Character Encodings in Process Integration (NW7.0)|http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/502991a2-45d9-2910-d99f-8aba5d79fb42]
The part of the XSLT / Java mapping might come in handy in your situation.
you can check for problematic chars in the code.
Good luck,
Imanuel Rahamim.

Changing the xml encoding from UTF-8 to ISO-8859-1

Hi,
I have created an xml file in xMII transaction that I feed into a webservice as input. As of now, the data in the xml file is entirely english text (it would be changing to have European text soon). I gave the encoding as UTF-8.
I get an error on the webservice side(not xMII code) that the its not able to parse. The error is 'SaxParseException: Invalid 1 of 1-byte UTF-8 sequence). I know that an easy fix is if tI change the encoding to iso-8859-1.
But the reference document doesnot let me put anythign other than UTF-8. Even if I put <?xml version="1.0" encoding="iso-8859-1"?> as the first line, when I save it and open it back, i see <?xml version="1.0" encoding="UTF-8"?>
Is there any way to change the encoding? Or better still, anyway idea why this invalid sequence is coming from?
Thanks,
Ravi.

Hi Ravi,
We have encountered scenarios where we needed to take the <?xml version="1.0" encoding="UTF-8"?> out completely. As xMII was providing the Web Service, it needed a workaround.
In your case, it seems that you wish to pass it from xMII to an external Web Service provider. One option might be to pass the XML document as string.
Once you convert it to a string, it may escape all XMl characters (i.e. '<' into '<'). You could perform a string manipulation and remove the <?xml version="1.0" encoding="UTF-8"?> from the string. You may also need to play around with xmlDecode( string ) function in the Link Editor.
I would suggest that before you try this option, create a string variable will the contents, but without the <?xml version="1.0" encoding="UTF-8"?> and try assigning it to the input.
You may also wish to try a string variable that has <?xml version="1.0" encoding="iso-8859-1"?> as the first line. If this works, you should be able to perform string manipulations to convert your XML document into this modified string.
Cheers,
Jai.

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

Change encoding from utf-8 to ISO-8859-1

Hi
I have a problem with changeing the encoding of a text. The text is in utf-8, but when I try to send the text as mail with javax.mail and "text/html", Outlook doesn't want to display the right characters. Can somebody help me?

Hi,
String s = java.net.URLEncoder.encode(myText, newencoding)
http://galileo.spaceports.com/~ibidris/

Change encoding from utf-8 to iso-8859-1 in JMS receiver!

Hi.
I have some problems regarding encoding.
The simple setup: dummy datatype as input, XSLT mapping and standard XI output(to JMS).
Are there any way to tell the JMS adapter to deliver the message in iso-8859-1 and not utf-8?
Regards Peter

> Hi Henrique.
>
> This sounds like an idea. Can you guide me to some
> documentation, that describes adding mapping in the
> jms adapter module?
>
> Regards Peter
To use modules in JMS adapter: http://help.sap.com/saphelp_nw2004s/helpdata/en/0f/80243b4a66ae0ce10000000a11402f/frameset.htm
Now, you add the MessageTransforBean module, to use the XSLT mapping. Check the end of this blog to learn how to use XSLT mapping on MessageTransformBean: /people/michal.krawczyk2/blog/2005/11/01/xi-xml-node-into-a-string-with-graphical-mapping
Regards,
Henrique.

Changing charset from UTF-8 to iso-8859-1

Hi,
I am deploying my web service in Weblogic Server 9.2.2.
The result is returned using encoding "UTF-8". How can I
alter this so that the result wil be returned using encoding "iso-8859-1"? Could some one help please?
Thanks in advacne
Mike

What's the source of the "generated content"? I think you'd be better off investigating how to get that source to generate UTF-8 content.
Changing the meta tag won't give you what you want, because it will cause all the accented characters (and anything else outside ASCII) that are entered directly in Muse to be handled incorrectly by the browser.

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

Switching from "UTF-8" to "ISO-8859-1"

Dear all,
I am using Designer 7.0 to create forms, where the content is sent back via eMail and, after review, imported to a wepage.
Due to multiple languages on the site, encoding="ISO-8859-1" is mandatory.
Unfortunately I am not able to generate a PDF which sends back data in xml-format in this encoding ... it is always "UTF-8" !?!
I tried to edit the xml source of the form directly but without any effect. May feeling is, that the whole form has to be saved in the ISO encoding but I don't know where to select this !
Any help greatly appreciated. Thanks in advance. Stefan.

XML files are almost always in UTF-8. Other encodings are not
recommended; most software only supports UTF-8 or UCS-2. So it seems
very unlikely Designer would have such an options.
Aandi Inston

XML Encoding Issue - Format UTF-16 to ISO-8859-1

Dear Groupmates,
I have data in my Internal table which i am converting to XML using custom Transformation.
Data is going to third party.The third party system requires data in ISO-8859-1 Format but SAP is generating the same in UTF-16 Format.I have been able to change the format of file from
utf-16 to ISO-8859-1 format but after conversion i am getting invalid tag information in form of characters
like &lt , &gt etc..in my file.
Here is the code i have used to set the encoding to ISO-8859-1 :-
DATA: xmlout TYPE xstring.
DATA: ixml TYPE REF TO if_ixml,
streamfactory TYPE REF TO if_ixml_stream_factory,
encoding TYPE REF TO if_ixml_encoding,
ixml_ostream TYPE REF TO if_ixml_ostream.
ixml = cl_ixml=>create( ).
streamfactory = ixml->create_stream_factory( ).
ixml_ostream = streamfactory->create_ostream_xstring( xmlout ).
encoding = ixml->create_encoding(
character_set = 'ISO-8859-1' byte_order = 0 ).
ixml_ostream->set_encoding( encoding = encoding ).
Sample Output :-
<?xml version="1.0" encoding="iso-8859-1"?>
<AMS_DOC_XML_EXPORT_FILE><AMS_DOCUMENT AUTO_DOC_NUM="FALSE" DOC_CAT="CA" DOC_CD="CA" DOC_DEPT_CD="045" DOC_ID="XR10281060830400001" DOC_IMPORT_MODE="OE" DOC_TYP="CH" DOC_UNIT_CD ="NULL" DOC_VERS_NO="01">
<CH_DOC_HDR AMSDataObject="Y">
<DOC_CAT Attribute="Y"><![CDATA[CA]]></DOC_CAT>
<DOC_TYP Attribute="Y"><![CDATA[CH]]></DOC_TYP>
Please let me know if anyone has idea how i can get rid of the invalid tag information.
Thanks !
With Regards,
Darshan Mulmule

Darshan,
Did you get an answer for this question? We have same requirement to create XML file in ISO-8859-1 format with Attributes is set to "Y" and CDATA is being used for data.
Can you please let me know if you still remember how did you achieve it?
Satyen...

Creating XML-files in ABAP with format ISO-8859-1 after the use of unicode

Hello,
We have a problem with XML-files created in z_abap-programma.
Before the use of unicode the XML-file was of the format: ISO-8859-1.
After the introducting of unicode the format is UTF-16.
In the abap-program we are using:
        CALL TRANSFORMATION xls-program
         SOURCE t_vbak = it_vbak
         RESULT XML xmlstring.
        CALL FUNCTION 'SCMS_STRING_TO_XSTRING'
          EXPORTING
            text     = xmlstring
          IMPORTING
            buffer   = lx_xml_as_string.
        CALL FUNCTION 'SCMS_XSTRING_TO_BINARY'
          EXPORTING
            buffer        = lx_xml_as_string
          IMPORTING
            output_length = li_xml_size
          TABLES
            binary_tab    = ltb_xml_table.
        CALL METHOD cl_gui_frontend_services=>gui_download
          EXPORTING
            bin_filesize = li_xml_size
            filename     = lc_filename
            filetype     = 'BIN'
          CHANGING
            data_tab     = ltb_xml_table
          EXCEPTIONS
            OTHERS       = 24.
Is it prossible to create the XML-file with the format ISO-8859-1 after the unicode, please can you explane how to solve this problem.
Regards,
Theo Pijlman

hi theo,
did you read my thread i wrote some days before ? have a look in my sample coding find   " if_ixml_encoding ..... " there you can set the encoding of character .
greetz
tony
thread:
Re: abap to xml
SAP Explanation for Interface if_ixml_encoding :
http://help.sap.com/saphelp_nw04/helpdata/de/bb/5766a6dca511d4990b00508b6b8b11/content.htm

Codepage coverting error utf-8 from System codepage to iso-8859-1 (PI 7.1)

Hello Experts,
In our Prcess, we receive an Idoc from an IS-U system and then we send this Idoc with some Header-Information via http-Adapter to a Seeburger System.
In the outbound communication Channel we have a XI Payload manipulation with xml-Code iso-8859-1.
We get the Error: Codepage coverting error utf-8 from System codepage to iso-8859-1, and only for this Idoc, where othe similar Idocs runs correctly.
Is it possible, that the Idoc contains non-utf-8 chars so the error occurs?
PS: another XI in our landscape uses a http-Channel with the same configuration in a similar process, an it work, so guess the Problem is not in the communication channel.
thanks,
best regards

> Is it possible, that the Idoc contains non-utf-8 chars so the error occurs?
A would rather think, that there could be any non-iso-8859-1 character be in the IDoc. For example an czech or polish character.

Changing the encoding attribute in xml output

We are creating an xml file using:
vc_string_clob := dbms_xmlgen.getxml('select * from mytable');
then opening the file with UTL_FILE.FOPEN('dir','filename','W',31767)
then parsing through vc_string_clob and using UTL_FILE.PUT_LINE to write to the file.
This all works fine, expect the header of the XML file is <?xml version="1.0"?> and our users need it to be <?xml version="1.0" encoding="ISO-8859-1"?>
Is there a function within dbms_xmlgen that will allow me to change this?
I'm thinking I can use brute force to change it, but I'm sure there is a 'more correct' way to go about it.
Thank you,
Jill Jacomine

Hi Jill,
Welcome to the forum.
There are easier methods to output XML to a file, rather than using line-by-line UTL_FILE operations.
For example :
DECLARE
xml_result xmltype;
doc        dbms_xmldom.DOMDocument;
BEGIN
xml_result := dbms_xmlgen.getXMLType('SELECT * FROM scott.dept');
doc := dbms_xmldom.newDOMDocument(xml_result);
dbms_xmldom.writeToFile(doc, 'TEST_DIR/my_file.xml', 'ISO-8859-1');
dbms_xmldom.freeDocument(doc);
END;
/or,
DECLARE
xml_result xmltype;
xml_prolog clob := '<?xml version="1.0" encoding="ISO-8859-1"?>'||chr(10);
BEGIN
xml_result := dbms_xmlgen.getXMLType('SELECT * FROM scott.dept');
dbms_xslprocessor.clob2file(xml_prolog || xml_result.getClobVal(), 'TEST_DIR', 'my_file.xml');
END;
/Both will produce :
<?xml version="1.0" encoding="ISO-8859-1"?>
<ROWSET>
<ROW>
    <DEPTNO>10</DEPTNO>
    <DNAME>ACCOUNTING</DNAME>
    <LOC>NEW YORK</LOC>
</ROW>
<ROW>
    <DEPTNO>20</DEPTNO>
    <DNAME>RESEARCH</DNAME>
    <LOC>DALLAS</LOC>
</ROW>
<ROW>
    <DEPTNO>30</DEPTNO>
    <DNAME>SALES</DNAME>
    <LOC>CHICAGO</LOC>
</ROW>
<ROW>
    <DEPTNO>40</DEPTNO>
    <DNAME>OPERATIONS</DNAME>
    <LOC>BOSTON</LOC>
</ROW>
</ROWSET>Hope that helps.

Changing character encoding

Hi,
I have a procedure in my database that produces a .csv-output for Excel.
Using http headers I get Excel to open the "file" produced.
My problem is our swedish characters, åäö.
Excel (at least Excel 2003) wants iso-8859-1 encoding for these characters to work.
So my procedure uses convert() to go from database charset UTF8 to WE8ISO8859P1.
This worked fine under Oracle Portal but not so under Apex Listener on WebLogic.
I think the listener is converting my iso text to utf on the way to the browser.
Is this so?
I've read that it "defaults to utf8" and "bound to utf8" but nothing official.
My listener version is 1.1.3.243.11.40
Kind regards
Tomas

Hi Tomas,
I'm sorry it took some time to prepare an answer for you...
Excel (at least Excel 2003) wants iso-8859-1 encodingThis hasn't changed with 2007 as far as I've experienced it - it still doesn't like UTF-8 in CSV files unless you use the import function.
So my procedure uses convert() to go from database charset UTF8 to WE8ISO8859P1.I've experimented a lot on that issue. If you ever have to deal with EURO signs (and a few other specialities) I'd consider WE8ISO8859P15.
Anyway, since you say you use a procedure, I assume you aren't using the APEX standard CSV function for export, right? We had similar issues with UTF8-Character sets on OHS, but no problems with standard CSV export on APEX Listener (we received ANSI file encoding as requested by the client) so I came to the conclusion this is not an APEX Listener specific issue, but has to be something in the way we build our custom export process using htp.p and owa_util.
I'm not familiar with Portal and APEX, but I assume that Portal uses mod_plsql and set PlsqlNLSLanguage to a Windows charset, e.g. AMERICAN_AMERICA.WE8MSWIN1252 or even your local territory. I guess this affects the output stream handling, but it's not the recommended way to run APEX. Since APEX has been "renamed" from HTMLDB to APEX, the installation guide requires AL32UTF8 as NLSLanguage parameter, and this is what the APEX Listener enforces by not giving you any option on that. But as I said before, we had the same problems with exports on OHS, so we sometimes ignored the installation guide to get proper files.
Without that option, there is one option that definetly works and one that might work, but I haven't implemented it (yet). So I start with the working one: Prepare a blob and download it as complete file using WPG_DOCLOAD. I'm not sure, but I guess the APEX standard export performs a similar operation. An additional advantage of that approach is the fact that you get proper filesize information when the download starts, so progress and time estimation is accurate...
I implemented the following procedure for the generic export (download) part:
PROCEDURE csv_export (in_clob IN CLOB, in_filename IN VARCHAR2, in_charset IN VARCHAR2 DEFAULT 'WE8MSWIN1252')
AS
    l_blob           BLOB;
    l_length         INTEGER;
    l_dest_offset    INTEGER := 1;
    l_src_offset     INTEGER := 1;
    l_lang_context   INTEGER := DBMS_LOB.DEFAULT_LANG_CTX;
    l_warning        INTEGER;
BEGIN
    -- create new temporary BLOB
    DBMS_LOB.createtemporary(l_blob, FALSE);
    -- tranform the input CLOB into a BLOB of the desired charset
    /** @TODO: check whether lang_context should be an additional parameter
     ** the DBMS_LOB documentation doesn't say much about that parameter
    DBMS_LOB.convertToBlob( dest_lob     => l_blob,
                            src_clob     => in_clob,
                            amount       => DBMS_LOB.LOBMAXSIZE,
                            dest_offset => l_dest_offset,
                            src_offset   => l_src_offset,
                            blob_csid    => nls_charset_id(in_charset),
                            lang_context => l_lang_context,
                            warning      => l_warning);
    -- determine length for header
    l_length := DBMS_LOB.getlength(l_blob);
    -- create response header
    OWA_UTIL.mime_header('text/comma-separated-values', false);
    htp.p('Content-length: ' || l_length);
    htp.p('Content-Disposition: attachment; filename="'||in_filename||'"');
    -- close the headers
    OWA_UTIL.http_header_close;
    -- download the BLOB
    WPG_DOCLOAD.download_file( l_blob );
    -- release BLOB from memory
    DBMS_LOB.freetemporary(l_blob);
EXCEPTION
    WHEN OTHERS THEN
      DBMS_LOB.freetemporary(l_blob);
      RAISE;
END csv_export;To use this in your procedure, you need to do the following
DECLARE
-- other variables here
l_clob CLOB;
BEGIN
-- create new temporary CLOB
DBMS_LOB.createtemporary(l_clob, FALSE);
-- loop to prepare your content - just an example
-- use the one you use right now for streaming with htp.p
-- and replace the htp.p with the append
FOR a in 1..10
LOOP
    DBMS_LOB.append(dest_lob => l_clob, src_lob => 'any_VARCHAR2_or_CLOB_content_or_variable');
END LOOP;
-- perform actual export/download
csv_export(in_clob => l_clob, in_filename => yourfilename.csv);
-- stop any other rendering unless you want that, e.g. for a confirmation or something similar
apex_application.g_unrecoverable_error := true;
-- release BLOB from memory
    DBMS_LOB.freetemporary(l_clob);
EXCEPTION
    WHEN OTHERS THEN
      DBMS_LOB.freetemporary(l_clob);
      RAISE;
END;Adapt that example as needed.
If you need streaming for some reason, you should start some research on HTP.PUTRAW and the surrounding procedures for setting transferencoding and headers to fit to that mode. It should work as well, but I don't like the 2000 bytes size limit that comes along with RAW and I knew the BLOB-approach works for proper downloads...
I hope this helps you solve your problem.
-Udo

Changing character encoding in ps xml pub. from utf-8 to iso-8859-1

Similar Messages

Maybe you are looking for