Registered schema lost one byte of Chinese character at certain position

Hello all,
I registered a schema as below. When viewing the registered schema in the Enterprise Manager, I found a byte was lost for the Chinese character at the position of byte 4200 ( or 0x1068 ).
before registration:
22 B2 FA C6 B7 CA FD C1 BF B5 A5 CE BB 22 20 ; "产品数量单位"
after registration:
22 B2 FA C6 B7 FD C1 BF B5 A5 CE 3F 20 ; "产品康ノ?
My database (9.2.0.1 & 9.2.0.3) has the character set of SIMPLIFIED CHINESE_CHINA.ZHS16GBK.
Connect test/test;
DECLARE
samplexmldoc clob := '<?xml version="1.0" encoding="GB2312"?>
<xs:schema xmlns:xdb="http://xmlns.oracle.com/xdb" xmlns:xs="http://www.w3.org/2001/XMLSchema">
     <!--This is a test This is a test This is a test -->
     <!--This is a test This is a test This is a test -->
     <!--This is a test This is a test This is a test -->
     <!--This is a test This is a test This is a test -->
     <!--This is a test This is a test This is a test -->
     <!--This is a test This is a test This is a test -->
     <!--This is a test This is a test This is a test -->
     <!--This is a test This is a test This is a test -->
     <!--This is a test This is a test This is a test -->
     <!--This is a test This is a test This is a test -->
     <!--This is a test This is a test This is a test -->
     <!--This is a test This is a test This is a test -->
     <!--This is a test This is a test This is a test -->
     <!--This is a test This is a test This is a test -->
     <!--This is a test This is a test This is a test -->
     <!--This is a test This is a test This is a test -->
     <!--This is a test This is a test This is a test -->
     <!--This is a test This is a test This is a test -->
     <!--This is a test This is a test This is a test -->
     <!--This is a test This is a test This is a test -->
     <!--This is a test This is a test This is a test -->
     <!--This is a test This is a test This is a test -->
     <!--This is a test This is a test This is a test -->
     <!--This is a test This is a test This is a test -->
     <!--This is a test This is a test This is a test -->
     <!--This is a test This is a test This is a test -->
     <!--This is a test This is a test This is a test -->
     <!--This is a test This is a test This is a test -->
     <!--This is a test This is a test This is a test -->
     <!--This is a test This is a test This is a test -->
     <!--This is a test This is a test This is a test -->
     <!--This is a test This is a test This is a test -->
     <!--This is a test This is a test This is a test -->
     <!--This is a test This is a test This is a test -->
     <!--This is a test This is a test This is a test -->
     <!--This is a test This is a test This is a test -->
     <!--This is a test This is a test This is a test -->
     <!--This is a test This is a test This is a test -->
     <!--This is a test This is a test This is a test -->
     <!--This is a test This is a test This is a test -->
     <!--This is a test This is a test This is a test -->
     <!--This is a test This is a test This is a test -->
     <!--This is a test This is a test This is a test -->
     <!--This is a test This is a test This is a test -->
     <!--This is a test This is a test This is a test -->
     <!--This is a test This is a test This is a test -->
     <xs:element name="产品目录">
          <xs:complexType xdb:SQLType="ST产品目录">
               <xs:sequence>
                    <xs:element ref="第一种产品目录"/>
               </xs:sequence>
          </xs:complexType>
     </xs:element>
     <xs:element name="第一种产品目录">
          <xs:complexType xdb:SQLType="ST第一种产品目录">
               <xs:sequence>
                    <xs:element name="产品分类名称" type="xs:string"/>
                    <xs:element name="产品分类概况" type="xs:string"/>
                    <xs:element name="产品数量单位" type="xs:string"/>
                    <xs:element name="产品存放总分布图" type="xs:anyURI"/>
                    <xs:element name="产品样本" type="xs:anyURI"/>
               </xs:sequence>
          </xs:complexType>
     </xs:element>
</xs:schema>
BEGIN
dbms_xmlschema.registerSchema('http://www.antu.com.cn/metaxml.xsd',samplexmldoc,True,True,False,FALSE);
End;
Because we have to generate schemas by program, it's not acceptable to adjust the schema text manually.
What shall I do? Thanks for any help.
Chen Hui

Please open a tar with your local support organization...
Chen
Please excuse me if I ask some basic questions here, I've no previous experience working with documents containing Chinese Character sets.
I assume that if I look at your post with my Brower character set to simplifiedChinese.GB2312 I will see the schema document posted correctly..
Can you test wether or not this problem occurs if the document is encoded in UTF8 and loaded into an AL32UTf8 database. Also, do you see , rather than GB2312. Also are the characters still missing if you view it from SQL*PLUS...

Similar Messages

  • Does one Simplied Chinese character occupy 1 bype in SAPscript in Ecc6.0?

    Recently,we upgraded our SAP system from R3 4.6C to ECC6.0. But one simplied chinese character occupy 1 byte when I printed a sapscript form.
    It means that a field which length is 12 bytes can output 12 simplied chinese  character, otherwise it could only output 6 simplied chinese character in R3 4.6C.
    I don't know why? Cany anybody tell me?

    Does nobody know how to solve it?

  • GUI_DOWNLOAD give 2 bytes for each chinese character - I need fixed length

    Due to the Unicode system takes each Chinese character as a byte, the field(10) can take 10 Chinese Characters, not like before only 5 characters allowed.
    The problem is when the data is downloaded to a txt file. Some records contains only Western Europe charactes and will fill 10 bytes in the output file and other records contains only Chinese characters and will fill up 20 bytes in the output file.
    The data is exported for a system that can upload chinese characters, but only allow fixed record length file (always 10 bytes).
    In other words: the records with Western Europe characters should contain 10 characters = 10 bytes but the records with Chinese characters should only contain 5 characters = 10 bytes.
    Anyone who can solve this, thanks in advance.
    My code:
      CALL METHOD CL_GUI_FRONTEND_SERVICES=>GUI_DOWNLOAD
        EXPORTING
          FILENAME                = p_file
          CONFIRM_OVERWRITE       = 'X'
          codepage                = '8400' "Chinese
        CHANGING
          DATA_TAB                = it_output
        EXCEPTIONS

    Hi Thomas,
    Now I understand.
    Pl. check the class CL_ABAP_CONV_X2X_CE.
    May it can help u.
    Here is it's documentation.
    CL CL_ABAP_CONV_X2X_CE
    Short Text
    Code Page and Endian Conversion Between External Formats
    Functionality
    Instances of the class CL_ABAP_CONV_X2X_CE allow you to convert text data between different character sets and numeric data between different number formats (byte order).
    Using the class corresponds to transforming data from a binary input stream to a binary output stream: The data objects are read from the input buffer sequentially and written to an output buffer.
    The class methods are normally used as follows:
    CL_ABAP_CONV_X2X_CE=>CREATE
    This creates a conversion instance. Among other options, you can specify the following as parameters: The input buffer (that is the binary string that contains the data to be read), the character format at used in the input buffer, the byte order used in the input buffer, the character format to be used in the output buffer, or the byte order to be used in the output buffer.
    CONVERT_C, CONVERT_...
    This converts the data. Calling this method several times consecutively allows you to read data from the input buffer sequentially and add it to the end of the output buffer.
    GET_OUT_BUFFER
    This gets the output buffer, making it available for further processing (such as writing to a file, sending using RFC).
    RESET
    This allows you to reset individual attributes of the conversion instance. (This method is especially designed for restarting on a new input buffer and deleting the output buffer while retaining the remaining attributes.)
    Relationships
    CL_ABAP_CONV_IN_CE
    Converting Binary Data into ABAP Data Objects
    CL_ABAP_CONV_OUT_CE
    Converting ABAP Data Objects to a  Binary Format.
    CL_ABAP_CHAR_UTILITIES
    Various Attributes and Methods for Character Sets and Byte Order
    Example
    In the following example, UTF-8 texts are converted to the codepage 1100 (Latin-1) and numbers are converted from little-endian to big-endian format:
    DATA:
      in_buffer TYPE XSTRING,
      out_buffer TYPE XSTRING,
      conv TYPE REF TO cl_abap_conv_x2x_ce.
    in_buffer = '414220C3B602010000'.
    conv = cl_abap_conv_x2x_ce=>create(
             in_encoding = 'UTF-8'
             in_endian = 'L'
             out_encoding = '1100'
             out_endian = 'B'
             input = in_buffer
    CALL METHOD conv->convert_c( n = 5 ).
    CALL METHOD conv->convert_i( ).
    out_buffer = conv->get_out_buffer( ).
    The content of the in_buffer variable is made up of  5 bytes (hexadecimal "414220C3B6"), which represent 4 UTF-8 characters (A, B, SPACE, o-Umlaut), and 4 bytes (hexadecimal "02010000"),  which represent the value 258 in little-endian format. This data is converted and the out_buffer variable now contains the hexadecimal string "414220F600000102". It is made up of:
    4 bytes (hexadecimal "414220F6"), which represent the above  4 characters in codepage 1100 (ISO-8859-1). Note that the length specification n = 5 refers to the number of elementary characters to be converted. For multi-byte codepages like UTF-8 this means that the multi-byte character "C3B6" is counted in length 2.
    4 Bytes (hexadecimal "00000102"), which represent the value 258 in big-endian format.
    If you have the desired byte order in the old format as expected by TRANSLATE ... NUMBER FORMAT (as an N(4) value), you can proceed as follows:
    TYPE-POOLS: ABAP.
    CLASS cl_abap_char_utilities DEFINITION LOAD.
    DATA:
      in_number_format(4) TYPE N VALUE '0101',
      out_number_format(4) TYPE N VALUE '0000'.
    DATA:
      in_endian TYPE ABAP_ENDIAN,
      out_endian TYPE ABAP_ENDIAN,
      conv TYPE REF TO cl_abap_conv_x2x_ce..
    in_endian  = cl_abap_char_utilities=>number_format_to_endian(
                   in_number_format
    out_endian = cl_abap_char_utilities=>number_format_to_endian(
                   out_number_format
    conv = cl_abap_conv_x2x_ce=>create(
             in_encoding = 'UTF-8'
             in_endian = in_endian
             out_encoding = '1100'
             out_endian = out_endian
             input = in_buffer
    Notes
    For details refer to the documentation for the individual methods.
    Regards,
    Joy.

  • In ECC6.0,why chinese character is 1 byte?

    Dear experts,
    In our current project, SAP version is ECC 6.0. In my program, I found chinese character only is 1 byte, for example:
    data: l_char(20) type c.
    l_char = '&#21271;&#20140;'.
    l_char+4(6) = '&#27426;&#36814;&#24744;'.
    write: l_char.
    The result is: &#21271;&#20140;  &#27426;&#36814;&#24744;
    There are two blanks after '&#21271;&#20140;'.
    So it will cause problem, I can't control the display length of the string because the number of chinese charater in this string is variable.
    Why the chinese character only is 1 byte in our system?
    Thanks in advance.
    Sam

    Dear Rich,
    Could you please help me to resolve this problem or please give me some suggestion.
    Thanks a lot
    Sam

  • Data upload Vendor Master Chinese character from Excel does not upload

    Hi Gurus,
    We are trying to upload Vendor Master from Excel sheet.
    The Chinese characters in excel sheet is not getting uploaded.
    After upload, we see in SAP as ????? for these Chinese character.
    Could any one inform what setting I may need to change?
    Thanks and Best Regards,
    Mohan

    Hi Bala,
    Goto he Initial screen of SAP and click the ALT+F12    costomizating of local setup.the choose the options-->choose the I18N Tab in that POP up and check the Activate the multi byte support.
    press Apply and OK.
    close the  SAP Log on and Re-loag on.if u r not closing the Logon screen the changes wiil not effect.
    or
    click on the log on SAP and choose the server  name -->right click ->Properties>chose the log on language as chanies .-->Apply and Logon.
    Now u can eassily Upload to the Excel in checnies language.
    Thanks & REgards,
    Nelson.

  • How can i convert jstring to PSTR with chinese character

    Hi all,
    I'm not an expert of C++. So please help me to fix the following problem.
    I'm using jni to call the dll. In java side, the input parameter is jstring. In C++ side, the input parameter of PrintDrugReceipt are PSTR.
    The following is the code of my C++:
    #include <windows.h>
    #include <stdio.h>
    #include <jni.h>
    #include "DrugReceiptWrapper.h"
    #include "DrugReceipt.h"
    const char * JNU_GetStringNativeChars(JNIEnv *env, jobject obj, jstring jstr) {
    jbyteArray bytes = 0;
    jthrowable exc;
         jclass cls;
         jmethodID getBytes;
    char *result = 0;
    if ((*env)->EnsureLocalCapacity(env, 2) < 0) {
    return 0; /* out of memory error */
         cls = (*env)->GetObjectClass(env, obj);
         getBytes = (*env)->GetMethodID(env, cls, "getBytes","()[B");
         //jbyteArray buf = (jbyteArray*)(*env)->CallObjectMethod(env, obj, jlprSourceChiName, getBytes);
         bytes = (*env)->CallObjectMethod(env, jstr, getBytes);
         exc = (*env)->ExceptionOccurred(env);
         if (!exc) {
             jint len = (*env)->GetArrayLength(env, bytes);
             result = (char *)malloc(len + 1);
             if (result == 0) {
                 //JNU_ThrowByName(env, "java/lang/OutOfMemoryError", 0);
                 (*env)->DeleteLocalRef(env, bytes);
                 return 0;
    (*env)->GetByteArrayRegion(env, bytes, 0, len, (jbyte *)result);
    result[len] = 0; /* NULL-terminate */
    } else {
    (*env)->DeleteLocalRef(env, exc);
    (*env)->DeleteLocalRef(env, bytes);
    return result;
    JNIEXPORT jlong JNICALL
    Java_TestPrint_PrintDrugReceiptWrapper(
    JNIEnv *env, jobject obj,
    jstring jlprPrinterPort, jstring jlprSourceChiName,
    jstring jlprTargetChiName, jstring jlprPrintData1,
    jstring jlprPrintData2, jstring jlprCaseNo, jstring jlprReceiptNo){
         PSTR lprPrinterPort;
         PSTR lprSourceChiName;
         PSTR lprTargetChiName, lprPrintData1;
    PSTR lprPrintData2 , lprCaseNo, lprReceiptNo;
         printf("before %s", jlprSourceChiName);
         lprPrinterPort = (*env)->GetStringChars(env, jlprPrinterPort , 0);
         lprSourceChiName = (*env)->GetStringChars(env, jlprSourceChiName, 0);     
         lprTargetChiName = (*env)->GetStringChars(env, jlprTargetChiName, 0);
         lprPrintData1 = (*env)->GetStringChars(env, jlprPrintData1 , 0);
         lprPrintData2 = (*env)->GetStringChars(env, jlprPrintData2 , 0);
    lprCaseNo = (*env)->GetStringChars(env, jlprCaseNo , 0);
         lprReceiptNo = (*env)->GetStringChars(env, jlprReceiptNo , 0);
         PrintDrugReceipt(lprPrinterPort, lprSourceChiName, lprTargetChiName, lprPrintData1, lprPrintData2, lprCaseNo, lprReceiptNo);
         (*env)->ReleaseStringChars(env, jlprPrinterPort , lprPrinterPort);
         (*env)->ReleaseStringChars(env, jlprSourceChiName, lprSourceChiName);
         (*env)->ReleaseStringChars(env, jlprTargetChiName, lprTargetChiName);
         (*env)->ReleaseStringChars(env, jlprPrintData1 , lprPrintData1);
         (*env)->ReleaseStringChars(env, jlprPrintData2 , lprPrintData2);
         (*env)->ReleaseStringChars(env, jlprCaseNo , lprCaseNo);
         (*env)->ReleaseStringChars(env, jlprReceiptNo , lprReceiptNo);
         return 1;
    the h file:
    /* DO NOT EDIT THIS FILE - it is machine generated */
    #include <jni.h>
    /* Header for class TestPrint */
    #ifndef _Included_TestPrint
    #define _Included_TestPrint
    #ifdef __cplusplus
    extern "C" {
    #endif
    * Class: TestPrint
    * Method: PrintDrugReceipt
    * Signature: (Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;)J
    JNIEXPORT jlong JNICALL Java_TestPrint_PrintDrugReceiptWrapper
    (JNIEnv *, jobject, jstring, jstring, jstring, jstring, jstring, jstring, jstring);
    #ifdef __cplusplus
    #endif
    #endif
    Note: the jstring input parameters are the chinese character. If i print out the jstring, it will display dirty character, why? and how to fix it? and the PrintDrugReceipt will expected accept the chinese character and print it to the printer.
    Thank you for you guys help.
    Matthew

    you can't use char...have to use a wchar....and look around at the wide character handling function in C/C++.

  • Chinese Character Printing in Smartform (Different Question)

    Hi all,
    Can anyone explain to me further the OSS Note 776507 that Anji Reddy Vangala recently posted?  It involves the preview and printing of different character sets.  Currently I've managed to preview my form correctly, but it still prints out #'s.  Do I need to re-assign the fonts to the printer device or something, or do I need to use a different printer?  The printer I am currently using is an HP 2100.  Please please help, anyone?
    <b>EDIT:</b> Probably a better question would be how to map the conversion font of CNSONG to something that can be read by the printer?
    A copy of the note for everyone's reference:
    OSS Note: 776507
    Symptom
    Documents printed via SAPscript or SmartForms do not print with correct special characters, e.g. ### prints instead of Japanese or Russian characters. What to do?
    Other terms
    SAPscript, SmartForms, printing, device types, OTF
    Reason and Prerequisites
    Help required to choose proper fonts in a SAPscript or SmartForm
    Solution
    When using SAPscript or SmartForms to print (or email or fax) a form from a business application, many factors influence the outcome of the actual text within the form. All these factors must be checked in order to ensure a correct printout:
    1) The language version of the form used to produce the printout.
    Example: If you want to print a French invoice, you need to have a FR version of your SAPscript or SmartForms invoice form RVINVOICE01. And the application program must specify the corresponding language key (FR) when calling the SAPscript or SmartForms API.
    2) The font selections specified in the form (possibly also in a SAPscript style or SmartStyle used in a form).
    Example: In a SAPscript form or a SmartStyle you need to specify HELVE if you want to print German text in Helvetica (or similar) font. If you want to print Japanese text, HELVE is not a valid choice but you need to specify a Japanese font like JPMINCHO in your Japanese form.
    3) The output character set of the device type
    Every printer in transaction SPAD has a "device type" assigned. Device types used by the spooler for printing support only one single specific output character set. All text from the form has to be converted (using SAP's built-in character conversion mechanism) to this output character set.
    A character set can typically support either a single language (e.g. Shift-JIS which supports only Japanese) or a set of languages (e.g. ISO 8859-1, which supports Western-European languages). It is possible that a given language (such as German) can be supported by several output character sets, e.g. you may use either ISO 8895-1 (Latin-1) or ISO 8859-2 (Latin-2) to represent German text. This is so because both character sets contain the special characters used in German.
    Example: HPLJ4000 is a HP LaserJet device type supporting the ISO 8859-1 (Latin-1) character set. ISO 8859-1 can be used to represent e.g. Dutch, English, French, German, Spanish, Swedish but NOT Russian or Japanese.
    As a consequence, it is ok to use HPLJ4000 to print English, German French etc. but not for Japanese or Russian.
    4) The set of available printer fonts for a given device type
    When formatting a document, SAPscript and SmartForms perform an automatic mapping of the font definitions in the form (e.g. "HELVE 14 point bold") and the available printer fonts of the device type. A replacement printer font is chosen, should the specified font selection not be available in the device type. Now this replacement can be problematic if a language-specific font, such as Chinese CNSONG, is specified in a form and it gets replaced by a font which does not support this language, e.g. COURIER.
    To solve this problem, font families in SE73 have language attribute assigned, e.g. some fonts are characterized as being suitable only for certain languages. And when a replacement has to be chosen because the original font from the form is not available in the device type, a replacement font is chosen which has the same language attributes.
    If no fonts for the language in question exist in the device type, the resulting font will not be able to print the special characters and you will see "wrong" output characters in the printout.
    Note on SAPscript/SmartForms Print Preview:
    The OTF Print Preview available in Windows GUI (e.g. from transaction SP01) will sometimes not show the "wrong" characters which appear on the final printout. Here is the reason: since the Print Preview runs in Windows environment, it will use Windows fonts to represent the actual printer fonts. A Windows font typically has more available characters (i.e. covers more character sets) than are actually available in a printer's resident font.
    A typical example where the Print Preview will differ from the printout is here: if you have a Chinese PCL5 printer such as CNHPLJ4 and use the Western Latin font COURIER in your document, the print preview will show you Chinese characters if you (by accident) tried to format Chinese characters in COURIER font. This is because Windows will automatically choose a font that can output Chinese characters (which is actually not Courier). But when you print the job on an actual PCL5 printer with resident Western and Chinese fonts, the Courier font will not print any Chinese characters but Western special characters instead, because the printer's resident Courier font does not include Chinese characters.
    Rule of thumb: all Asian device types (e.g. CNHPLJ4, JPHPLJ4, JPPOST, KPHPLJ4) support not only Asian fonts but also COURIER, HELVE and TIMES fonts. But these Latin fonts can only be used to print English text, not Chinese/Japanese/Korean characters.
    Which fonts are suitable for a given language?
    Language(s): Font family to use in a form:
    Latin-1 (Western Europe/Americas) *******
    DE,EN,FR,ES,NL,SV COURIER, HELVE, TIMES
    (LETGOTH, LNPRINT)
    Latin-2 (Central Europe) ****************
    PL, CZ COURIER, HELVE, TIMES
    ISO 8859-4 (Baltic) *********************
    ET, LT, LV COURIER, HELVE, TIMES
    ISO 8859-5 (Cyrillic) *******************
    BG, RU, SR, UK COURCYR, HELVCYR, TIMECYR
    ISO 8859-7 (Greek) **********************
    EL COUR_I7, HELV_I7, TIME_I7
    ISO 8859-8 (Hebrew) *********************
    HE COURIER, HELVE, TIMES
    ISO 8859-9 (Turkish) ********************
    TR COURIER, HELVE, TIMES
    Simplified Chinese **********************
    ZH CNHEI, CNKAI, CNSONG
    Japanese ********************************
    JA JPMINCHO, DBMINCHO, DBGOTHIC
    Korean **********************************
    KP KPBATANG, KPDODUM, KPGULIM
    KPGUNGSE, KPSAMMUL
    Traditional Chinese *********************
    ZF TWDPHEI, TWMING, TWSONG
    Thai ************************************
    TH THANGSAN, THDRAFT, THVIJIT
    Arabic (Unicode systems only) ***********
    AR ANDALE_J
    Verify your output by examining the OTF data
    When analysing printing problems of this type, be sure to check the OTF data which gets produced by SAPscript or SmartForms. OTF or "Output Text Format" is the intermediate page-description format generated from SAPscript or SmartForms. OTF will contain the final printer font names and character set/language identifiers which help to solve the problem. OTF will even name the form and the language of the form used to create the output.
    The easiest way to do this is to create a spool request from your application, run transaction SP01, use menu
    Goto->Display Requests->Settings
    and choose
    Display Mode: Raw
    Now display your spool request. If this is a SAPscript or SmartForms spool request, you will see OTF data. Each line represents one OTF command, every command starts with a 2-character cmd identifier and possibly some cmd parameters follow.
    Here is an excerpt from a sample OTF file where we highlight the most interesting commands:
    //XHPLJ8000 0700 00000000001
    IN04EALEXTEST_ZEBRA
    IN05%PAGE1
    OPDINA4 P 144 240 1683811906000010000100001
    IN06%WINDOW2
    MT0024401289
    CP11000000E
    FCHELVE 120 00109XSF100SF101110000067E X
    UL +0000000000000
    SW00067
    CT00000000
    ST0453037Dieses SF hat Stil ALEXTEST_ZEBRA mit
    The 1st line with the // (Control) command reveals the device type usedto print: HPLJ8000
    //XHPLJ8000 0700 00000000001
    The 2nd line (IN = Info command) shows the name and (internal 1-char)language key of the form:
    IN04EALEXTEST_ZEBRA
    In this case it is the English (E = EN) SmartForm ALEXTEST_ZEBRA
    The OP-line (OP = Open Page) gives the page format used in the form, it is DINA4 Portrait orientation:
    OPDINA4 P 144 240 1683811906000010000100001
    The CP (CodePage) cmd shows the SAP system codepage used to code the text and the active language. In our case it is codepage 1100 and language E = EN = English.
    CP11000000E
    Finally, the FC-cmd (Font Call) lists a printer font selected within SmartForms. Please note that every SmartForm has a designated default SmartStyle under "Form Attributes->Output Options". In addition, every text node can have a SmartStyle attached (which will override the definitions from the default style for the text). In our case the resulting printer font that was selected is HELVE 12.0 pt bold-off, italic-off.
    FCHELVE 120 00109XSF100SF101110000067E X<b></b><b></b><b></b>

    Hi,
    there a different things to know.
    I produce sapscript forms with cinese and english characters for frontend / backend and archiv printing.
    Please check:
    Editor displays ###: You have to install the chinese language in your e.g. windows-system to display them.
    Script: You have to chose the the font family "CNSONG" (customized for chinese simplified and LATIN).
    Transaction I18N: May you have to set correct subfonts for the unicode areas (Cascading fonts, Standard is Courier).
    You can print in different ways:
    For archiv/PDF: Install the unicode truetype font with chinese characters for the pdf-converter.
    For Frontend: Use the Frontendprinter SAPWIN or SAPWIN*CF (Cascading Font) to send it to the gui (note: SAPLPD does not support it, use the newer technology.....)
    Backend printing: POSTSCRIPT is not yet implemented :-((
    PLease note: What you see in spool / print preview is a simulation of the possible print, but backend print is not frontend preview!!!!
    Regards,
    Christian

  • GUI Download Chinese Character to Excel gibberish character

    Hi Experts,
    I'm facing a problem where I'm using FM gui_download to save Chinese Character into Excel file.
    Upon double click to open the excel file, funny character shows up.
    But if I were to open the same file using a blank Ms Excel application (Go to File->Open->choose file),
    Excel will prompt me to select a proper encoding (GB2312 in this case), and the Chinese character can be seen thereafter.
    But, my user doesn't want to go through this.
    I've browsed through the forum and someone has posted about this before and it's unanswered.
    How to download the chinese character using GUI_DOWNLOAD - unanswered
    And, Re: GUI_DOWNLOAD give 2 bytes for each chinese character - I need fixed len which is not related to my problem.
    Below is my code:
    DATA: lv_codepage   TYPE cpcodepage,
            lv_char_cpage TYPE abap_encod,
            lv_encoding   TYPE abap_encod.
    Get Code Page for Chinese Character Spras = '1' or 'ZH'
      CALL FUNCTION 'NLS_GET_FRONTEND_CP'
        EXPORTING
          langu                 = '1'   " Chinese Simplified Table T002
          fetype                = 'MS'  " Manufacturer is Microsoft Table TCP05
        IMPORTING
          frontend_codepage     = lv_codepage
        EXCEPTIONS
          illegal_syst_codepage = 1
          no_frontend_cp_found  = 2
          internal_or_db_error  = 3
          OTHERS                = 4.
    Conversion c(4) = n(10)
      lv_char_cpage = lv_codepage.
      CALL FUNCTION 'GUI_DOWNLOAD'
        EXPORTING
          filename                = p_file
          filetype                = 'DAT'                       "tried ASC and not working as well
          codepage                = lv_char_cpage   "8404 in this case tried 8400 and same result
          replacement             = '#'
          write_field_separator   = 'X'
        TABLES
          data_tab                = i_data_cnvr        "table content
          fieldnames              = i_data_head      "table header
    Please help. Does this has something to do with utf-8 encoding?
    Thank you.
    Thanks,
    ZY See

    Hi Nitesh,
    Is there a way to check the Excel codepage? Do you mean by codepage = 936 for GB2312 encoding?
    Anyway, this issue is fixed. Issue is related to unicode system.
    Below codes for gui_download solved the problem.
    CALL FUNCTION 'GUI_DOWNLOAD'
        EXPORTING
          filename                = p_file
          filetype                = 'DAT'
          codepage                = '4103'
          replacement             = '#'
          write_field_separator   = 'X'
          write_bom               = 'X'
        TABLES
          data_tab                = i_data_cnvr
          fieldnames              = i_data_head
    Codepage = 4103 for utf-16 Unicode system.
    Write-bom = 'X' to write Byte-Order-Mark.
    Thanks,
    ZY See

  • Some of Chinese character is not displaying correctly in PDF output

    Hi all
    I'm involved in the 1st Peoplesoft project in Korea and having a difficulty with displaying Chinese character in PDF output.
    Usually Koreans can translate their name in Chinese and that Chinese name is displayed in personal information in their company as well as Korean name.
    With Oracle BI Publisher I made rtf template that includes employees' Chinese name and tried to export to PDF output.
    Most of Chinese character was fine but '李' character that was ok in HTM output was crashed in PDF output.
    So I researched and tested some solutions.
    Here's what I did.
    I downloaded and installed five fonts(ALBANWTS.ttf, ALBANWTT.ttf, ALBANWT.ttf, ALBANWTK.ttf, ALBANWTJ.ttf) in client machine(c:\windows\fonts\) and did mapping job with xdo.cfg configuration file.
    After that I previewed PDF output in the rtf template and checked embeded fonts in the PDF file.
    I can see the newly installed font was embeded but still '李' character is crashed.
    My problem is little bit different from others becuase only one Chinese character is crashed by for now.
    The Chinese character '李' is very common last name in Korea and I believe Simplified Chinese character font have in it.
    Please let me know if you have any solutions or experiance.
    Thanks and best regards
    Kwangbock.

    Hi James
    Oh~ It perfectly works!!
    I've been tried to solve this problem for a long time and
    I really appreciate for your help~
    Thanks~
    Kwangbock.

  • How to read text file contain chinese character ?

    Hi XI Expert,
    I have scenario to read text file contain Chinese Character using sender file adapter. but every i was check from sxmb_moni all the chinese character looks different. and also the target file also i has changes.
    Please advise me how to maintaine the chinese character in PI 7.0 SP17.
    Thank You and Best Regards
    Fernand

    Hi,
    Refer these threads..
    Receiver file adapter corrupting characters
    Problem in converting special characters in input text file
    Here is one more useful guide..
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/502991a2-45d9-2910-d99f-8aba5d79fb42
    Regards,
    Sarvesh
    Edited by: Sarvesh Singh on Nov 17, 2008 3:47 PM

  • Chinese Character in PDF format for Oracle Reports 11g

    Hello Everyone,
    Currently we have a Report that need to be display chinese character in PDF format.
    We followed the steps specified in the "Oralce Fusion Middleware Publishing Reports to the Web with Oracle Reports Services"
    documentation but things doesn't work. We also installed Adobe Acrobat Reader 9 and Asian Font Pack 9 on the server side
    and even on the client/user/development side and followed the steps in the documentation, but no effect at all. Or we even
    tried "Arial Unicode MS", same thing no effect.
    For sure, we may miss something during PDF aliasing or PDF subsetting setup.
    Anyone out there who has the same experience and able to resolve the issue that currently using the Oralce Fusion Middleware Reports 11g?
    Doesn't matter if it does not related to chinese character, as long as it relates to this issue like japanese or arabic characters in PDF.
    If its ok, kindly provide the steps how you do it.
    Your help is highly appreciated.
    Regards and Thank you very much!

    I am now facing exactly the same problem as user449955 (Eric's). Dear Eric, how about your situation? If you have resolved this problem, may I ask for your solution?
    In my case, using either font aliasing or font subsetting doesn't work at all (displaying "garbage" characters instead of Chinese characters). The setting in my uifont.ali is as follows:
    If using font aliasing:
    [PDF]
    .....ZHT16HKSCS = "MSungStd-Light-Acro"
    If using font subsetting (the REPORTS_PATH already includes "C:\Windows\Fonts"):
    [PDF:Subset]
    "Courier New" = "mingliu.ttc,2"
    For both cases, the report server's NLS_LANG already set to "TRADITIONAL CHINESE_HONG KONG.ZHT16HKSCS" (I am in fact located at Hong Kong). For font aliasing, the client side already has Asian Adobe Reader with Asian font pack installed.
    By the way, I noticed that the WebLogic EM is configuring/updating the uifont.ali file at "<instance home>\config\FRComponent\frcommon\tools\common" directory, but the Oracle Reports 11g's documentation sometimes advise to refer to another uifont.ali file located at "<instance home>\config\FRComponent\frcommon\guicommon\tk\admin" directory. Which one of the uifont.ali files is the one used by the Oracle Reporting Service?
    My report server's platform is Windows 7 Enterprise (64-bit) and the Reports version is 11.1.1.3.
    Anyone can help to advise?
    Thank you very much.
    Regards

  • Output chinese character to CSV file in UNIX

    Hi
    I encountered ABAP dump whenever output chinese character to CSV file in UNIX in ECC6. Error show as
    "At the conversion of a text from codepage '4102' to codepage '1100':
    - a character was found that cannot be displayed in one of the two
    codepages;
    - or it was detected that this conversion is not supported"
    The program with coding of statement OPEN DATASET xxxxx FOR OUTPUT IN TEXT MODE  ENCODING NON-UNICODE. Reason to output to OPEN statement to non-unicode as users would like to open the csv file thru Excel directly. They do not wish to open the text file in Excel. Can Experts please share with me how to overcome the problem?
    Thanks
    Kang Ring

    May be you could give a try with the following code and check
    OPEN DATASET xxxxx FOR OUTPUT IN TEXT MODE ENCODING NON-UNICODE CODEPAGE '4103'.
    Vikranth

  • Chinese Character cannot be decoded

    hi,
    I would like to implement two JSP pages. The first JSP is just a html form, which is used to submit unicoded chinese data to a target JSP file.
    The target JSP file received those data and display.
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> is added in the first JSP file. As a result, data will be submitted in UTF-8 format.
    In target JSP, I used the following code to recieve and decode data:
    <%@ page contentType="text/html; charset=UTF-8" %>
    <%
    String para = request.getParameter("para"); // where para is name of received parameter
    byte[] bytes = para.getBytes();
    para = new String(bytes, "UTF-8");
    out.println("Recieved character: " + para);
    %>
    My Problem:
    After I submitted chinese characters from the first JSP file, only some of them can be displayed on target JSP. Some of those characters are missing.
    For example, when I input "�@", target JSP can display the character. On the other hand, when I input "�p", nothing is displayed. But I know that variable "bytes" stored 3 bytes for each chinese character. I would like ask why
    para = new String(bytes, "UTF-8");
    cannot encode properly. Is anything wrong about my coding?
    Thx

    More information can be provided.
    OS: Windows 2000 server
    web server: iPlanet
    P.S. : I have set the Character set to UTF-8 in iPlanet.
    thx.
    hi,
    I would like to implement two JSP pages. The
    The first JSP is just a html form, which is used to
    submit unicoded chinese data to a target JSP file.
    The target JSP file received those data and
    and display.
    <meta http-equiv="Content-Type"
    ype" content="text/html; charset=UTF-8"> is added in
    the first JSP file. As a result, data will be
    submitted in UTF-8 format.
    In target JSP, I used the following code to
    to recieve and decode data:
    <%@ page contentType="text/html; charset=UTF-8"
    F-8" %>
    <%
    String para = request.getParameter("para"); //
    // where para is name of received parameter
    byte[] bytes = para.getBytes();
    para = new String(bytes, "UTF-8");
    out.println("Recieved character: " + para);
    %>
    My Problem:
    After I submitted chinese characters from the
    m the first JSP file, only some of them can be
    displayed on target JSP. Some of those characters are
    missing.
    For example, when I input "�@", target JSP can
    P can display the character. On the other hand, when I
    input "�p", nothing is displayed. But I know that
    variable "bytes" stored 3 bytes for each chinese
    character. I would like ask why
    para = new String(bytes, "UTF-8");
    cannot encode properly. Is anything wrong about my
    coding?
    Thx

  • Cannot display Chinese Character in ver 10.1.3

    Hello,
    I would like to ask one more question, when i run my program, it contain two jsp pages,
    the first one is to ask the user to input some chinese character, then the second one is to display the input data in the second page. I found out that the second one cannot display the input chinese character, but other chinese character in the second one can be display.
    Some of my code in the second one are as follow:
    String firstName = request.getParameter("firstName");
    &#20013;&#25991; <%=firstName%>
    The result are displayed are displayed as follow:
    &#20013;&#25991; ?T???\!
    It seems to me that the text can display but the variable cannot display, does any one know the reason?
    One of the replies from the JDeveloper forum are as follow:
    I seem to recall there was a bug in the 10.1.3 OC4J with passing parameters on the URL in other languages. You might want to ask on the OC4J forum:
    OC4J
    Regards,
    Alan 20/11/2005

    chulongjiang,
    i solve the problem with your advice, thanks lot!
    Regards,
    Alan 24/11/2005

  • Display chinese character

    I have a java application with read string from IE browser through JNI interface.
    The issue is the String i got, which is "\u963f\u5f1f\u4ed4" can't be display in Chinese directly.
    I do following convetion, it doesn't work.
    byte[] sb=link.getBytes();
    String Zhongwen=new String(sb, "GB2312");
    But if I define a this String in my application, it works.
    String link = "\u963f\u5f1f\u4ed4";
    I bet Java treats first case as a buch of seperate characters since if I build
    a String as "\\u" + "963f", I can't get chinese character.
    So it is looks I can only use the parseInt(..) method on the Integer class and casting the result to a char.
    try
    char p = (char)Integer.parseInt(x, 16);
    System.out.println(p);
    catch(Exception e)
    System.out.println(e);
    Does antbody have another solution?

    The most probable source of error is character encoding conversion...most likely from the IE browser to the Java environment. Do you have a way to find out what encoding is used in the browser? IE will transfer form data back to the server in either UTF-8 or the encoding of the original form.
    Transfer the data from IE correctly, and you will be able to display the characters without further problem.
    John O'Conner

Maybe you are looking for

  • Can't download add-in adobe connect

    i am attendging a webinar, which uses adobe connect. i can connect to everything (including recorded lectures) EXCEPT for the live presentations.   i get the message that i must add Connect, but then i am unable to.   i can use it by entering as a gu

  • Nested SQL Queries

    Hi, I have a question for hierarchical queries.Suppose we have three tables manufacturer,brand and product.I wish to generate the XML for this query.The query I gave is as follows select a.manid ,b.brandid,c.prodid from manufacturer a ,brand b ,produ

  • Installer Error Message with Adobe Pro IX

    I have tried several times to download Adobe Pro IX with no success.  Today I keep getting an error message that states the installer is misconfigured.  Tried to download new installer and just keep getting the same error message.  I checked the syst

  • Unable to set Media location in iTunes

    Hi All, I have just finished the Yosemite upgrade and want to set my media folder in iTunes. In iTunes>Preferences>Advanced I select my music folder, (held on a separate internal drive), and then press Scan For Media, nothing happens, no media locate

  • Can I get a native dump (Dr. Watson) when JNI code causes an exception?

    Is there a way to get the JVM to just not trap an exception, so that we can get a native dump? I have tried -XX:OnError="drwtsn32 -p %p". This did produce a Dr. Watson dump, but not a good one. I placed a deliberate error in the code, and called it o