SJIS- Japan Encoding Issues(*Unable to handle Double Byte Numeric and Spec)

Hi All,
Problem:
Unable to handle Double Byte Numeric and Special Characters(Hypen)
The input
区中央京勝乞田１９４４－２
Output
区中央京勝乞田１９４４?２
We have a write service created based on the JCA (Write File Adapter) with the native schema defined with SJIS Encoding as below.
*<?xml version="1.0" encoding="SJIS"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
     xmlns:nxsd="http://xmlns.oracle.com/pcbpel/nxsd" xmlns:tns="http://nike.com/***/***********"
     targetNamespace="http://nike.com/***/*************"
     elementFormDefault="unqualified" attributeFormDefault="unqualified"
     nxsd:version="NXSD" nxsd:stream="chars" nxsd:encoding="SJIS">*
Do anyone have similar issue? How can we handle the double byte characters while using SJIS encoding? At the least how can we handle double byte hyphen ??
Thanks in Advance

Have modified my schema as shown below and it worked well for me and i am partially successful up to some extent. Yet, not sure the workaround will resolve the issue at the final loading...
<?xml version="1.0" encoding="UTF-8"?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:nxsd="http://xmlns.oracle.com/pcbpel/nxsd" xmlns:tns="http://nike.com/***/***********"
targetNamespace="http://nike.com/***/*************"
elementFormDefault="unqualified" attributeFormDefault="unqualified"
nxsd:version="NXSD" nxsd:stream="chars" nxsd:encoding="UTF-16">*
If anyone has the resolution or have these kind of issues let me know.........

Similar Messages

Handling Double Byte characters

Hi All,
We have a requirement to read Japanese characters from a fixed length file.
The file contains both Single and Double byte characters in a single record.
The file needs to be read by an ABAP program in terms of bytes and it has to be filled into different fields of a structure.
If you have encountered a similar situation , please let me know how it was handled.
Thanks,

Hi,
It isn't possible to say which character use only ony and which two bytes. Are you sure that inside your file these one and two bytes characters are mixed?
Best regards
Marcin Cholewczuk

XSL Transform, double-byte characters and padding

I have a stylesheet with the following variable that is being formatted to pad a parameter named textQualifierDescription to a length of 30 by calling the template called format-string.
<xsl:variable name="textQualifierDescription2">
     <xsl:call-template name="format-string">
          <xsl:with-param name="myString" select="$textQualifierDescription"/>
          <xsl:with-param name="numbatchspaces">30</xsl:with-param>
     </xsl:call-template>
</xsl:variable>
<xsl:template name="format-string">
     <xsl:param name="myString" select="' ' "/>
     <xsl:param name="numbatchspaces" select="20"/>
     <xsl:param name="direction" select="right"/>
     <xsl:variable name="spacesstr" select="string('                                              ')"/>
     <xsl:variable name="padsize" select="$numbatchspaces -string-length($myString)"/>
     <xsl:variable name="spacepad" select="substring($spacesstr, 1, $padsize)"/>
     <xsl:choose>
          <xsl:when test="$direction = 'left'">
               <xsl:value-of select="concat($spacepad,$myString)"/>
          </xsl:when>
          <xsl:otherwise>
               <xsl:value-of select="concat($myString,$spacepad)"/>
          </xsl:otherwise>
     </xsl:choose>
</xsl:template>I execute the xsl transform using the following statement in a stored procedure:
transformedData := xmldata.transform(xsldata);The xsl transform works as expected until it encounters data that contains double-byte characters. My output is supposed to contain the following three fields as a single record
textQualifierDescription - padded to a length 30
lineNumber
id
If my textQualifierDescription contains a value of "Texto de posición"
Line 1 - Texto de posición             00000001POS2005
Line 2 - Texto de posición            00000001POS2005
Line 1 is the expected result.
Line 2 is the actual result. When the "format-string" function is called and even though "Texto de posición" is 17 characters in length, it looks as if oracle counts the double-byte character as 2 and calculates the string-length as 18 to come up with a padsize of 12. It then creates a spacepad of 12 spaces which is then concatenated to the 17 characters for a total length of 29. I have tested the stylesheet in xmlspy and it produces the expected result.
Has anyone ever run into this sort of situation and is able to provide me with some sort of solution to this dilemma? This is running on 10g Release 10.2.0.4.0.

Your searches should have also come up with the fact that CR XI R2 is not supported in .NET 2008. Only CR 2008 (12.x) and Crystal Reports Basic for Visual Studio 2008 (10.5) are supported in .NET 2008. I realize this is not good news given the release time line, but support or non support of cr xi r2 in .net 2008 is well documented - from [Supported Platforms|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/7081b21c-911e-2b10-678e-fe062159b453
] to [KBases|http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes_boj/sdn_oss_boj_dev/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/scn_bosap/notes.do], to [Wiki|https://wiki.sdn.sap.com/wiki/display/BOBJ/WhichCrystalReportsassemblyversionsaresupportedinwhichversionsofVisualStudio+.NET].
Best I can suggest is to try SP6:
https://smpdl.sap-ag.de/~sapidp/012002523100015859952009E/crxir2win_sp6.exe
MSM:
https://smpdl.sap-ag.de/~sapidp/012002523100000634042010E/crxir2sp6_net_mm.zip
MSI:
https://smpdl.sap-ag.de/~sapidp/012002523100000633302010E/crxir2sp6_net_si.zip
Failing that, you will have to move to a supported environment...
Ludek
Follow us on Twitter http://twitter.com/SAPCRNetSup
Edited by: Ludek Uher on Jul 20, 2010 7:54 AM

Safari 3(PC) can't handle double-byte characters

I used Safari to browse a Chinese web site. However, there was a lot of BLANK SPACE coz Safari can't show the Chinese contents. Later, I noticed that Safari can't handle those html content that use non-English for the fontface name. If I change the font-face name to English(still the same Chinese font), Safari can display the content. However, it didn't use the font-face.

I am running a windows xp. It is a microsoft XP professional(5.1 build 2600)
intel celeron 1.1ghz
with a 254mb of ram( that is part of a ram card)
I am not running windows 95 it's just my pc is quite old.
I downloaded the flash player 10 archive nothing else but the 10th version and I installed the newest version it had on there.
If there is a better option please tell me. thanks
edit: i am using mozzilla firefox the newest version of it.
Ok I'd like to say this now I pressumed my pc couldn't handle flash palyer 10.3 since the requirments asked ofr higher specs.
AND right before I tried to install it igot rid of my old flash palyer 10 and adobe flash activex.
After that I tried to install the program for firefox yet after I pressed run NOTHING appeared and firefox was off. I keep getting a error that says it couldn't connect or run a script or something from internet explorer.
I've been having these random script errors latly too.
Yet I have cleared up my pc and recently ran anti-malware, anti-virus, and defragmentaion scans,etc and more. (Avast piriform malwarebytes). SO every tiemi did this the program would run underprocesses but it would do absolutly NOTHING so I end up having to stop the process. Each time itry to install it it deletes it'self orsomthing as well from the file I downloaded it to though i pressume that is normal
Unless my problem lies more in the program then my pc then I'm ok.

Java to Excel encoding issue.

I'm trying to export my data in to Excel file. When I open the excel file the Japanese characters looks garbled.
iResponse.setHeader("attachment ; filename = \"" + reportFileName() + "\" ", "content-disposition");
iResponse.setHeader("application/vnd.ms-excel;","content-type");
iResponse.setHeader("UTF-8","Content-Encoding");
By Googling I learnt that Excel doesn't like UTF-8 format. Is there any other way I can export the data.
Thanks.

Specifying the content encoding for a binary format like Excel is pointless. You are producing native Excel format, aren't you? If you're producing a CSV file and claiming it's Excel, you should have mentioned that.
Anyway: you're producing native Excel using something like Apache POI, I suppose? I would have thought it handled encoding issues, but check its documentation or its FAQ to see if that's really the case.
Another option, which may or may not be feasible, is to use the new Office 2007 format. It's based on XML, so all of the encoding issues are automatically handled.

Column Encoding issue for user spreadsheet import via Wizard

Hi,
I'm trying to build an upload page for users, they should be able to upload spreadsheets into one of the tool's table.
I have built a "Data Load Page" via the Wizard on apex.oraclecorp.com which created 4 pages : data load, data/table mappings, data validation and data load results.
I do receive the correct mappings, however because some characters are double byte, hispanish and so on, I do receive weird characters in my rows. This data looks well in CSV (I save it in txt first as unicode text). Is there a way that I can force apex to grab my import and see char encoding as little endian?
Thanks and regards,
Diez

Hi again,
Are there no solutions for this?
I would simply like to make available to the user an option where he can change the character encoding (like UTF-8, little endia, big endian, western european windows etc) or make it little endian by default.
If this is not possible I'm open to any suggestions.
Thanks and regards,
Diez
Edited by: 837311 on Dec 16, 2011 5:26 AM

Double byte chracter sets

Can anyone verify the Forte 3.0.F.x supports double byte? I am looking
primarily at Japanese.
Greg Fuller

Greg,
Forte is fully localized for Japanese. This means
-Forte can handle Double byte (SJIS, EUC, DEC KANJI) codesets.
-Applications written in Forte can also handle multibyte
codesets.
-Our runtime messages are fully translated into japanese.
-Our developer UI (the workshops) are fully translated.
-Our manual set has been translated into Japanese.
-Forte Education Courses have been translated as well.
We have over 30 customers in Japan using multi byte Forte.
Let me know if you have any specific questions I can
answer for you.
Doug Welch
Manager, Technical Services
Forte Asian Operations
From: Greg Fuller <[email protected]>
Subject: Double byte chracter sets
Can anyone verify the Forte 3.0.F.x supports double byte? I am looking
primarily at Japanese.
Greg Fuller

PDF acceleration F5 BigIP WA and double byte characters

We have been trying to use the F5 appliance from BigIP to accelerate the delivery of PDF files from SharePoint over the WAN. However, we encountered problems with the double-byte files many months ago and have been trying to resolve the problem with F5. We have turned off PDF acceleration on the F5 because of the problems. The problem occurs when PDF files have Kanji characters in the file name. If the file names are English (single byte) the problem does not occur, even if the content of the PDF contains Kanji characters.
After many months of working with F5, they are now saying that the problem is with the Adobe plug-in to Internet Explorer. Specifically they say:
The issue is a result of Adobe's (not F5's) handling of the linearization request of PDF’s with the Japanese character set over 300 KB when the Web Accelerator is enabled on the BigIP (F5) appliance. We assume the issue exists for all double-byte languages, not only Japanese. If a non-double byte character set is used, this works fine. “Linearization” is a feature which allows the Adobe web plug-in to start displaying the PDF file while it is still being downloaded in the background.
The F5 case number is available to anybody from Adobe if interested.
The F5 product management and the F5 Adobe relationship manager have been made aware of this and will bring this issue up to Adobe. But this is as far as F5 is willing to pursue as a resolution. F5 consider this an Adobe issue, not a F5 issue.
Anybody know if this is truly a bug with the PDF browser plug-in? Anybody else experienced this?

Your searches should have also come up with the fact that CR XI R2 is not supported in .NET 2008. Only CR 2008 (12.x) and Crystal Reports Basic for Visual Studio 2008 (10.5) are supported in .NET 2008. I realize this is not good news given the release time line, but support or non support of cr xi r2 in .net 2008 is well documented - from [Supported Platforms|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/7081b21c-911e-2b10-678e-fe062159b453
] to [KBases|http://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/oss_notes_boj/sdn_oss_boj_dev/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/scn_bosap/notes.do], to [Wiki|https://wiki.sdn.sap.com/wiki/display/BOBJ/WhichCrystalReportsassemblyversionsaresupportedinwhichversionsofVisualStudio+.NET].
Best I can suggest is to try SP6:
https://smpdl.sap-ag.de/~sapidp/012002523100015859952009E/crxir2win_sp6.exe
MSM:
https://smpdl.sap-ag.de/~sapidp/012002523100000634042010E/crxir2sp6_net_mm.zip
MSI:
https://smpdl.sap-ag.de/~sapidp/012002523100000633302010E/crxir2sp6_net_si.zip
Failing that, you will have to move to a supported environment...
Ludek
Follow us on Twitter http://twitter.com/SAPCRNetSup
Edited by: Ludek Uher on Jul 20, 2010 7:54 AM

JSF and Double Byte Character

Hi,
I wanted to know how to handle <h:outputText> with chinese character or double byte character.
See sample code below :
<%@ page language="java" contentType="text/html; charset=UTF-8" pageEncoding="UTF-8"%>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<h:form styleClass="form" id="form1">
<% request.setCharacterEncoding("UTF-8"); %>
<h:inputText styleClass="inputText" id="text1"></h:inputText>
<hx:commandExButton type="submit" value="Submit" styleClass="commandExButton" id="button1" action="#{pc_SubmitTest.doButton1Action}"></hx:commandExButton>
<h:outputText styleClass="outputText" id="text2"></h:outputText>
</h:form>
When you input with double byte character and submit,
the output screen value did not render properly .
I tried this similiar code at JSP, it work fine.
Anybody know how to solve this problem ?
Anything need to do at pagecode level ?
Thank you.
Reinardy

Problem was due to the fact that I was trying to generate the excel file in char stream instead of byte stream

Double-byte parser

Hey,
I need to load in 400 character string of data into text using the FM SAVE_TEXT in chucks of 60 characters. If the user logs in Japanese, they could be loading in a mix of single byte and double characters. I need to be able to check if I break my string of data at the 60th character, will I be corrupting a double character.
Does anyone know how to perform this test in ABAP?
Thanks for the feedback! Bill

Hi Bill,
If you are on version 6.2+ you could try using the NUMOFCHAR( ) command.
I guess you could do something like:
* First determine the number of actual
* characters in 60th and 61st bytes.
w_num_of_chars = NUMOFCHAR( w_text+60(2) ).
* If there is only 1, then split on 59.
IF w_num_of_chars = 1.
* Otherwise, we have two characters so we can split at 60.
ELSE.
ENDIF.
I must admit I'm a complete novice when it comes to double byte languages and their handling, so that may just be complete gobbledegook.
Hope that helps.
Cheers,
Brad

How to check double byte characters

Hi
My requirement: I have to accept the string (may include double byte characters and special characters). Need to check that wether that string contains any special characters(like %,&,..), if so should display error message.
My solution: Starting i tried by usign the ASCII values. But the my code dividing the Double Byte characters into two characters.
Code:
package JNDI;
public class CharASCIIValues {
     public static void main(String[] args) {
          // TODO Auto-generated method stub
          String s = args[0];
          char ch[] = s.toCharArray();
          for(int i=0;i<=ch.length;i++){
               System.out.println(" "+ch[i]+"="+(int)ch);
I ran with some double characters (japanese)
But i got the out put was = ?=63 ?=63 ?=63 ?=63 ?=63 ?=63 1=49 2=50 3=51 h=104 e=101 l=108 l=108 o=111
The ? are double byte charcters.
Queries:
Do i need to set any java setting to support DB characters.
Please help me to come out this problem....any help/information will be appreciated.

First of all Java strings are encoded in a modified version of UTF-8 that uses 2 bytes per character. That is the char datatype is equivalent to an unsigned short.
Second what exactly do you mean by double byte? Whether a character ends up encoded in two bytes or not depends on the encoding used (UTF-8, UTF-16 (both unicode), BIG5, GB2312 (both chinese), iso-8859-1(Latin-1), ASCII, etc...). This means that there are no "double byte characters" there are only "double byte characters when encoded in <your encoding>".
Where does your string come from? What encoding are you using to read the string in the first place? Are you sure you are creating the string using the right encoding?

Double Byte Characters for Japanese Kanji Language

Hello All,
How can you identify the Double Byte characters and how we can check whether they are double byte characters or not.
Can you please tell me the double byte characters from Japanese Kanji language for the characters.
This is very urgent.I will reward you with points.
Thanks,
Karan

*& Report YTEST_LOGIC
REPORT teched_unicode_solution_1               .
*** Exercise 1: Distinction between byte and character length
*** after Unicode enabling
parameter: param type c.
PERFORM test1 USING param.
* FORM test1
FORM test1 USING text TYPE c.
DATA: len1 TYPE i,
        len2 TYPE i,
        off TYPE i.
DESCRIBE FIELD text LENGTH len1 IN BYTE MODE.
DESCRIBE FIELD text LENGTH len2 IN CHARACTER MODE.
WRITE:/ LEN1, LEN2.
ENDFORM.                                                    "test1
Use the above code to find which characters are double bytes and which are not...
The double byte characters will have double the length when they are in the byte mode..
reward points for helpful answers
Edited by: Rahul Kavuri on Mar 26, 2008 6:35 PM

Double byte capability

Hi,
Can any one tell me what is Double byte capability in SAP

No Double byte font and variable are differnt ....
Pl... Refer the following links
http://help.sap.com/saphelp_erp2005/helpdata/en/62/3f2cb0b35311d5993800508b6b8b11/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/a0/c49b54323e4a99bfa7ea400c7e67e1/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/e2/5a131fde7c11d5994e00508b5d5211/frameset.htm
Hope thisll give you idea!!
<b>P.S award the points.</b>
Good luck
Thanks
Saquib Khan
"Some are wise and some are otherwise"

Application Issue - Adobe connect unable to handle "unreachable" responses

Hi,
We've discovered what seems to be a bug with the Adobe Connect application/flash player.
For some reason when you have a proxy in place adobe connect still attempts to establish a direct connection to the adobe servers (for example na7fms2.adobeconnect.com), if these packets get dropped video plays with no issue.
However in our case we have ACL's setup on our Cisco routing core (which do not allow this traffic), which in turn respond with "Destination Unreachable (Communication administratively filtered)".
Adobe Connect seems to be unable to handle these responses and goes into a loop continiously attempting a direct connection (around every 10-12 seconds), therefore causing streaming video's to restart every 10-12 seconds.
Below is a screenshot of the packet capture of the accurance.
Basically we managed to create two of the following scenarios in our network.
Video restarts every 10-12 seconds:
Video plays with no issues:
Now this "Destination Unreachable" response is completely legal in terms of RFC http://www.ietf.org/rfc/rfc792.txt
It would be great if this issue could be raised as a bug and fixed in future versions.
Thanks,
Daniil

Seeing the same issue. Did anyone find any solution?.
Only solution that I could see was opening HTTPS at firewall for only Adobe Connect servers. Wasn't able to locate anything that published the network ranges for the Adobe Connect servers however. Wasn't really a solution that I was happy with anyway.
Only need to do this to allow 1 employee to access a recorded Adobe Connect meeting.
Thanks
Iain.

Encoding Issue : JMS and Mapping : utf-8 iso8859-1

Hi All,
I am facing some problem with encoding issue.
Scenario : JMS --> SAP PI --> JMS
Requirment : Input plain text file contain some special characters,"©®" . Based on this condition,In Java Mapping
                   we check the Payload and changed the 'encoding' tag to UTF-8 or   ISO8859-1.
               : <?xml version="1.0" encoding="UTF-8"?>     in the target XML output.
While testing in Operation mapping our Java mapping works fine. as the encodeing tag changes from
             UTF-8 to ISO8859-1 if the special character exists.But if I test the same in Integration Directory(Test Configuration)
             or did a end to end testing. The encoding tag did'nt changes.
For testing we had to a set of Plain Text files with UTF-8 and ISO8859-1 .
I tried the options of using beans in Adapter modules in Sender JMS channel.
MessageTransformBean, TextCodepageConversionBean, XmlAnonymizerBean
These doc & threads ,was also referred[How to Handle Encoding in PI|http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/502991a2-45d9-2910-d99f-8aba5d79fb42]
Regards,
Ashutosh R

Hi
public static boolean fixSpecialCharforWeb(String text) {
        int i = 0;
        Character c = null;
        char[] ctext = null;
        StringBuffer newText = new StringBuffer("");
        //boolean encodingType = false;
        if ((text == null) || (text.trim().length() == 0)) {
            return encodingType;
        } else {
            try {
                               for (i = 0; i < text.trim().length(); i++) {
                    ctext = text.trim().substring(i, i + 1).toCharArray();
                    c = new Character(ctext[0]);
                    //Single quote
                    if ((text.trim().substring(i, i + 1).equals("'")) || (c.hashCode() == 8217) || (text.trim().substring(i, i + 1).equals("?")) || (c.hashCode() == 146) || (c.hashCode() == 145)) {
                        //newText.append("'");
                        encodingType = true;
                        return encodingType;
                    //Double quotes
                    if ((c.hashCode() == 8220) || (c.hashCode() == 8221) || (c.hashCode() == 147) || (c.hashCode() == 148)) {
                        //newText.append(""");
                        encodingType = true;
                        return encodingType;
                    // bullet point
                    if ((c.hashCode() == 8226) || (c.hashCode() == 149)){
                        encodingType = true;
                        return encodingType;
                    // tilde
                    if ((c.hashCode() == 732) || (c.hashCode() == 152)){
                        encodingType = true;
                        return encodingType;
                    // Soft Hypen
                    if (c.hashCode() == 173){
                        encodingType = true;
                        return encodingType;
                    // En-Dash
                    if ((c.hashCode() == 8211) || (c.hashCode() == 150)) {
                        encodingType = true;
                        return encodingType;
                    // Em-Dash
                    if ((c.hashCode() == 8212) || (c.hashCode() == 151)) {
                        encodingType = true;
                        return encodingType;
                    // Euro Sign
                    if ((c.hashCode() == 8364) || (c.hashCode() == 128)) {
                        encodingType = true;
                        return encodingType;
                    // Yen Sign
                    if (c.hashCode() == 165) {
                        encodingType = true;
                        return encodingType;
                    // Pound Sign
                    if (c.hashCode() == 163) {
                        encodingType = true;
                        return encodingType;
                    // 1/2 sign
                    if (c.hashCode() == 189) {
                        encodingType = true;
                        return encodingType;
                    // 1/4 sign
                    if (c.hashCode() == 188) {
                        encodingType = true;
                        return encodingType;
                    // 3/4 sign
                    if (c.hashCode() == 190) {
                        encodingType = true;
                        return encodingType;
                    // Sword/dagger
                    if ((c.hashCode() == 8224) || (c.hashCode() == 134)) {
                        encodingType = true;
                        return encodingType;
                    // Trademark
                    if ((c.hashCode() == 8482) || (c.hashCode() == 153)) {
                        encodingType = true;
                        return encodingType;
                    // Ampersand &
                    if ((text.trim().substring(i, i+1).equals("&")) || (c.hashCode() == 38)) {
                        encodingType = true;
                        return encodingType;
                    //Registered mark
                    if ((text.trim().substring(i, i + 1).equals("?")) || (c.hashCode() == 174)) {
                        //newText.append("®");
                        encodingType = true;
                        return encodingType;
                    //Copyright mark
                    if ((text.trim().substring(i, i + 1).equals("?")) || (c.hashCode() == 169)) {
                        encodingType = true;
                        return encodingType;
                    // Question.
                    if (c.hashCode() == 63 && c.toString().equals("?")){
                        //newText.append("?");
                        encodingType = true;
                        return encodingType;
                    //handling symbol ?
                    if ((text.trim().substring(i, i+1).equals("?")) || (c.hashCode() == 233)) {
                        encodingType = true;
                        return encodingType;
                    if ((text.trim().substring(i, i+1).equals("?")) || (c.hashCode() == 232)) {
                        encodingType = true;
                        return encodingType;
                    if (c.hashCode() == 144) {
                        encodingType = true;
                        return encodingType;
            } catch (Exception e) {
                e.printStackTrace();
        return encodingType;

SJIS- Japan Encoding Issues(*Unable to handle Double Byte Numeric and Spec)

Similar Messages

Maybe you are looking for