UTF-8 encoding vs ISO 8859-1 encoding

The iTunes tech specs call for UTF-8 encoding of the XML feed file; a friend of mine uses feed generator software through his blog that uses ISO 8859 encoding. Is there a way to convert the latter to UTF-8 so that iTunes tags may be successfully added?
When I tried editing his XML file, I got error messages when I submitted the file to RSS feed validator sites (such as http://feedvalidator.org/. Any help or knowledge is appreciated because I am not the least bit expert in this coding arena.

You don't need to convert iso 8859-1 (us-ascii) to utf-8 unless you have nonstandard characters. Basically, ascii is a subset of utf-8 and for English it will serve you just fine. You can have iTunes tags in the xml file even if the file itself is encoded in iso 8859-1.
The error you see at feedvalidator.org is most likely a warning.
Hope this helps!
- Andy Kim
Potion Factory
http://www.potionfactory.com

Similar Messages

WSDL Generating in ISO-8859-1 encoding want in UTF - 8

Hi XI Geeks,
       When I am using "Define Web Service" tool in Integration Directory, the WSDL file is being created with encoding <b>ISO-8859-1</b>, <i><b>but we want in "UTF-8"</b></i>.
        Is there any setting we need to change in WAS which will change this default.
Any ideas are welcome and thanks in advance.
Regards
Sujan

Hi Vishnu,
         We already did that for the time being. But the client wants it be consistent.
         In another client engagement the WSDL is created in "UTF-8" format we double checked twice.
         We are running on SP12.
If any of the SP12 guys can generated a WSDL and let us know that it is created in "ISO-8859-1" encoding.
Regards
Sujan

How to store UTF-8 characters in an iso-8859-1 encoded oracle database?

How can we store UTF-8 characters in an iso-8859-1 encoded oracle database? We can NOT change the database encoding but need to store e.g. Polish or Russian characters besides other European languages.
Is there any stable sollution with good performance?
We use Oracle 8.1.6 with iso-8859-1 encoding, Bea WebLogic 7.0, JDK 1.3.1 and the following thin driver: "Oracle JDBC Driver version - 9.0.2.0.0".

There are a couple of unsupported options, but I wouldn't consider using them on a production database running other critical applications. I would also strongly discourage their use unless you understand in detail how Oracle National Language Support (NLS) works, otherwise you could end up with corrupt data or worse.
In a sense, you've been asked to do the impossible. The existing databas echaracter sets do not support encoding the data you've been asked to store.
Can you create a new database with an appropriate database character set and deploy your application there? That's probably the easiest solution.
If that isn't an option, and you really need to store data in this database, you could use one of the binary data types (RAW and BLOB), but that would mean that it would be exceptionally difficult for applications other than yours to extract the data. You would have to ensure that the data was always encoded in the same character set, otherwise you wouldn't be able to properly decode it later. This would also add a lot of complexity to your application, since you couldn't send or recieve string data from the database.
Unfortunately, I suspect you will have to choose from a list of bad options.
Justin
Distributed Database Consulting, Inc.
http://www.ddbcinc.com/askDDBC

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>

Java App on Linux : Unable to read iso-8859-1 encoded file correctly.

I have a file which is encoded as iso-8859-1, and contains characters such as ô .
I am reading this file with java code, something like:
File in = new File("myfile.csv");
InputStream fr = new FileInputStream(in);
byte[] buffer = new byte[4096];
while (true) {
int byteCount = fr.read(buffer, 0, buffer.length);
if (byteCount <= 0) {
break;
String s = new String(buffer, 0, byteCount,"ISO-8859-1");
System.out.println(s);
However the ô character is always garbled, usually printing as a ? .
I am running this on a Linux machine. It works fine on my XP machine.
I have verified that I can see the correct characters when I cat the file on the terminal.
(Interestingly, but I think maybe only by co-incidence, it works when I run with the -Dfile.encoding=UTF16 option, but not with UTF8, although this appears a hack rather than a fix since this option was not intended for developer use by sun - but I thought mentioning it may provide some clues as to what is going on)

I think your main probelm is with the console. When you send text to the console, it's sent in the system default encoding. On an English-locale system that might be ASCII, ISO-8859-1, windows-1252, UTF-8, MacRoman, and probably several other possibilities. Then the console decodes the the bytes using whatever encoding it feels like using--on my WinXP machine, it uses cp437 by default (just for laughs, as far as I can tell). If the text happens to be pure, seven-bit ASCII, there's no problem, since all those encodings are identical in that range.
But if you need to output anything other than ASCII characters, avoid the console. Send the output to a file and specify an encoding that you know will be able to handle your characters--UTF-8 can handle anything. Then open the file with an editor that can read that encoding; most of them can handle UTF-8 these days, and many will even detect it automatically. You also need to be using a font that can display your characters.
However, you're also going about the reading part wrong. Instead of reading the text in as bytes and passing them to a String constructor, you should use an InputStreamReader and read it as text from the beginning: BufferedReader br = new BufferedReader(
new InputStreamReader(
new FileInputStream("myfile.csv"), "ISO-8859-1"));I am curious about your statement that "it works" when you run with the -Dfile.encoding=UTF16 option. I wouldn't be surprised to see it output the correct characters (ASCII characters, anyway), but I would expect to see the characters interspersed with blank spaces or rectangles.

Setting ISO-8859-1 Encoding in AXIS RPC call

As per my understanding UTF-8 is default for webservice call in AXIS implementation I may be wrong.
Is there any way to set ISO-8859-1 encoding in AXIS RPC call?
Below is the WSDL file details.
Thanks for you help.
Regards,
Hemen
<Code>
<?xml version="1.0" encoding="ISO-8859-1"?>
<definitions name="TestService_Service"
targetNamespace="http://webservice.de.rt.wsdl.WebContent/TestService_Service/"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:format="http://schemas.xmlsoap.org/wsdl/formatbinding/"
xmlns:java="http://schemas.xmlsoap.org/wsdl/java/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:tns="http://webservice.de.rt.wsdl.WebContent/TestService_Service/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<message name="getResponseRequest">
<part name="xml" type="xsd:string"/>
<part name="product" type="xsd:string"/>
<part name="source" type="xsd:string"/>
<part name="tran" type="xsd:string"/>
<part name="content" type="xsd:string"/>
</message>
<message name="getResponseResponse">
<part name="return" type="xsd:string"/>
</message>
<portType name="TestService">
<operation name="getResponse" parameterOrder="xml product source tran content">
<input message="tns:getResponseRequest" name="getResponseRequest"/>
<output message="tns:getResponseResponse" name="getResponseResponse"/>
</operation>
</portType>
<binding name="TestServiceJavaBinding" type="tns:TestService">
<java:binding/>
<format:typeMapping encoding="Java" style="Java">
<format:typeMap formatType="java.lang.String" typeName="xsd:string"/>
</format:typeMapping>
<operation name="getResponse">
<java:operation methodName="getResponse"
parameterOrder="xml product source tran content" returnPart="return"/>
<input name="getResponseRequest"/>
<output name="getResponseResponse"/>
</operation>
</binding>
<binding name="TestServiceBinding" type="tns:TestService">
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="getResponse">
<soap:operation soapAction="" style="rpc"/>
<input name="getResponseRequest">
<soap:body
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
namespace="distributionengine.com"
parts="xml product source tran content" use="encoded"/>
</input>
<output name="getResponseResponse">
<soap:body
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
namespace="distributionengine.com" use="encoded"/>
</output>
</operation>
</binding>
<service name="TestServiceService">
<port binding="tns:TestServiceJavaBinding" name="TestServiceJavaPort">
<java:address className="rt.de.webservice.TestService"/>
</port>
</service>
<service name="TestService_Service">
<port binding="tns:TestServiceBinding" name="TestServicePort">
<soap:address location="http://localhost:9080/servlet/rpcrouter"/>
</port>
</service>
</definitions>
</code>

try to put the below code at the top of the JSP page
<%@ page language="java" pageEncoding="UTF-8"%>

Help needed to enable ISO-8859-1 encoding in Weblogic 10.3

We have upgraded from Weblogic 10 to Weblogic 10.3. In the old environment foreign characters (iso-8859-1 charater set) were enabled using the Java properties "*-Dfile.encoding=iso-8859-1 -Dclient.encoding.override=iso-8859-1*".
Also, we set the page encoding in the JSPs to be
_'<%@ page pageEncoding="iso-8859-1" contentType="text/html; charset=iso-8859-1" %>'._
This was working fine. We were able to input characters like euro (€) and display it back to user.
After we upgraded to Weblogic 10.3, I applied the same Java properties, all the special characters of the 8859-1 set like Æ, Ã etc are just displayed as garbled text like 'ï¿½ï¿½ï' etc. So, the new server is unable to handle/encode these characters.
Our weblogic environment is - Weblogic appserver 10.3, JRockit 1.6.0_31-R28.2.3-4.1.0 running on Linux OS.
Is there any additional seting in 10.3 to encode character sets?
Thanks in advance.

Hi Kalyan,
Thanks for the info. Please help me understand just one more thing, before I ask our server team to apply the patch.
I checked the full version of our Weblogic server from WEBLOGIC_HOME/registry.xml. It is *<component name="WebLogic Server" version="10.3.6.0" >*.
The patch from MOS says it is *"Release WLS 10.3.3"*. Does this mean the version 10.3.6 should already have this patch? Is the release of Patch same as WLS version?
Should I still go ahead and install the patch for this version 10.3.6 also?
Thanks again.
- Shankar.

Convert a UTF-8 string to ISO-8859-1 string

Hello. As you can see from my other post, I am working on internationalization. I could not find an appropriate entry in the forum already.
I want to convert form data (submitted from an HTML UTF-8 charset page) from the UTF-8 format to ISO-8859-1 format. How do I do that?
I.e.
String utfFormat="視聴者";
String isoFormat="";
// Do magic here
System.out.println(isoFormat); // out: "しての" (or whatever it is)
Can you help?
Dailysun
null

As I said in the other thread (did you read that, BTW?), you shouldn't have to bother with actual character-set conversions. You just tell the InputStream what the Charset is when you read it in, and the OutputStream what Charset to use when you write it out.
What you're doing is escaping characters by replacing them with numeric entity references--the opposite of what you asked in the other thread. The process is just as simple: cast the char to an int, convert that to a string with String.valueOf(int), and add the "&#" and ";". You can use a regex-based approach like I did over there, but going in this direction, it will be just as easy without them.
Hiwa, check out that other thread; I think you'll find it amusing (in light of that second link you posted).

Convert from ISO 8859-1 encoding to UTF-8

Hi
My Os name is 'SunOS ut51109 5.10 Generic_144500-19 sun4v sparc SUNW,T5440'.
I want to change the encoding of the existing .bcp file from ISO 8859-1 to UTF-8 with out using any temp files as these .bcp file will be pointed by an external table.
here is the command I issued in the script(ksh file)
iconv -f ISO8859-1 -t UTF-8 file1.bcp > file1.bcp
After the script got executed file1 is empty(showing 0 bytes).
Please correct me or let me know the syntax to be followed to write the data into the same file in UTF-8 format.
Thanks
kartheek

You cannot do conversion from ISO 8859-1 to UTF-8 in-place because the UTF-8 version will generally be longer (unless you convert a pure ASCII file, which does not need conversion in the first place). Therefore, you would have to overwrite what you have not read yet. Instead, convert to a new file with a temporary name, drop the original and rename the temporary back to original. This is not that complicated.
If the problem is that you want to overwrite a file already open by the database, then rename the incoming file first and then convert copying to the target.
-- Sergiusz

Default UTF-8 encode to Iso-8859-1 How to?

Excused my English, I have a problem with JCreator 2 early access, when, in JSP page, change encode it from Utf-8 to Iso-8859-1 JCreator of default restores to Utf-8, as I can make? I cannot use Italian chars as "� "
Thanks to who will want to help me.

Hi,
Please post the queries related to creator 2EA to the creator 2 EA discussion at https://feedbackprograms.sun.com/login.html
regards

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

Problem when setting encoding to ISO-8859-1

Hi. Is there something I'm missing when it comes to setting
encoding? Here are the code in the mxml:
<?xml version="1.0" encoding="ISO-8859-1"?>
<mx:Application xmlns:mx="
http://www.adobe.com/2006/mxml"
layout="absolute">
</Application>
In the html-template I'm setting:
<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1" />
The code for sending data from the app:
<mx:HTTPService
id="service"
url="encoding.jsp"
method="post"
showBusyCursor="true"
result="onResult(event)"
resultFormat="xml"
contentType="application/xml"
fault="onFault(event)"
useProxy="false" />
public function send():void {
var xml:XML = <Data>{data.text}</Data>;
service.send(xml);
But still the respons jsp I have made says it receives the
data in UTF-8 format? What am I doing wrong?
Servercode:
don't work: BufferedReader reader = new BufferedReader( new
InputStreamReader( is ) );
work: BufferedReader reader = new BufferedReader( new
InputStreamReader( is, "UTF-8") );

Are there no-one who have the same problem? I've tried
everything imaginable, and still the serverside receives the data
as UTF-8.
Is it supported at all to set the encoding of the
request?

Flat file transformation to xml with encoding in iso-8859-1

We have a BPEL process that picks up a flat fle (fixed length), transforms it to xml and emails it. The flat file is in iso-8859-1 (when I look at special characters like e-accent's in hex).
The basic transformation that you get from (the wizards) of BPEL don't do the trick, the special characters are corrupted and unreadable.
After that I changed all the encoding's (in xsd's and xsl's) from utf-8 into iso-8859-1 but doesn't help either. I also added an xsl:output section to my xsl (with "encoding="iso-8859-1") but that also fails...
Does anyone have a clue? We're using SOA Suite 10.1.3.1.
greetings,
Jan

just tried that but the problem is still there
I suspect that the output of the file adapter (reading the flat file) is already corrupted, you should be able to tell the file adapter what encoding the input file is...

Oracle Service Bus to IBM MQ v7.0 Integration Issue ISO-8859-1 Encoding

Hi,
This is the issue we badly struggling with for a few days..
I"ve a MQ proxy service listening to MQ REQUEST queue and when message is arrived to proxy, do some service callouts to local protcol proxy services and reply back to MQ REPLY queue on the same Listener Proxy. This is working good without any issues.
However, when I want to route reply through MQ business service, the message is going to *MQ reply queue with encoding="ISO-8859-1*". but expected requirement is to publish a message *with encoding="UTF-8"* which I'm not able to do. Hence MQ is rejecting the message.
Working path: MQ <--> MQ proxy <-->DynamicRouting<-->Local Proxy
*NOT Working Path: REQUEST MQ --> MQ proxy -->DynamicRouting -->Response Route Line -->For Loop -->Publish-->MQ Business Service-->REPLY MQ*
Transport Headers I'm passing to Outbound Request: mq:putApplicationName, mq:Format
MQ v7.0
OSB v11.1.1.5
Could you please help and guide me where I'm wrong and which property I need to set explicitly to achieve this.
Thank you
Edited by: 1002815 on May 2, 2013 10:51 AM

Here is a simple Answer:
In MQ Transport Headers, set mq:characterset to '1208' (UTF8) and Check 'Pass all headers". That's itThanks for sharing it here with the community. Would you mind closing this thread as well?
Regards,
Anuj

Encoding Characters ISO-8859-2

You say:
You need to set your $ORACLE_HOME environment variable point to the database of interest.
I mean:
We work under WinNT(SP4) with MS DevStudio 6.0. What can I do to encoding Character ?
I put line <?xml version="1.0" encoding="ISO-8859-2"?> in the XML-Header, but the oracle-parser say ' LPX-00201 '.
Help, I need somebody help ? Thanks Matthias

I've found a solution. Yes, the problem was, when I've written polish characters into Excel file it encoded them as a rubbish. The problem was, I didn't set the cell encodding. So my code after I've fixed the problem looks like:
HSSFCell cell = row.createCell((short)0);
// And below is the line I was looking for
cell.setEncoding(HSSFCell.ENCODING_UTF_16);
cell.setCellValue("Some text with polish characters");
Now it works great. Thanks anyway.

UTF-8 encoding vs ISO 8859-1 encoding

Similar Messages

Maybe you are looking for