Charset ISO-8859-5

I am trying to convert ASCII to ISO-8859-5.
For it I should add new Charset to CharsetProvider.
What I do:
1. create file java.nio.charser.spi.CharsetProvider in META-INF\services ( in \jre\lib\rt.jar file );
2. there:
sun.io.ByteToCharISO8859_5
sun.io.CharToByteISO8859_5
3. I try simple converting:
String str = new String( b, "ISO-8859-5" );
error:
java.lang.ClassCastExeption: sun.io.ByteToCharISO8859_5
BTW, I try that too:
Charset charset = Charset.forName("ISO-8859-5");
CharsetDecoder decoder = charset.newDecoder();
same error.
Any ideas, tips, or help would be greatly appreciated.
Thanks very much!
Hill

Hi,
Why do u want to add it to the CharsetProvider.
I feel there is no need for that.
You can just achieve this by following lines of code:
String ascii = "hsgfjg";
byte[] byt = null;
byt = ascii.getBytes("iso-8859-5");
String strISO-8859-5 = new String(byt);
I guess this shoulf answer your problem
Thanks & regards
Paritosh Wechalekar
Software Engineer
L&T Infotech Ltd
& Chief Controller
International Mathematics Consortium

Similar Messages

  • Unsupported Content-Type: text/html; charset=iso-8859-1

    Originally posted on JBI forum -
    It was helpfully suggested there that I check on JAX-WS forum whether this was an issue with utf-8/16 encodings...
    I have been experimenting with the openESB composite application described here
    http://jlorenzen.blogspot.com/2007/08/using-jbi-javaee-serviceengine.html
    This works fine as it appears on this webpage.
    I have tried to adapt it to act as a proxy to a secure version of Hello EJB that runs on the SSL port of glassfish AS.
    To do this I edited the EJB to set up the security properties. Edited the BPEL wsdl file and created a new composite application using the updated BPEL project.
    This leads to an Unsupported Content-Type exception when a test case is run on the composite application from SOAP-UI
    Does anyone know how I can explicitly set the content type of the proxied request to the secure WS?
    Thanks
    Joss Armstrong
    HTTPBC-E00720: Provider for service [{http://j2ee.netbeans.org/wsdl/HelloBPEL}HelloBPELService] endpoint [HelloBPELPort] responded with an error status. Error detail is: BPCOR-6135:A fault was not handled in the process scope; Fault Name is {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is <?xml version="1.0" encoding="UTF-8"?><jbi:message xmlns:sxeh="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling" type="sxeh:faultMessage" version="1.0" xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"><jbi:part>Unsupported Content-Type: text/html; charset=iso-8859-1 Supported ones are: [text/xml]</jbi:part></jbi:message>. Sending errors for the pending requests in the process scope before terminating the process instance
    BPCOR-6151:The process instance has been terminated because a fault was not handled; Fault Name is {http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling}systemFault; Fault Data is <?xml version="1.0" encoding="UTF-8"?><jbi:message xmlns:sxeh="http://www.sun.com/wsbpel/2.0/process/executable/SUNExtension/ErrorHandling" type="sxeh:faultMessage" version="1.0" xmlns:jbi="http://java.sun.com/xml/ns/jbi/wsdl-11-wrapper"><jbi:part>Unsupported Content-Type: text/html; charset=iso-8859-1 Supported ones are: [text/xml]</jbi:part></jbi:message>
    com.sun.jbi.engine.bpel.core.bpel.exception.SystemException: BPCOR-6131:An Error status was received while doing an invoke (partnerLink=EJBPartnerLink, portType={http://hellopack/}Hello, operation=sayHello)
    BPCOR-6129:Line Number is 29
    BPCOR-6130:Activity Name is Invoke1
    at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.processStatus(InvokeUnitImpl.java:968)
    at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.process(InvokeUnitImpl.java:538)
    at com.sun.jbi.engine.bpel.core.bpel.model.runtime.impl.InvokeUnitImpl.doAction(InvokeUnitImpl.java:181)
    at com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELInterpreter.execute(BPELInterpreter.java:148)
    at com.sun.jbi.engine.bpel.core.bpel.engine.BusinessProcessInstanceThread.execute(BusinessProcessInstanceThread.java:98)
    at com.sun.jbi.engine.bpel.core.bpel.engine.impl.BPELProcessManagerImpl.process(BPELProcessManagerImpl.java:1001)
    at com.sun.jbi.engine.bpel.core.bpel.engine.impl.EngineImpl.process(EngineImpl.java:258)
    at com.sun.jbi.engine.bpel.core.bpel.engine.impl.EngineImpl.process(EngineImpl.java:1229)
    at com.sun.jbi.engine.bpel.BPELSEInOutThread.processStatus(BPELSEInOutThread.java:407)
    at com.sun.jbi.engine.bpel.BPELSEInOutThread.processMsgEx(BPELSEInOutThread.java:239)
    at com.sun.jbi.engine.bpel.BPELSEInOutThread.run(BPELSEInOutThread.java:191)
    *Caused by: com.sun.xml.ws.server.UnsupportedMediaException: Unsupported Content-Type: text/html; charset=iso-8859-1 Supported ones are: [text/xml]*
    at com.sun.xml.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:291)
    at com.sun.xml.ws.encoding.StreamSOAPCodec.decode(StreamSOAPCodec.java:128)
    at com.sun.xml.ws.encoding.SOAPBindingCodec.decode(SOAPBindingCodec.java:287)
    at com.sun.xml.ws.transport.http.client.HttpTransportPipe.process(HttpTransportPipe.java:171)
    at com.sun.xml.ws.tx.client.TxClientPipe.process(TxClientPipe.java:177)
    at com.sun.xml.ws.api.pipe.helper.PipeAdapter.processRequest(PipeAdapter.java:115)
    at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:595)
    at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:554)
    at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:539)
    at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:436)
    at com.sun.xml.ws.client.Stub.process(Stub.java:248)
    at com.sun.xml.ws.client.dispatch.DispatchImpl.doInvoke(DispatchImpl.java:180)
    at com.sun.xml.ws.client.dispatch.DispatchImpl.invoke(DispatchImpl.java:206)
    at com.sun.jbi.httpsoapbc.OutboundMessageProcessor.outboundCall(OutboundMessageProcessor.java:986)
    at com.sun.jbi.httpsoapbc.OutboundMessageProcessor.dispatch(OutboundMessageProcessor.java:1016)
    at com.sun.jbi.httpsoapbc.OutboundMessageProcessor.processRequestReplyOutbound(OutboundMessageProcessor.java:661)
    at com.sun.jbi.httpsoapbc.OutboundMessageProcessor.processMessage(OutboundMessageProcessor.java:243)
    at com.sun.jbi.httpsoapbc.OutboundAction.run(OutboundAction.java:63)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
    at java.lang.Thread.run(Thread.java:619)
    Request doesnt have a Content-Type
    com.sun.xml.ws.server.UnsupportedMediaException: Request doesnt have a Content-Type
    at com.sun.xml.ws.encoding.SOAPBindingCodec.decode(SOAPBindingCodec.java:267)
    at com.sun.xml.ws.transport.http.HttpAdapter.decodePacket(HttpAdapter.java:276)
    at com.sun.xml.ws.transport.http.HttpAdapter.invokeAsync(HttpAdapter.java:341)
    at com.sun.jbi.httpsoapbc.embedded.JAXWSGrizzlyRequestProcessor.processAsynchRequest(JAXWSGrizzlyRequestProcessor.java:372)
    at com.sun.jbi.httpsoapbc.embedded.JAXWSGrizzlyRequestProcessor.service(JAXWSGrizzlyRequestProcessor.java:228)
    at com.sun.enterprise.web.connector.grizzly.DefaultProcessorTask.invokeAdapter(DefaultProcessorTask.java:637)
    at com.sun.jbi.httpsoapbc.embedded.JBIGrizzlyAsyncFilter.doFilter(JBIGrizzlyAsyncFilter.java:95)
    at com.sun.enterprise.web.connector.grizzly.async.DefaultAsyncExecutor.invokeFilters(DefaultAsyncExecutor.java:175)
    at com.sun.enterprise.web.connector.grizzly.async.DefaultAsyncExecutor.interrupt(DefaultAsyncExecutor.java:153)
    at com.sun.enterprise.web.connector.grizzly.async.AsyncProcessorTask.doTask(AsyncProcessorTask.java:92)
    at com.sun.enterprise.web.connector.grizzly.TaskBase.run(TaskBase.java:265)
    at com.sun.enterprise.web.connector.grizzly.WorkerThreadImpl.run(WorkerThreadImpl.java:116)

    Jossarm/Jeff,
    The Cryptography forum is not the right forum for this question; have you tried posting to the Glassfish forum on java.net?
    But, here is what I think the problem might be:
    SOAP-based web-service security uses XML Signature and XML Encryption to secure the message - not SSL; as a result it uses text/xml at the start of its message (which is what SOAP messages are). SSL assumes that the secure session has been established and all messages thereafter, are expected to begin with text/html (as expected in HTTP). You cannot mix-and match this - unless the service is an HTTP-based service that expects a SOAP-based message embedded in the HTTPRequest.

  • [svn:fx-trunk] 7661: Change from charset=iso-8859-1" to charset=utf-8" and save file with utf-8 encoding.

    Revision: 7661
    Author:   [email protected]
    Date:     2009-06-08 17:50:12 -0700 (Mon, 08 Jun 2009)
    Log Message:
    Change from charset=iso-8859-1" to charset=utf-8" and save file with utf-8 encoding.
    QA Notes:
    Doc Notes:
    Bugs: SDK-21636
    Reviewers: Corey
    Ticket Links:
        http://bugs.adobe.com/jira/browse/iso-8859
        http://bugs.adobe.com/jira/browse/utf-8
        http://bugs.adobe.com/jira/browse/utf-8
        http://bugs.adobe.com/jira/browse/SDK-21636
    Modified Paths:
        flex/sdk/trunk/templates/swfobject/index.template.html

    same problem here with wl8.1
    have you sold it and if yes, how?
    thanks

  • Client found response content type of 'text/html;charset=iso-8859-1', but expected 'text/xml'.

    Hello All,
    I am on BI 4.0 SP6.
    I am login to Advance Analysis Office using sso with Authentication : Windows AD, but when i login errors occurs:
    Client found response content type of 'text/html;charset=iso-8859-1', but expected 'text/xml'.
    The request failed with the error message:
    I have done all settings and configuration for SSO as per following notes:
    http://service.sap.com/sap/support/notes/1631734
    http://service.sap.com/sap/support/notes/1646920
    http://service.sap.com/sap/support/notes/1794675
    Earlier i was getting Login Exception Error WSE : 99999, i did some changes, after that the above error is coming
    Does anybody knows the solution?
    KR,
    MD

    refer the below note
    1785270 - How to configure AD SSO for Advance Analysis for MS Office with Business Objects BI 4.0

  • Not a valid SOAP Content-Type: text/html; charset=iso-8859-1

    Friends
    JDEV and SOA suite 10134
    I have multiple domains on my BPEL Server. In one of the domain since I deployed the new process, all the processes of that domain are now failing on execution with following error in opmn/soa_instance/*.err log files. No errors in domain.log
    +"Caused by: java.security.PrivilegedActionException: oracle.j2ee.ws.saaj.ContentTypeException: Not a valid SOAP Content-Type: text/html; cha+
    +rset=iso-8859-1"+
    At the same time we get Internal Server Error on BPEL Console.
    I have sync processes with 1 or two invokes, so I am generally losing the instances, cannot provide the details in the process execution. All BPEL processes are invoking Siebel Web Services, that is the common part.
    When I restart my system, it may or may not work; even if it works then within few instances execution again starts giving the same error. I can see that after the errors the instance are going through and getting completed successfully few times. All these processes were working successfully earlier.
    Any idea about this !!!!
    Thanks

    Thanks Anirudh,
    I don't use compensation handlers. Moreover I have properly defined the scopes and sequences throughout the bpel process. My processes are sync in nature and I'm not able say at what step exactly the processes are failing and throwing the SOAP content Type error though the instances are getting completed with delay soemtimes.

  • Problem with charset  ISO-8859 with dinamic action

    Hello
    I migrated my application that was Apex 3.2, and now Apex is 4.2.3, but a have a problem when I'm use Dynamic Action with ISO-8859.
    When I used a filter "ação" in dinamic action filter mounted by the apex presents 'aà § à £ o.'
    If I force use of PlsqlNLSLanguage = BRAZILIAN PORTUGUESE_BRAZIL.UTF8 in Dads, works correct.
    Please, Help me! I need to keep ISO-8859!
    Thanks

    Using another example to illustrate the problem… I
    found an apparent solution using "encodeURI".
    It sees:
    quote:
    BEFORE:
    function SaveMsg()
    if (document.sender.message == "" )
    return false;
    var mensagem=document.sender.message.value;
    ds2.setURL('responsexml.asp?action=add'&msg='+mensagem);
    ds2.loadData();
    document.sender.message.value="";
    document.sender.message.focus();
    When the entrance of the changeable "mensagem" was
    “João” was recorded in archive XML as
    “Joo” ...
    input: "João"
    output: "Joo"
    quote:
    AFTER:
    function SaveMsg()
    if (document.sender.message == "" )
    return false;
    var mensagem=encodeURI(document.sender.message.value);
    ds2.setURL('responsexml.asp?action=add'&msg='+mensagem);
    ds2.loadData();
    document.sender.message.value="";
    document.sender.message.focus();
    Now ...
    input: "João"
    output: "João"
    This would be a good solution? I will not have problems,
    right? Some opinion/suggestion on this solution?

  • IllegalStateException: (cannot change charset from 'ISO-8859-1' to 'null')

              My index.jsp page has the directive <%@ page contentType="text/html;charset=ISO-8859-1"
              %>.
              It uses my templating tag-library, which uses a requestDispatcher to include my
              template.
              My template doesn't have this contentType directive.
              Then I get an exception :
              java.lang.IllegalStateException: Attempt to change ContentType after calling getWriter()
              (cannot change charset from 'ISO-8859-1' to 'null')
              It actually works perfectly on WLS6.0.
              Here is the complete stacktrace which shows the path page -> tag -> include
              java.lang.IllegalStateException: Attempt to change ContentType after calling getWriter()
              (cannot change charset from 'ISO-8859-1' to 'null')
                   at weblogic.servlet.internal.ServletResponseImpl.setEncoding(ServletResponseImpl.java:695)
                   at weblogic.servlet.internal.ServletResponseImpl.setHeader(ServletResponseImpl.java:566)
                   at weblogic.servlet.internal.ServletResponseImpl.setContentType(ServletResponseImpl.java:236)
                   at weblogic.servlet.internal.ServletRequestImpl.reportJSPFailure(ServletRequestImpl.java:162)
                   at weblogic.servlet.internal.ServletRequestImpl.reportJSPTranslationFailure(ServletRequestImpl.java:168)
                   at weblogic.servlet.jsp.JspStub.reportTranslationFailure(JspStub.java:503)
                   at weblogic.servlet.jsp.JspStub.compilePage(JspStub.java:317)
                   at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:181)
                   at weblogic.servlet.jsp.JspStub.prepareServlet(JspStub.java:149)
                   at weblogic.servlet.internal.ServletStubImpl.getServlet(ServletStubImpl.java:344)
                   at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:240)
                   at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
                   at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:327)
                   at weblogic.servlet.internal.RequestDispatcherImpl.include(RequestDispatcherImpl.java:207)
                   at bv2.template.TemplateRequest.doStartTemplate(TemplateRequest.java:56)
                   at bv2.template.BodyTag.doStartTag(BodyTag.java:31)
                   at jsp_servlet._index._jspService(_index.java:173)
                   at weblogic.servlet.jsp.JspBase.service(JspBase.java:27)
                   at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:245)
                   at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:200)
                   at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:2279)
                   at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:1923)
                   at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
                   at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              

    [att1.html]
              

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

  • Convert utf-8 to iso-8859-1

    Hello,
    sorry for my very bad english
    i use httpxmlrequest to answer a database and show resultin a
    div
    the string means utf-8 encoded by my javascript fonction and,
    of course,
    no result are found in the database.
    How can i convert the string to iso-8859-1 before request the
    database ?
    Thank if you have an idea
    JiBé (France)

    PaulH **AdobeCommunityExpert** a écrit :
    > Jibé wrote:
    >> PaulH **AdobeCommunityExpert** a écrit :
    >> I work with a MS SQL server database encoding in
    iso-8859-1
    >
    > data stored in plain text,char,varchar datatypes (ie not
    "N")?
    datatype of "titre" is varchar(250) and "contenu" is text
    using the
    > ODBC or JDBC (it would be listed as ms sql server in the
    db drivers
    > list) driver?
    I think it's jdbc driver (case of my test computer)
    >
    >> The code :
    >
    > you're not following good i18n practices. while my
    preference is for
    > unicode ("just use unicode" has been my motto for
    years), if you're
    > really only ever going to use french & never need
    the euro symbol then i
    > guess iso-8859-1 (latin-1) is fine.
    Here is a part of the content of my application.cfm
    <cfprocessingdirective pageencoding="iso-8859-1">
    <cfcontent type="text/html; charset=iso-8859-1">
    <cfset setEncoding("URL", "iso-8859-1")>
    <cfset setEncoding("Form", "iso-8859-1")>
    >
    > if you think you might need other languages, including
    the euro symbol,
    > then you should consider unicode. change your text
    columsn to "N" type
    > (nText, nChar, nVarChar) & swap the latin-1
    encodings in the tags above
    > to utf-8.
    I'm going to test that....
    JiBé

  • 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

  • Mail adapter module  UTF-8 to ISO-8859-1 conversion

    Hi!
    I've a problem with a mail attachment which is generated by an adapter module for the mail adapter. The content type is set to "Application/EDIFACT; charset=iso-8859-1" when I add the attachment, but the mail adapter ignores the charset-setting.
    Therefore german "umlauts" like ü are displayed in a wrong way: ü
    When I set the content, I transform it in ISO-8859-1 : attachment.setContent(edifactString.getBytes("ISO-8859-1"),"ISO-8859-1");
    When I test the result of edifactString.getBytes("ISO-8859-1"), I get the String in the right character encoding, but the mail adapter seems to "fix" the encoding
    I also tried to use the messageTransformBean, but it doesn't worked.
    Anyone knows how to solve this issue?
    Best regards,
    Daniel

    Hi all!
    I found a solution for this problem: First I used the TextPayload-Object for the Attachment which should be added. It seems that the TextPayload-Object has some bugs handling different encodings (handels only Unicode and deletes the charset=... setting from the ContentType).
    When using the Payload object for the attachment (which handles binary data), there is no conversion to Unicode, so I get my attachment as desired (but still without the charset-setting).
    Best regards,
    Daniel

  • HTTP Test Tool Umlaut (Special Character) Problem iso-8859-1 utf-8

    Hi folks,
    I habe a Problem in an HTTP to IDOC Scenario. The configuration works and when I test it, by using the Test Message Tool from the Runtime Workbench i get the following problem:
    I post an IDOC XML Charset iso-8859-1 when it arrive as IDoc in business system german umlauts would be displayd very cryptic
    ä = ä
    ü = ü
    and so on ....
    When I post the XML with UTF-8 charset it works, what can i do to handle this ?
    Thank you

    Hi,
    maybe this document is helpful:
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/502991a2-45d9-2910-d99f-8aba5d79fb42
    and also this thread:
    Character translation error in Mapping Lookup API (RFC)
    Regards
    Patrick

  • Iso-8859-1 to UTF-8

    JExpert,
    The encoding of my current servlet is iso-8859-1 when i execute the following method. How can I change it into UTF-8?
         public void displaySkinFile(HttpServletRequest req, HttpServletResponse resp, String skinFile) throws ServletException, IOException {
              try {
                   String fileContent = getFileContent(skinFile);
                   resp.setContentType("text/html");
    System.out.println("encoding="+resp.getCharacterEncoding());
                   PrintWriter out = resp.getWriter();
                   out.println(fileContent);
              } catch (FileNotFoundException e) {
                   logAndRedirect(req, resp, skinFile);
              } catch (IOException e) {               
                   logAndRedirect(req,resp,skinFile);
    Thanks!!

    I am having a similar problem, but whenever I do the setContentType, it is not actually switching it for me. Any ideas?
    CODE:
         protected void doGet(HttpServletRequest req, HttpServletResponse resp)
                   throws ServletException, IOException {
              PrintWriter w = resp.getWriter();
              String text;
              String path = null;
              text = map.getDocumentText(path);
                   System.out.println("BEFORE: Char Encoding");
                   System.out.println(resp.getCharacterEncoding());
                   System.out.println("BEFORE: Content Type");
                   System.out.println(resp.getContentType());
              resp.setContentType("text/html; charset=utf-8");
              resp.setCharacterEncoding("UTF-8");
              resp.setContentLength(text.length());
              w.write(text);
                   System.out.println("AFTER: Char Encoding");
                   System.out.println(resp.getCharacterEncoding());
                   System.out.println("AFTER: Content Type");
                   System.out.println(resp.getContentType());
    CONSOLE OUTPUT:
    BEFORE: Char Encoding
    ISO-8859-1
    BEFORE: Content Type
    null
    AFTER: Char Encoding
    ISO-8859-1
    AFTER: Content Type
    text/html;charset=ISO-8859-1

  • 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?

  • Cant mount usb sticks with fat32 ISO-8859-1 2.6.31-ARCH

    when trying to mount my usb sticks from xfce4 desktop(halmount).
    Following error occurs (as told by dmesg).
    FAT: IO charset ISO-8859-1 not found
    First i suspected hal being the culprit but now im not so sure anymore.
    im using stock 2.6.31-ARCH.
    when i checked the .config for the stock kernel CONFIG_NLS_ISO8859_1=y is enabled in the kernelconfig, and also everything below to support fat32.
    CONFIG_FAT_FS=m
    CONFIG_MSDOS_FS=m
    CONFIG_VFAT_FS=m
    CONFIG_FAT_DEFAULT_CODEPAGE=437
    CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
    CONFIG_NTFS_FS=m
    but when i list the modules nls_iso8859-1.ko is missing.
    #~ls -a /lib/modules/2.6.31-ARCH/kernel/fs/nls/nls_iso*
    /lib/modules/2.6.31-ARCH/kernel/fs/nls/nls_iso8859-13.ko
    /lib/modules/2.6.31-ARCH/kernel/fs/nls/nls_iso8859-14.ko
    /lib/modules/2.6.31-ARCH/kernel/fs/nls/nls_iso8859-15.ko
    /lib/modules/2.6.31-ARCH/kernel/fs/nls/nls_iso8859-2.ko
    /lib/modules/2.6.31-ARCH/kernel/fs/nls/nls_iso8859-3.ko
    /lib/modules/2.6.31-ARCH/kernel/fs/nls/nls_iso8859-4.ko
    /lib/modules/2.6.31-ARCH/kernel/fs/nls/nls_iso8859-5.ko
    /lib/modules/2.6.31-ARCH/kernel/fs/nls/nls_iso8859-6.ko
    /lib/modules/2.6.31-ARCH/kernel/fs/nls/nls_iso8859-7.ko
    /lib/modules/2.6.31-ARCH/kernel/fs/nls/nls_iso8859-9.ko
    So i suspect the newest kernel broke mounting with hal.
    Last edited by nichlas.johansson (2009-10-17 14:25:56)

    Based on the information given in http://bbs.archlinux.org/viewtopic.php?id=82176, I changed in /etc/rc.conf from LOCALE=en_GB.iso88591 to LOCALE=en_GB.utf8, uncommented en_GB.UTF-8 UTF-8  in /etc/locale.gen, issued # locale-gen and after a reboot, I was able to mount my usb sticks again.
    However, now I get "FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!" in dmesg. Is this something, I need to worry about...?
    Last edited by smurf (2009-10-19 08:29:15)

Maybe you are looking for