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.

Similar Messages

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

XMLReader throws "Invalid UTF8 encoding." - Need parser for ISO-8859-1 chrs

Hi,
We are facing an issue when we try to send data which is encoded in "ISO-8859-1" charset (german chars) via the EMDClient (agent), which tries to parse it using the oracle.xml.parser.v2.XMLParser . The parser, while trying to read it, is unable to determine the charset encoding of our data and assumes that the encoding is "UTF-8", and when it tries to read it, throws the :
"java.io.UTFDataFormatException: Invalid UTF8 encoding." exception.
I looked at the XMLReader's code and found that it tries to read the first 4 bytes (Byte Order Mark - BOM) to determine the encoding. It is probably expecting us to send the data where the first line is probably:
<?xml version="1.0" encoding="iso88591" ?>
But, the data that our application sends is typically as below:
========================================================
# listener.ora Network Configuration File: /ade/vivsharm_emsa2/oracle/work/listener.ora
# Generated by Oracle configuration tools.
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = semsa2)
(ORACLE_HOME = /ade/vivsharm_emsa2/oracle)
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = tcp)(HOST = stadm18.us.oracle.com)(PORT = 15100))
========================================================
the first 4 bytes in our case will be, int[] {35, 32, 108, 105} == chars {#, SPACE, l, i},
which does not match any of the encodings predefined in oracle.xml.parser.v2.XMLReader.pushXMLReader() method.
How do we ensure that the parser identifies the encoding properly and instantiates the correct parser for "ISO-8859-1"...
Should we just add the line <?xml version="1.0" encoding="iso88591" ?> at the beginning of our data?
We have tried constructing the inputstream (ByteArrayInputStream) by using String.getBytes("ISO-8859-1") and passing that to the parser, but that does not seem to work.
Please suggest.
Thanks & Regards,
Vivek.
PS: The exception we get is as below:
java.io.UTFDataFormatException: Invalid UTF8 encoding.
at oracle.xml.parser.v2.XMLUTF8Reader.checkUTF8Byte(XMLUTF8Reader.java:160)
at oracle.xml.parser.v2.XMLUTF8Reader.readUTF8Char(XMLUTF8Reader.java:187)
at oracle.xml.parser.v2.XMLUTF8Reader.fillBuffer(XMLUTF8Reader.java:120)
at oracle.xml.parser.v2.XMLByteReader.saveBuffer(XMLByteReader.java:450)
at oracle.xml.parser.v2.XMLReader.fillBuffer(XMLReader.java:2229)
at oracle.xml.parser.v2.XMLReader.tryRead(XMLReader.java:994)
at oracle.xml.parser.v2.XMLReader.scanXMLDecl(XMLReader.java:2788)
at oracle.xml.parser.v2.XMLReader.pushXMLReader(XMLReader.java:502)
at oracle.xml.parser.v2.XMLReader.pushXMLReader(XMLReader.java:205)
at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:180)
at org.xml.sax.helpers.ParserAdapter.parse(ParserAdapter.java:431)
at oracle.sysman.emSDK.emd.comm.RemoteOperationInputStream.readXML(RemoteOperationInputStream.java:363)
at oracle.sysman.emSDK.emd.comm.RemoteOperationInputStream.readHeader(RemoteOperationInputStream.java:195)
at oracle.sysman.emSDK.emd.comm.RemoteOperationInputStream.read(RemoteOperationInputStream.java:151)
at oracle.sysman.emSDK.emd.comm.EMDClient.remotePut(EMDClient.java:2075)
at oracle.sysman.emo.net.util.agent.Operation.saveFile(Operation.java:758)
at oracle.sysman.emo.net.common.WebIOHandler.saveFile(WebIOHandler.java:152)
at oracle.sysman.emo.net.common.BaseWebConfigContext.saveConfig(BaseWebConfigContext.java:505)

Vivek
Your message is not XML. I believe that the XMLParser is going to have problems with that as well. Perhaps you could wrap the message in an XML tag set and begin the document as you suggested with <?xml version="1.0" encoding="iso88591"?>.
You are correct in that the parser uses only the first 4 bytes to detect the encoding of the document. It can only determine if the document in ASCII or EPCDIC based. If it is ASCII it can detect only between UTF-8 and UTF-16. It will need the encoding attribute to recognize the ISO-8859-1 encoding.
hope this helps
tom

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

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"%>

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

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>

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

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

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.

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.

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

Help Needed: Automator Applescript for Folder Action - Encode Video

Hi !
I have created an Automator Applescript for a Folder Action to do the following:
When a new video file is moved to the target folder (i.e. Download of Vuze is done), automatically launch the Applescript Action that does the followin g(Applescripted):
1) Using "run shell script" and FFMPEG on a UNIX command line, determine Width/Height, Framerate, Bitrate
2) Calculate encoding parameters (slightly reduced bitrate, reduced Aspect etc.)
3) Using "run shell script" with ffmpeg on the command line and the calculated parameters to encode the video file
At the same time, the action is written to a log file so I know if a file is recognized, when encoding started etc.
It works fine if I save this Action as an .app, make an alias on the Desktop and drop video files on it.
It also works fine if I attach the script to a folder as a folder action and drag a video file in there.
However, when I attach the script as a folder action to the Vuze download folder, it encodes only some video files, i.e. if there was a download of 5 files, chances are good that it will not encode 1 or 2 files out of those 5.
If for example a second download finishes while the encoding for the first download is still going on, sometimes the second file starts encoding after the first encode finishes, sometimes it does not, the file does not make the log file at all, i.e. the folder action missed it or the automator action dropped it because it was still encoding. Still, sometimes it happens, sometimes not.
As I need a solution that is 100% accurate, I would like to ask if there are any ideas on how to do this better maybe? As I am not an Applescript Guru, I would need some help to know what works and what doesn't and what the syntax is.
My main idea right now:
Similar to how ffmpegX works with its "process" application, have a second script (as .app) that receives the files to be encoded from the automator action and puts them in a queue, then proceeds to encode this queue while the main automator action is free to receive the next file.
Writing this second app is quite straightforward (a modified version of my current script) but I have some questions I need help with:
1) How do I call another applescript from within an existing applescript that launches the new applescript in a new process?
2) How do I pass parameters to this new applescript?
3) In case of this "Queueing" Idea, once I called the external applescript the first time, how do I make sure when I call next time, that I don't open a second instance of this script but rather pass another queue item to the original instance to be processed?
Or in general: Is there a better way to achieve this automatic encoding solution that I have not thought about?
Alternatively:
Does anyone know how to call the "process" application that comes with the ffmpegX package with the correct parameters to use as a queueing / processing tool?
Thanks!
Joe
Message was edited by: Joe15000
Message was edited by: Joe15000

To do this, I created an Automator workflow with an Applescript snippet to change the 'media kind'.
Here is the 'Run Applescript' workflow step code:
on run {input, parameters}
          tell application "iTunes"
                    set video kind of (item 1 of input) to movie
          end tell
          return input
end run
Prior to this running, I have an 'Import Files into iTunes' workflow step.
You can switch out 'movie' with: 'TV show', 'music video', or anything in ITLibMediaItemMediaKind.
Good luck,
Glenn

How to convert back from UTF8 to ISO-8859-1 encoding?

hi,
I have a bunch of XML files which were wrongly encoded, and we lost all our accent characters.
ie: é become Ã©
so how can I recover my XML files using powershell?
so I want to change all the UTF8 ecoded characters back to the original ISO accent character
Ã© -> é
I try this:
1")
$utf8 = [System.text.Encoding]::UTF8
$utfBytes = $utf8.GetBytes("Ã©")
$isoBytes = [System.text.Encoding]::Convert($utf8, $iso, $utfBytes)
$iso.GetString($isoBytes)
but doesnt works.
so is there a way to do this in powershell?
I have to scan hundreds of files...
thanks.

You can't. UTF-8 strips all of the information from the characters so you cannot know which characters are which. If you know which characters you need to fix (requires knowing the spelling of the words) you could possible develop an matrix of
replacements. There is no simple one line method.
¯\_(ツ)_/¯

Airpot express help needed to enable wireless printing.

Hello and thanks to everyone who post on this fourm, I have read and learned alot over the past year. When I bought my Macbook last December It cam with an airport express router. At that time I has a mediocre isp and we were not able to trouble shoot the airport express so I gave up on trying to get it to work. Recently I got DSL and I am using my same linksys. I tried to hook up my airport ex tonight and again just screwed my entire internet up. I really think I will just continue to use my linksys for the net, but is there a way to run my printer downstairs through my airpot express but not use it for the web. Dont get me wrong Im sure they are good but I have spent between 10 to 15 hours reading and trying only to keep going back to linksys.
Thanks so much for all the help

The driver provided by HP doesn't work for network printing, because it bypasses the CUPS system. The only comm protocol you get is what was written into the driver - USB. Install the hpijs and ESP ghostscript driver set from:
http://www.linuxprinting.org/macosx/hpijs/
Second issue - the windows setup software enters the server queue name during setup, but we don't have that software on OS X. You need to find the queue name in the print server docs, then enter it next to IP address in OS X Printer Setup. Common queue names are L1, lp, lpt1, etc.
Wait - just remembered I downloaded that manual for someone elses's question. The queue name is lp1 (el-p-one). So in Printer Setup select IP printer > LPD, and enter IP address and that queue name.
Good luck.

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

Similar Messages

Maybe you are looking for