SuperDrive and Encoding Problems

Can someone please explain to me why a disk would be
un useable after the encoding process but before the burn process?
I thought that the encoding didn't put any data on the disk and it was still blank.
I'm having problems with my Super Drive again. It stopped burning DL disks and I tested out 3 different disks.
Last week I burned about 10 DL disks and everything was fine, this week, it won't burn.
I'm not sure I'm too impressed if this machine keeps puttering out with the burn process.
Has anyone else experienced this with their drive?
And why can't disks be used again after the encoding process?
I don't understand that at all.
Thanks for your help, if you've got it.

+And why can't disks be used again after the encoding process?+
If you don't create a disk image, iDVD encodes and then burns the DVD-R and then spits it out and asks if you'd like to make another copy.

Similar Messages

Tomcat, custom error page, sendError and encoding problems

Hi All!
I have the following code in my index.jsp page:
<%
    if(hasParent && !imageStore.contains(parent))
        response.sendError(404, "Requested image with id=" + parent + " was not found on this server");
        return;
%>following in the web.xml:
<error-page>
    <error-code>404</error-code>
    <location>/404.jsp</location>
</error-page>Both pages (index.jsp and 404.jsp) are windows-1251 encoded:
<%@page contentType="text/html; charset=windows-1251"%>But I have an issue: all non-latin characters are mangled when 404.jsp displayed as the result of calling response.sendError.
I mean, if I open myserver.com/404.jsp or myserver.com/non-existing-document-la-la-la, everything is okay. But when I open myserver.com/index.jsp?parent=123 it calls response.sendError - text is mangled.
What's even more bizarre, Tomcat sends the right encoding in the response headers, but with ? instead non-latin characters:
HTTP request sent, awaiting response...
1 HTTP/1.1 404 Requested image with id=1231231 was not found on this server
2 Content-Type: text/html;charset=windows-1251
3 Date: Sat, 16 Sep 2006 18:14:27 GMT
4 Server: Apache-Coyote/1.1
5 Connection: Keep-Alive
22:14:27 ERROR 404: Requested image with id=1231231 was not found on this server
.I am using Apache Tomcat/5.0.28.
I understand that this issue is not trivial, but I would appreciate any ideas.

Hi All!
I have the following code in my index.jsp page:
<%
    if(hasParent && !imageStore.contains(parent))
        response.sendError(404, "Requested image with id=" + parent + " was not found on this server");
        return;
%>following in the web.xml:
<error-page>
    <error-code>404</error-code>
    <location>/404.jsp</location>
</error-page>Both pages (index.jsp and 404.jsp) are windows-1251 encoded:
<%@page contentType="text/html; charset=windows-1251"%>But I have an issue: all non-latin characters are mangled when 404.jsp displayed as the result of calling response.sendError.
I mean, if I open myserver.com/404.jsp or myserver.com/non-existing-document-la-la-la, everything is okay. But when I open myserver.com/index.jsp?parent=123 it calls response.sendError - text is mangled.
What's even more bizarre, Tomcat sends the right encoding in the response headers, but with ? instead non-latin characters:
HTTP request sent, awaiting response...
1 HTTP/1.1 404 Requested image with id=1231231 was not found on this server
2 Content-Type: text/html;charset=windows-1251
3 Date: Sat, 16 Sep 2006 18:14:27 GMT
4 Server: Apache-Coyote/1.1
5 Connection: Keep-Alive
22:14:27 ERROR 404: Requested image with id=1231231 was not found on this server
.I am using Apache Tomcat/5.0.28.
I understand that this issue is not trivial, but I would appreciate any ideas.

Playback and encoding problems premiere pro cs6 and lightroom4

BIG BLOCKY ARTIFACTS
the problem ocours in all videos(every 1sec) i recorded in my dslr d5100. 1080p 30fps .mov files. in media player classic it play flawless all videos as seen in my pics.
how to fix it? i tried unstalling codecs and nothing. will try installing quicktime. i think its codecs or maybe hardware.
my pc is i5-2500k gpu gtx560 8gb ram.
please help me. thanks

[URL=http://www.4shared.com/video/94VvVdUM/0511_videogasometro_002.html][IMG]http://dc584.4shared.com/img/94VvVdUM/0.4382360316505566/0511_videogasometro_002.MOV[/IMG][/URL]
its 280mb, original. worst artifacts at 13secs.

Encoding problems in email while on Windows Mail app

Hello.
I have a question concerning email and encoding problems in the Windows Mail App in Windows 8.1. I have encountered a problem with an email I received, while reading, I see strange ASCII characters in one email. I have never encountered it in
my web browsers nor Gmail, just the Mail App.
I was referred to come here when I had asked a similar question there:
http://answers.microsoft.com/en-us/windows/forum/windows8_1-ecoms/strange-foreign-ascii-characters-appearing-in/911f8a44-c302-4fa1-bcaa-3297b32d9120
I don't know which forum to go to so I picked here.
Is there any way that it can be resolved. I tried to troubleshoot, nothing worked; I even synched, to no avail.
I look forward to a response.
JB

Hi JB,
The responder on answers was a bit confused. The MSDN forums are for developers to discuss writing their own apps. We cannot help with problems using Windows or its built-in apps.
If the folks on answers cannot help then you may need to open a support incident. See
http://support.microsoft.com , or the folks on answers may be able to direct you to the specific page for the Windows Mail app.
--Rob

Character encoding problem using XSLT and Tomcat on Linux

Hi,
I have an application running on a Tomcat 4.1.18 application server that applies XSLT transformations to DOM objects using standard calls to javax.xml.transform API. The JDK is J2SE 1.4.1_01.
It is all OK while running on a development enviroment (which is Windows NT 4.0 work station), but when I put it in the production enviroment (which is a red hat linux 8.0), it comes up with some kind of encoding problem: the extended characters (in spanish) are not shown as they should.
The XSL stylesheets are using the ISO-8859-1 encoding, but I have also tried with UTF-8.
These stylesheets are dynamicly generated from a JSP:
// opens a connection to a JSP that generates the XSL
URLConnection urlConn = (new URL( xxxxxx )).openConnection();
Reader readerJsp = new BufferedReader(new InputStreamReader( urlConn.getInputStream() ));
// Gets the object that represents the XSL
Templates translet = tFactory.newTemplates( new StreamSource( readerJsp ));
Transformer transformer = translet.newTransformer();
// applies transformations
// the output is sent to the HttpServletResponse's outputStream object
transformer.transform(myDOMObject, new StreamResult(response.getOutputStream()) );Any help would be appreciated.

Probably you need to set your LANG OS especific environment variable to spanish.
Try adding this line:
export LANG=es_ES
to your tomcat/bin/catalina.sh, and restart tomcat.
It should look like this:
# OS specific support. $var _must_ be set to either true or false.
cygwin=false
case "`uname`" in
CYGWIN*) cygwin=true;;
esac
export LANG=es_ES
# resolve links - $0 may be a softlink
PRG="$0"
.(BTW, keep using ISO-8859-1 encoding for your XSL)
HTH
Un Saludo!

Using Max to rip and encode cds but encountering problems

I thought I'd use this software for a change something isnt quite right,On some cds the title artist and list of tracks appears as it should on Max window then the ripping and encoding commences.Only problem here is that i keep getting an ITunes file permission error which i have to delete each time .On other cds The Max window appears with nothing showing, the ripping and encoding starts but then seems to stop only to start importing in iTunes,I then stop this process to allow Max to continue but the end result is a iget a long list of unnamed tracks at the bottom of my itunes Music library.It seems like i havent got my settings quite right?? Could someone please advise me what the problem could be? thanks
Message was edited by: angloargie

You're problem is entirely different from the original poster's. You're more likely to get help if you start your own thread with a descriptive subject line. Include any error messages you're getting and any steps you've taken already to solve the problem.
Best of luck.

HD DVD encoding and playback problem

Hello,
we are running into a problem with some HD dvd authoring lately. We are using 1920x1080 23.98fps film based source material and encode it for HD DVD use with compressor. Like it says in the documentation we are using the hd dvd presets and just adjust the output to 720P for an H.264 encode. Apparently since the last upgrade to DVD studio 4.2 it is now possible to encode progressive h.264 with a framerate of 23.98 fps. Well as i said we encode the footage with compressor, import it into DVDSP 4.2 and include it into our project. Everything works fine until we put it into our DVD player (Toshiba HD-A20). The menus and everything works and looks great, but when we are playing the 720P 23.98fps H.264 clips we get a way too fast playing clip, basically as if it is trying to play it at 29.97 fps. Does anyone else run into that problem? First we thought it is the player, but then we tried playing the disc in our Macpro and the same problem. 1920x1080 works great with Mpeg2 29,97fps compression, even though, because we have film based 23.98fps source material it seems to stutter slightly. I wonder if we need to include 2:3 pulldown in order for the player to remove it properly. Any help would be great.
Thanks,
Gorilla

Harm,
Sorry for not responing for a few days, but I runned the benchmark you'll send me. The main results (dee details attached file):
53,6, secs Total Benchmark Time
6,4, secs AVI Encoding Time
14,2, secs MPEG Elapsed Time
33, secs Rendering Time
Since the potential problem is my hard disk, inaddition, I runned HDtune (hopefully it will help pinpionting the problem):
disk1: avarage transfer rate: 94MB/s, acces time 13.8ms, burst rate 185MB/s
disk2: avarage transfer rate: 85MB/s, acces time 14ms, burst rate 157MB/s
disk3: avarage transfer rate: 73MB/s, acces time 13.9ms, burst rate 183MB/s
Analyzing these results, could the current hard disk configuration cause the problem I have, or is my system to slow anyway to edit AVCHD material?
If the hard disk configuration is the problem, could it be solved by applying your suggestion by removing all partitions? Since, I'm not looking forward of removing all partions(re-installing windows (dual boot win7 and vista), shifting a huge amount of data, etc), but if it would help I will do it.
Thanks inadvance,
Jeffrey

XML deserialize and decrypting encoding problem. Please help me

This is my first topic here, so at first I'd like to say "Hi" everyone and apologise for my bad english ;)
I have just finished my new application about signing/checking and encrypting/decrypting XML files. I use Apache XML Security packages to do this.
Everything works fine, instead of one...
I'm Polish and sometimes I have to encrypt or decrypt XML which includes polish letters like: 'ą' , 'ę', 'ł' and some others... If I encrypt such file, it succeeds. The problem is when I try to decrypt such an encrypted file. I recieve an error like :
"[Fatal Error] :2:7: An invalid XML character (Unicode: 0x19) was found in the element content o
f the document.
gov.mf.common.exceptions.SenderException: E_SENDER_DECRYPTION
at gov.mf.common.xml.encryption.EncryptTool.decrypt(Unknown Source)
at gov.mf.CERBER.TestCBR.main(Unknown Source)
Caused by: org.apache.xml.security.encryption.XMLEncryptionException: An invalid XML character
(Unicode: 0x19) was found in the element content of the document.
Original Exception was org.xml.sax.SAXParseException: An invalid XML character (Unicode: 0x19)
was found in the element content of the document.
at org.apache.xml.security.encryption.XMLCipher$Serializer.deserialize(Unknown Source)
at org.apache.xml.security.encryption.XMLCipher.decryptElement(Unknown Source)
at org.apache.xml.security.encryption.XMLCipher.doFinal(Unknown Source)
... 2 more
What's wrong? My XML document is UTF-8 encoded, with or without BOM. I wrote in in Notepad++ or any other editior which has UTF-8 encoding.
I'm parsing my XML with DOM. There is an interesting line in an error above like: " at org.apache.xml.security.encryption.XMLCipher$Serializer.deserialize(Unknown Source)" , do you know that?
Everything is fine when I try to encrypt/decrypt '�' or 'ń', but things go wrong with 'ą', 'ę', 'ł' and others... I also managed to encrypt and decrypt 'ł' but unfortunately, after decryption 'ł' turns into 'B'. It obviously an encoding problem, but how to fix it?
I would be really thankfull if some of You guys would help me.
Looking forward fo any answers.
Matthew
Message was edited by:
matthew_pl

Hi once again.
I still don't havy any solution to my problem. I used Apache XML Security examples to encrypt/decrypt my XML document with Polish charaters but I also recieve the same error. What's wrong?
Here is some code:
----- Parsing XML do Document ------
DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
     //Bardzo wazna linijka - bless TEK ;)
     factory.setNamespaceAware(true);
     DocumentBuilder builder;
     builder = factory.newDocumentBuilder();
     File f = new File(Const.FILE_IN_PATH + File.separator + Const.FILE_IN);
     org.w3c.dom.Document doc = builder.parse(f);
---------- Encrypting & Decrypting XML document (whole class) -------------
import java.io.*;
import java.security.*;
import javax.crypto.SecretKey;
import javax.crypto.SecretKeyFactory;
import javax.crypto.spec.DESedeKeySpec;
import org.w3c.dom.Document;
import org.w3c.dom.Element;
import org.apache.xml.security.keys.KeyInfo;
import org.apache.xml.security.utils.EncryptionConstants;
import org.apache.xml.security.encryption.XMLCipher;
import org.apache.xml.security.encryption.EncryptedData;
import org.apache.xml.security.encryption.EncryptedKey;
public class EncryptTool
private PublicKey publicKey;
private PrivateKey privateKey;
static
org.apache.xml.security.Init.init();
public EncryptTool()
     publicKey = KeyStores.getCerberPublicKey();
     privateKey = KeyStores.getCerberPrivateKey();
public Document encrypt(Document doc, String sufix)
try
     byte[] passPhrase = "24 Bytes per DESede key!".getBytes("UTF-8");
     DESedeKeySpec keySpec = new DESedeKeySpec(passPhrase);
     SecretKeyFactory keyFactory = SecretKeyFactory.getInstance("DESede");
     SecretKey secretKey = keyFactory.generateSecret(keySpec);
     XMLCipher keyCipher = XMLCipher.getInstance(XMLCipher.RSA_v1dot5);
     keyCipher.init(XMLCipher.WRAP_MODE, publicKey);
     EncryptedKey encryptedKey = keyCipher.encryptKey(doc, secretKey);
          Element elementToEncrypt = (Element) doc.getDocumentElement();
          System.out.println("Szyrfuję: " + elementToEncrypt.getTextContent());
          XMLCipher xmlCipher = XMLCipher.getInstance(XMLCipher.TRIPLEDES);
          xmlCipher.init(XMLCipher.ENCRYPT_MODE, secretKey);
          EncryptedData encryptedDataElement = xmlCipher.getEncryptedData();
          KeyInfo keyInfo = new KeyInfo(doc);
          keyInfo.add(encryptedKey);
          encryptedDataElement.setKeyInfo(keyInfo);
          boolean encryptContentsOnly = true;
          xmlCipher.doFinal(doc, elementToEncrypt, encryptContentsOnly);
          // output the resulting document
          String [] parts = Const.FILE_IN.split("\\.");
          String saveAs = Const.FILE_OUT_PATH + File.separator + parts[0] + sufix + "." + parts[1];
          OutputStream os = new FileOutputStream(saveAs);
          XMLUtil.sameXMLtoFile(doc, os);
} catch (Exception ex)
     throw new TestCBRException("E_CERBER_ENCRYPTION", ex);
return doc;
public void decrypt(Document doc, String sufix) throws SenderException
try
          String namespaceURI = EncryptionConstants.EncryptionSpecNS;
     String localName = EncryptionConstants._TAG_ENCRYPTEDDATA;
     int ile = doc.getElementsByTagNameNS(namespaceURI, localName).getLength();
     if (ile == 0) throw new SenderException("E_SENDER_DECRYPTION_NEEDED");
     for(int i=0; i < ile; i++)
     Element encryptedDataElement = (Element) doc.getElementsByTagNameNS(namespaceURI, localName).item(0);
     XMLCipher xmlCipher = XMLCipher.getInstance();
     xmlCipher.init(XMLCipher.DECRYPT_MODE, null);
     xmlCipher.setKEK(privateKey);
     xmlCipher.doFinal(doc, encryptedDataElement);
               String [] parts = Const.FILE_IN.split("\\.");
               String saveAs = Const.FILE_OUT_PATH + parts[0] + sufix + "." + parts[1];
               OutputStream os = new FileOutputStream(saveAs);
                    XMLUtil.saveXMLtoFile(doc, os);
} catch (SenderException ex) {
     throw ex;
} catch (Exception ex) {
     throw new SenderException("E_SENDER_DECRYPTION", ex);
Please help me. I'm going into madness what's wrong with it...

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>

Encoding problem while reading binary data from MQ-series

Dear all,
we are running on 7.0 and we have an encoding problem while reading binary data from MQ-series. Because we are getting flat strings from queue we use module "Plain2ML" (MessageTransformBean) for wrapping xml-elements around the incoming data.
The MQ-Series-Server is using CCSID 850, which we configured in connection parameters in communication channel (both parameters for Queuemanager CCSID and also CCSID of target).If there are special characters in the message (which HEX-values differ from codepage to codepage) we get errors in our adapter while executing, please see stack-trace for further analysis below.
It seems to us that
1. method ByteToCharUTF8.convert() expects UTF-8 in binary data
2. Both CCSID parameters are not used anyway in JMS-adapter
How can we solve this problem without changing anything on MQ-site?
Here is the stack-trace:
Catching com.sap.aii.af.mp.module.ModuleException: Transform: failed to execute the transformation: com.sap.aii.messaging.adapter.trans.TransformException: Error converting Message: 'sun.io.MalformedInputException'; nested exception caused by: sun.io.MalformedInputException caused by: com.sap.aii.messaging.adapter.trans.TransformException: Error converting Message: 'sun.io.MalformedInputException'; nested exception caused by: sun.io.MalformedInputException
    at com.sap.aii.af.modules.trans.MessageTransformBean.throwModuleException(MessageTransformBean.java:453)
    at com.sap.aii.af.modules.trans.MessageTransformBean.process(MessageTransformBean.java:387)
    at com.sap.aii.af.mp.module.ModuleLocalLocalObjectImpl0_0.process(ModuleLocalLocalObjectImpl0_0.java:103)
    at com.sap.aii.af.mp.ejb.ModuleProcessorBean.process(ModuleProcessorBean.java:292)
    at com.sap.aii.af.mp.processor.ModuleProcessorLocalLocalObjectImpl0_0.process(ModuleProcessorLocalLocalObjectImpl0_0.java:103)
    at com.sap.aii.adapter.jms.core.channel.filter.SendToModuleProcessorFilter.filter(SendToModuleProcessorFilter.java:84)
    at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
    at com.sap.aii.adapter.jms.core.channel.filter.ConvertBinaryToXiMessageFilter.filter(ConvertBinaryToXiMessageFilter.java:304)
    at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
    at com.sap.aii.adapter.jms.core.channel.filter.ConvertJmsMessageToBinaryFilter.filter(ConvertJmsMessageToBinaryFilter.java:112)
    at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
    at com.sap.aii.adapter.jms.core.channel.filter.InboundDuplicateCheckFilter.filter(InboundDuplicateCheckFilter.java:87)
    at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
    at com.sap.aii.adapter.jms.core.channel.filter.TxManagerFilter.filterSend(TxManagerFilter.java:123)
    at com.sap.aii.adapter.jms.core.channel.filter.TxManagerFilter.filter(TxManagerFilter.java:59)
    at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
    at com.sap.aii.adapter.jms.core.channel.filter.DynamicConfigurationFilter.filter(DynamicConfigurationFilter.java:72)
    at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
    at com.sap.aii.adapter.jms.core.channel.filter.PmiAgentFilter.filter(PmiAgentFilter.java:66)
    at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
    at com.sap.aii.adapter.jms.core.channel.filter.InboundCorrelationFilter.filter(InboundCorrelationFilter.java:60)
    at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
    at com.sap.aii.adapter.jms.core.channel.filter.JmsHeadersProfileFilter.filter(JmsHeadersProfileFilter.java:59)
    at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
    at com.sap.aii.adapter.jms.core.channel.filter.MessageInvocationsFilter.filter(MessageInvocationsFilter.java:89)
    at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
    at com.sap.aii.adapter.jms.core.channel.filter.JarmMonitorFilter.filter(JarmMonitorFilter.java:57)
    at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
    at com.sap.aii.adapter.jms.core.channel.filter.ThreadNamingFilter.filter(ThreadNamingFilter.java:62)
    at com.sap.aii.adapter.jms.core.channel.filter.MessageFilterContextImpl.callNext(MessageFilterContextImpl.java:195)
    at com.sap.aii.adapter.jms.core.channel.SenderChannelImpl.doReceive(SenderChannelImpl.java:263)
    at com.sap.aii.adapter.jms.core.channel.ChannelImpl.receive(ChannelImpl.java:437)
    at com.sap.aii.adapter.jms.core.connector.MessageListenerImpl.onMessage(MessageListenerImpl.java:36)
    at com.ibm.mq.jms.MQMessageConsumer$FacadeMessageListener.onMessage(MQMessageConsumer.java:399)
    at com.ibm.msg.client.jms.internal.JmsMessageConsumerImpl$JmsProviderMessageListener.onMessage(JmsMessageConsumerImpl.java:904)
    at com.ibm.msg.client.wmq.v6.jms.internal.MQMessageConsumer.receiveAsync(MQMessageConsumer.java:4249)
    at com.ibm.msg.client.wmq.v6.jms.internal.SessionAsyncHelper.run(SessionAsyncHelper.java:537)
    at java.lang.Thread.run(Thread.java:770)
Caused by: com.sap.aii.messaging.adapter.trans.TransformException: Error converting Message: 'sun.io.MalformedInputException'; nested exception caused by: sun.io.MalformedInputException
    at com.sap.aii.messaging.adapter.Conversion.service(Conversion.java:714)
    at com.sap.aii.af.modules.trans.MessageTransformBean.processTransform(MessageTransformBean.java:538)
    at com.sap.aii.af.modules.trans.MessageTransformBean.processTransform(MessageTransformBean.java:528)
    at com.sap.aii.af.modules.trans.MessageTransformBean.processTransform(MessageTransformBean.java:471)
    at com.sap.aii.af.modules.trans.MessageTransformBean.process(MessageTransformBean.java:364)
    ... 36 more
Caused by: sun.io.MalformedInputException
    at sun.io.ByteToCharUTF8.convert(ByteToCharUTF8.java:270)
    at sun.nio.cs.StreamDecoder$ConverterSD.convertInto(StreamDecoder.java:287)
    at sun.nio.cs.StreamDecoder$ConverterSD.implRead(StreamDecoder.java:337)
    at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:223)
    at java.io.InputStreamReader.read(InputStreamReader.java:208)
    at java.io.BufferedReader.fill(BufferedReader.java:153)
    at java.io.BufferedReader.readLine(BufferedReader.java:316)
    at java.io.LineNumberReader.readLine(LineNumberReader.java:176)
    at com.sap.aii.messaging.adapter.Conversion.convertPlain2XML(Conversion.java:310)
    at com.sap.aii.messaging.adapter.Conversion.service(Conversion.java:709)
    ... 40 more
Any ideas?
Kind regards, Stefan

Hi Stefan,
for the first MTB now we are using only one parameter: Transform.ContentType = text/plain;charset="ISO-8859-1"
The second MTB, which does the XML-Wrapping, is configured like this:
Transform.Class = com.sap.aii.messaging.adapter.Conversion
Transform.ContentType = application/xml
xml.conversionType = SimplePlain2XML
xml.fieldNames = value
xml.fieldSeparator = §%zulu§%
xml.processFieldNames = fromConfiguration
xml.structureTitle = payload
Both CCSID configuration parameters from the "Source"-Tab we've set to 850.
Now, we don't get an error anymore - sun.io.malformedInputException - , but, unfortunately, now special character conversion succeeded (we need an "ß" and we get an ISO-HEX-E1 -> á). E1 is (different from ISO) an "ß" in 850.
Any ideas?

Encoding problem in call-back to hook URL (post parameters)

Hello all,
I'm encountering a character encoding problem while retrieving the content of the shopping basket from one of our provider.
After the POST request is made by the provider to our system using the hook url, when debbuging I can see that some special characters are represented with the sign '#' (after the call the ITS_IMPORT_CONTEXT).
In our case using the parameter http_content_charset with various values, including UTF-8, did not change the result.
Inspecting the HTTP traffic has highlighted the following: the encoding received from the provider is related to UTF-8, but while we are expecting the hexadecimal values, we are receiving the "Unicode code points", which are not recognized by our SAP system. For more details look at the UTF-8 encoding table found here and compare the values under column "Unicode code point" with the one under column "UTF-8 (hex.)".
As an example, for the character 'é', we are receiving the value "%E9" (the code point) instead of receiving the the hexa value : "%C3%A9".
Do you have any idee if this can be corrected on our side or if the provider must addapt the way it's sending the POST parameters?
Many thanks in advance for you help.
Best regards,
Jerome.

Hi Jason,
Indeed I had contacted the provider and informed them about the encoding problem and the fact that passing the parameter http_content_charset had no effect on the sent back encoding.
They have taken into account my request and have changed the encoding used during the request to the HOOK_URL.
Thanks to all of your for your help.
Regards,
Jerome.

C# GWTypeLibrary - AddressBook Entry encoding problem

Hello.
I am using C#(Visual Studio 2005) and GroupWareTypeLibrary to develop for
GroupWise Client 7.0.
Working with AddressBook I have faced some problems.
I am getting display name (AddressBookEntry.DisplayName) for all entries
of AddressBook. Almost all DisplayNames are correct but there are some
problems with two or three of them (there are some illegal char displayed
instead of some char of real user DisplayName). I think it is local
encoding problem bekause I see the same problem with the same users in
GroupWise Client AddressBook.
I thought display name is building not correctly but when I tried to get
these users first and last name I have got the same problem with encoding
in them.
Please advice how to decide this problem.
Regards,
Alex.

Sounds like a GW Client problem and not an API problem if you see it in the client address book. Technical Support should be able to help you.
Glade,
Novell Developer Support

Encoding Problems with WRT300N V2

Hello guys,
i have following problem:
I have a WRT300n Router and it seems to have problems with WPA2 encoding. I have 2 different deviceses (a SMC Ethernet Bridge and a PS3) trying to connect to my Linksys wireless router. No chance in WPA2 mode but when I try in WEP-Mode, both devicec can connect to it.
Are there known encoding problems?
Any idea what i can do?

It is able to use. But my router always drops the connection. WEP is no problem, but ... what about low security and Wirless N is not enabled ??

Encoding problem (via ORB)

Hello,
I posted this problem few months ago, but still havent been able to solve this.
I have a Client Server program which communicates via ORB, i.e. using CORBA, with server running on Solaris OS and Client running on windows.
The server returns string containing chinese characters to the client.
However, my chinese characters dont appear properly on the client side.
If i run the client on the Solaris OS there is no problem with it.
I tried converting the encode of the string by getting its byte and creating
a new string with encoding parameter. None of this seems to work.
I can see the chinese character when the server is writing to OutputStream of CORBA, but on the InputStream of CORBA it does not
show properly.
Any ideas on how i can overcome this encoding problem where the C/S is
communicating via CORBA (ORB)?
Thanks in advance.

Thanks for your reply
Yes, i know the BIG5 is for Traditional Chinese and japansese is using like Shift-JIS or EUC.
So when i try to post japanese in a BIg5 web page, i think it's normal that i can't see it in BIG5 encoding.
But then i change the Safari default decoding to BIG5 HKSCS, the japanese appers! At the same time i can see the traditional chinese too!
And if i use Firefox, i can both see the japanese and chinese at the default BIG5 encoding.
So i simple think maybe safari translate my japanese into BIG5 HKSCS,not Shift-JIS. But if i use Firefox, i can get the same result with only BIG5 encoding, not BIG5 HKSCS. So i am just wondering why it's different between Safari and Firefox with the same BIG5 encoding.
Following is a example URL
It's a MAC discussing froum with BIG5 encoding in Taiwan.
http://ubb.frostyplace.com.tw/viewtopic.php?t=19162
It's a froum topic posted by me. I input some japanese into this topic
If you browse this page with Safari BIG5 encoding, you can see a lot of question mark instead of the original japanese word that i and other people posted.
But if you change the encoding to BIG5 HKSCS, the japanese appears. And if you using Firefox with BIG5 encoding, the japanese appears too.
So is it someing wrong with Safari's BIG5 encoding or some other reason makes this happen?

View Object Encoding problem

I'm using Jdeveloper version 11.1.2.1. I have a encoding problem when creating View Object based on a query. This is my query:
select id, DECODE(id,'11','Индивидуално,'13','Semejno','14','Grupno') naziv
from ins_type
where class_id = '14' and id in ('11', '13', '14')
It is a simple LOV query with cyrilic letters. When I save the ViewObject and re-open it im getting question marks(???????) instead of the cyrilic letters. This only happens in the view object. I dont have other encoding issues when working with cyrilic letters only when im trying to build a View Object based on a query that has cyrilic letters. If i read those values from the database everything is fine
Thanks,

Change the encoding of your application to UTF-8 which appears to be sufficient for cyrilic chars. Here is a quick guide on how to do this http://docs.oracle.com/cd/E17984_01/doc.898/e14693/appa_configuring_jdev.htm
You may also need to update any pages that have encoding explicitly set

SuperDrive and Encoding Problems

Similar Messages

Maybe you are looking for