Printing of german characters

Hello Friends,
I am new to SDN and would like to know something. I want to print special german characters via SAP like 2 dots on alphabet A and O. How can I get those printed on the document. Currently these special characters are not printed but a blank space is printed instead. Can someone help?
Regards,
Atul Lotlikar.

Hello Friends,
This is about a non-unicode system where I see that the european characters like the german umlauts ( ä, ö, ü ) are not printed. What could be the solution? Implementing a new codepage like ISO 8859-2 or can it be done with the existing codepage 1100? Can someone help me on this?
Regards,
Atul Lotlikar.

Similar Messages

  • Problem in printing German characters

    Hello Experts,
    We have one issue regarding printing of German characters.
    Issue : When an invoice is created an automatic printout is issued to printer and one is archived in Vf03 (path : invoice header data-> output -> edit -> diplay originals). In the automatic issued printout capital German characters like Ö are not getting printed in invoice. But if we see the same in VF03, the document which is archived, the German characters are appearing.
    Could you please let me know what can be the reason for this ? It cannot be a printer issue because if we take a printout from VF03 the archived document it is printing absolutely fine. Problem is with automatic printout.
    Any suggestions are appreciated.
    Ravi Teja.
    Edited by: Amaravadi on Nov 9, 2011 5:02 PM

    Hi Saurabh,
    Did you [Search|https://www.sdn.sap.com/irj/scn/advancedsearch?query=chinesecharactersin+Script&cat=sdn_all] before posting...
    and also refer to this [link|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/00adf4da-76f1-2910-43aa-81ad2a67332c]
    Regards!

  • Special German characters not printing correctly on BI pub report

    Hi
    We have a BI PU Report which gets the XML from the 6i reprot, the titles on the report are dervied from a custom table where we store the label value for each language. THis is worked so for okay on NA, now we migrated this to Europe and having issues with the label value. when the XML is viewed from the unix server the value appears oaky (the value is : Abnahmeprüfzeugnis),
    but when I copy the XML output and view it from the desktop, it appears as Abnahmeprüfzeugnis , bsically it replaces ü with ü.
    The pdf output also prints this wrong value (as Abnahmeprüfzeugnis). Not sure what's wrong with this. Please let me know if you have any ideas?
    Thanks,
    Ravi
    Edited by: user8944246 on Jun 10, 2010 12:30 PM

    Steve- I understand what you are mentioning about the ftp, the XML file looks okay on both server and the client except for the letter 'ü ' and the rest of the German characters prints okay. THe problem is that the BI reprot is printing the same wrong characters.
    --Ravi                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   

  • Unable to load German characters in NON Unicode Essbase Cube

    Hi Guys,
    This is what we want to do:
    Build a Cube for Germany on our Essbase server in US. Our users will access cube using Excel Add-In from Germany. But since the Essbase server is in US, system environment variable ESSLANG is set to English_UnitedStates.Latin1@Binary.
    The version of Essbase we are using is 7.1.3.
    What we tried & failed:
    To load German characters from our dimension build Text file, we added a header: //ESS_LOCALE German_Germany.Latin1@Default
    at the beginning of the dim build Text file hoping the rule file will understand that the file contains German characters & load it correctly. Then using EAS I load the dimensions using its corresponding rule file.
    Essbase loads the dimensions correctly, with NO Error, but when it encounters German characters it Replaces it with a Question Mark "?"
    Some of the German characters are:ß Ü ü Ö ö Ä ä Å Ä Ö
    Lastly, the reason we do not want to build Unicode cube is because Excel Add-In will not work with Unicode cubes.
    Its urgent. Please help.
    Thanks.

    The simple and easy way to check
    non-unicode character sets are not supported on unicode system any longer. Am I right?
    Transaction code i18N
    Select
    trouble shooting --> printing  test --> smartforms --> multiple scripts, select your output device and see print preview. it will display all supported characters.
    I guess, above information will be useful for closing the thread.
    Regards,
    SaiRam

  • Preview and Printing of Chinese Characters in Smartform

    Hi everyone!
    I have a development that needs to output in Smartform a combination of Chinese and English characters, on an English Logon,
    When I debug the form, the Chinese characters are shown in the debug screen, but when it is previewed or printed, it shows garbage.  Can anyone help me with this?
    Thanks a lot! Points for any helpful answer!

    Hi
    check this OSS Note
    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
    Regards
    Anji

  • SAP special german characters(umlaut) like ü, ö, ä not displayed properly in XML output

    Hello Team,
    Here we are facing issues while converting SAP tables data to XML file.
    the description is not converting properly for the special German characters like ü, ö, ä.
    Actual output should be :Überprüfung nach § 29 STVZO
    Output Displayed :Ã#berprüfung nach § 29 STVZO
    Can you please look into and help me in this to get correct output .
    Thank you.

    Hi,
    Unicode or Non-Unincode System ?
    Displayed where ? SAPGUI ? Print Preview ? Spool-Display ?
    And how is the XML file written ?  OPEN DATASET ? BAPI ?
    At all of these stages it might be either that it is only a display system, like the selected display CHARSET in SAPGUI, when it is a non-unicode system, or simply not coded correctly like OPEN DATASET without specifying the cdepage when necessary.
    And it might even be, that even "displaying" the XML File is simply done with the incorrect codepage while the data inside the file is correct.
    If you are on Windows, you might even face funny results when saving a simple textfile from notepad with ANSI/DOS and both Unicode variants and then go to CMD.EXE ans simply "type" the content.
    All 4 results will be different, allthough notepad will display the same stuff.
    So first of all, makes sure which codepage is relevant at all stages from DB-table to "display"
    - DB-Charset
    - SAP system type (unicode/non-unicode)
    - SAP codepage (1100 / 410x )
    - crosscheck the test from report RSCPINST
    - Codepage on Windows running SAPGUI
    - Selected codpage for Sapgui
    Good hunting
    Volker

  • German characters in SAPscript

    hello
    We have transported a SAPscript from DEV to PROD.
    In DEV all characters are displayed correctly. In PROD not. System does not display correctly German characters like "ä".
    SAPscript is a copy from standard RVORDER01 (Order confirmation)
    What could be a reason and how to solve the problem with characters ?
    regards
    Rafal

    Hi,
    Please see the below links for you Problem..
    Genrally that type of problem will come if the printer is Different from DEV or PRD..
    and if the Driver of the Printer will not support..
    in Print privew appear properly but while Printing it will not print the fonts properly..
    see the Below links for Detailed solution..
    Hungarian Character Printing problem
    Problem in displaying special chars
    Prabhudas

  • Report not printing all the characters -main section width greater than 11"

    Hi,
    I am trying to build/modify a Report (used in Oracle Apps) which will be printed on some perforated paper. The perforated paper is little bit wider (11.25 inches) than the regular A4 size paper.
    The problem is when I print the report in Oracle Apps, the report isn’t printing all the characters at end of the page. I adjusted the page width to 11.25" in the main section's property palette, but the same thing is happening. Another point to mention is, I should use all of paper space.
    I am not sure if it’s a report builder issue or oracle apps issue.
    Any help is appreciated.
    Thanks
    Srikanth

    You must have larger margin. Try to make smaller header and/or footer.

  • Output File : German Characters are not coming

    Hi All,
    In my output file german characters are not showing. All the german Symbols are coming as '?'.
    Is there any way to get that?
    Regards,
    Sridhar

    Hi,
    Change the encoding in your File adapter to <b>ISO-8859-1</b>
    In the receiver file adapter --> File Encoding.
    http://help.sap.com/saphelp_nw04/helpdata/en/bc/bb79d6061007419a081e58cbeaaf28/content.htm
    Regards,
    Bhavesh

  • Transformation of german characters using xsl

    Hi,
    I have an xml which contains german characters .. i apply an xsl on the xml to get an html output using xalan. and the german character is converted to "?". When i try converting this using a stand alone java client class it successfully transforms it and am able to see the german character but when the same code is deployed within the application server all the german characters are converted to "?" on the browser. can anyone help me out on this ? i am using an oracle application server (OC4J)
    Pointers on how to move ahead for solving the issue would be real helpful.
    Thanks in advance,

    I'm doing this, and my XSL files include other XSLs. Here's the line of code I use:Templates t =
    factory.newTemplates(new StreamSource(new File(getServletContext().getRealPath(xslFile))));where the String variable xslFile contains something like "Callers.xsl" and my Callers.xsl file is in the web application root. I don't doubt it would work just as well creating a Transformer.

  • German Characters issue while invoking Web Services via UTL_HTTP

    Dear Forum Members,
    I'm trying to invoke SAP CRM Web services from Oracle PL/SQL. I have used following code which is working fine.
    -- call web service using Oracle UTIL_HTTP packages
    DECLARE
      http_req utl_http.req;
         http_resp utl_http.resp;
         lv_request VARCHAR2(32767);
         lc_response CLOB;
         lv_buffer VARCHAR2(32000);
         lv_name          VARCHAR2(256);
         lv_hdr_value     VARCHAR2(1024);     
         l_xml XMLType;          
    BEGIN     
         utl_http.set_persistent_conn_support(true);
         utl_http.set_transfer_timeout(600);
         http_req:= utl_http.begin_request
                                       ( url => 'http://xyz3ni92.server.xyz.com:8045/sap/bc/srt/xip/sap/crm_bupa_custid_qr/011/customersbycrmid/http_binding'
                                       , method => 'POST'                              
         lv_request := '<?xml version="1.0" encoding="UTF-8"?>'
         ||'<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:glob="http://sap.com/xi/CRM/Global2">'
       ||'<soap:Header/>'
       ||'<soap:Body>'
          ||'<glob:CustomerCRMByIDQuery>'
             ||'<MessageHeader>'
                ||'<ID schemeID="?" schemeAgencyID="?" schemeAgencySchemeAgencyID="?"></ID>'
                ||'<UUID></UUID>'
                ||'<ReferenceID schemeID="?" schemeAgencyID="?" schemeAgencySchemeAgencyID="?"></ReferenceID>'
                ||'<ReferenceUUID></ReferenceUUID>'
             ||'</MessageHeader>'
             ||'<BusinessPartnerSelectionByBusinessPartner>'
                ||'<UUID schemeID="?" schemeAgencyID="?"></UUID>'
                ||'<InternalID>2200117598</InternalID>'
             ||'</BusinessPartnerSelectionByBusinessPartner>'
          ||'</glob:CustomerCRMByIDQuery>'
               ||'</soap:Body>'
         ||'</soap:Envelope>';     
         /*set username and password*/
         utl_http.set_authentication (
                   r => http_req,
                   username => 'WS_USER',
                   password => 'WS_PASSWORD',
                   scheme => 'Basic',
                   for_proxy => false);     
         utl_http.set_header(http_req, 'Content-Type', 'application/soap+xml;charset=UTF-8');
         utl_http.set_header(http_req, 'Content-Length', LENGTHB(lv_request));
         utl_http.write_text(http_req, lv_request);
         /*Make HTTP call*/
         http_resp:= utl_http.get_response(http_req);
         /*read response text from response*/
         BEGIN
                   LOOP
                             utl_http.read_text(http_resp, lv_buffer);
                             lc_response := lc_response || TO_CLOB(lv_buffer);
                   END LOOP;
         EXCEPTION
                   WHEN OTHERS THEN
                        -- ora-29266 end-of-body reached
                        IF SQLCODE <> -29266 THEN
                                  RAISE;
                        END IF;
         END;
         utl_http.end_response(http_resp);     
         l_xml := XMLType(lc_response);
         /*Log response for testing*/
         DELETE FROM webservice_log;
         INSERT INTO webservice_log (seq_id,xml_response) VALUES (sqe_Webservice_Log.NEXTVAL,l_xml);
    EXCEPTION WHEN OTHERS THEN
              RAISE;
    END;However, if there are any German Characters in SAP, then they are being replaced by JUNK data when they come to Oracle.
    If I invoke the same web-service suing tools like SOAP-UI, then German characters are coming fine. I have also traced web-service requests/responses from SAP side, and there response is showing fine. When it comes to Oracle, they are getting corrupted.
    I'm sure it's something to do with character-set, but I'm not able to find-out where and what I should fix/change.
    Thanks for your help in advance.
    DB: Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
    NLS_DATABASE_PARAMETERS
    PARAMETER                      VALUE                                 
    NLS_LANGUAGE                   AMERICAN                                
    NLS_TERRITORY                  AMERICA                                 
    NLS_CURRENCY                   $                                       
    NLS_ISO_CURRENCY               AMERICA                                 
    NLS_NUMERIC_CHARACTERS         .,                                      
    NLS_CHARACTERSET               AL32UTF8                                
    NLS_CALENDAR                   GREGORIAN                               
    NLS_DATE_FORMAT                DD-MON-RR                               
    NLS_DATE_LANGUAGE              AMERICAN                                
    NLS_SORT                       BINARY                                  
    NLS_TIME_FORMAT                HH.MI.SSXFF AM                          
    NLS_TIMESTAMP_FORMAT           DD-MON-RR HH.MI.SSXFF AM                
    NLS_TIME_TZ_FORMAT             HH.MI.SSXFF AM TZR                      
    NLS_TIMESTAMP_TZ_FORMAT        DD-MON-RR HH.MI.SSXFF AM TZR            
    NLS_DUAL_CURRENCY              $                                       
    NLS_COMP                       BINARY                                  
    NLS_LENGTH_SEMANTICS           BYTE                                    
    NLS_NCHAR_CONV_EXCP            FALSE                                   
    NLS_NCHAR_CHARACTERSET         AL16UTF16                               
    NLS_RDBMS_VERSION              11.2.0.1.0   Regards,
    Hari
    added further details by: Hari_639 on Apr 24, 2013 6:45 PM

    Hello Both,
    Thank you.
    I ran following command from SQL Plus window after connecting to DB..
    SQL> @[%NLS_LANG%]
    SP2-0310: unable to open file "[AMERICAN_AMERICA.WE8MSWIN1252]"And also I have checked actual data using DUMP function, it looks like data stored is wrong.
    I have updated one field in SAP such that it only contains German character ä. When I query corresponding data from Oracle I got following output..
    SELECT xmlresponse.Notes,
      dump(xmlresponse.Notes,1010) dump_text
    FROM webservice_log,
      Xmltable(Xmlnamespaces
                                  ('http://www.w3.org/2003/05/soap-envelope' AS "env",
                                   'http://sap.com/xi/CRM/Global2' AS "nm",
                                   'urn:sap.com:proxy:DCT:/1SAI/TAS57DF0B317943DEAE3C49:702' AS "prx"
                                   '/env:Envelope/env:Body/nm:CustomerCRMByIDResponse/BusinessPartner'
                                   PASSING xml_response
                                   columns
                                   NOTES VARCHAR2(4000) PATH 'TextCollection/Text/TextContent/Text'
                             ) XMLRESPONSE;
    /* Output */
    NOTES -- DUMP_TEXT
    ä     Typ=1 Len=4 CharacterSet=AL32UTF8: 195,131,194,164But decimal notation for German character ä is different!
    SELECT DUMP('ä',1010) dump_text from dual;
    /*Output*/
    DUMP_TEXT
    Typ=96 Len=2 CharacterSet=AL32UTF8: 195,164Regards,
    Hari

  • Report printing in Greek characters after changing Font

    Hi All,
    We had a bunch of reports created in 'Courier New' font whose output type is PDF. The users wanted the reports to print in 'Arial' font. When I changed the same from Courier New to Arial and ran the report , the report is printing in Greek characters instead of English. I initially thought that it prints in Greek may be because of insufficient space or something for the text fields but there seems to be sufficient spaces to print characters. I tried reducing the size and still the reports prints in Greek in lower size.
    Can anyone let me know how to get rid of this?
    Thanks,
    Srini.

    See if the solution in the following thread applies to you:
    Problem converting font to .afm using ttf2pt1

  • Problems with german characters in data migration

    Hello,
    I tried to migrate a Access 2002 mdb to Oracle 10g XE. In order to avoid errors I used Access 2000 exporter to generate xml and dat for table and data, imported the schema to Oracle database, generated data move scripts and imported the data with a batch-file.
    I did it according to the steps explained here:
    http://www.oracle.com/technology/tech/migration/workbench/viewlets/ofdm.html
    http://www.oracle.com/technology/obe/11gr1_db/appdev/msamigrate/msamigrate.htm
    All german characters in Table names were migrated correctly. But when I import the data, german characters are converted to weird signs like ü.
    If I open the dat-files with windows editor all german characters are displayed properly. If I open the same file with wordpad the german characters are displayed with the errors described above.
    Environment
    Win XP SP 3 German
    Ms Access 2002 sp3 german
    SQL Developer 1.5.0.53 german
    Access 2000 Exporter 10.2.0.2.5
    What am I doing wrong? I can't get it solved since two days.

    Check if database characterset supports these special characters
    check client's nls settings.
    check client machine's language settings (converts characters in driver level)

  • How to handle german characters in case of Outbound JMS interface

    HI all,
           I am doing an interface which is an outbound JMS interface where the message from MQ and uploading it to a file server. The message contains german characters, JMS adapter while converting the message from binary format to XI message format is not able to handle that. So where can we have the option to change the encoding type.

    Hi RamaKiran,
    chk out his link
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/405a83e3-0132-2a10-d3ad-a94a604a0469
    /people/thomas.jung3/blog/2004/07/13/bsp-150-a-developer146s-journal-part-vii--dealing-with-multiple-languages-english-german-spanish-thai-and-polish
    http://help.sap.com/saphelp_nw04/helpdata/en/7d/49ae0771924cf4a1fc7e2af7b2e18c/frameset.htm
    Regards
    Sampath

  • German characters not displaying correctly when redaing from URLConnection

    I have a java file reading the contents of a generated jsp page and writing to an html file and I have the code below doing that. However a couple of German characters like �, � and � are being changed to � in the html file. I tried to set the encoding for the reader, the OutputStreamWriter and also for the URLConnection, but it does not seem to help.
    The data is fine in the database.
    Any inputs on resolving this will be greatly appreciated.
    public void makeLiveHTMLfile(String uri, String HTMLFileName, String siteUrl, String siteDir) throws
    Exception {
    //Local vars
    int i = 0;
    try {
    getConnection(uri);
    Reader rd = getReader(uri);
    FileOutputStream output_file = new FileOutputStream(
    SystemProps.getInstance().getProperty( WEBTOOL_HOME_DIR )+"/html/" + HTMLFileName);
    OutputStreamWriter output = new OutputStreamWriter(output_file, "UTF8");
    while (i != -1) {
    i = rd.read();
    if (i != -1) {
    output.write(i);
    rd.close();
    output.close();
    this.sendFile(HTMLFileName, siteDir, "html", siteUrl);
    } catch (Exception e) {
    throw e;
    private Reader getReader(String uri) throws IOException {
    if (uri.startsWith("http:") || uri.startsWith("https:")) {
    // Retrieve from Internet.
    return new InputStreamReader(conn.getInputStream(), "UTF8");
    } else {
    // Retrieve from file.
    return new FileReader(uri);
    private Writer getWriter(String uri) throws IOException {
    if (uri.startsWith("http:") || uri.startsWith("https:")) {
    // Retrieve from Internet.
    return new OutputStreamWriter(conn.getOutputStream(), "UTF8");
    } else {
    // Retrieve from file.
    return new FileWriter(uri);
    private void getConnection(String uri) throws IOException {
    if (uri.startsWith("http:") || uri.startsWith("https:")) {
    // Retrieve from Internet.
    conn = new URL(uri).openConnection();
    conn.setRequestProperty("Content-Type", "text/html; charset=utf-8");
    conn.setRequestProperty("Accept-Encoding", "utf-8");
    conn.setRequestProperty("Accept-Charset", "utf-8");
    conn.setDoOutput(true);
    conn.setDoInput(true);
    Thanks,
    Monisha

    This web page says that the correct encoding code is "UTF-8", not "UTF8".
    http://java.sun.com/j2se/1.3/docs/api/java/lang/package-summary.html#charenc
    Maybe there are aliases, and it recognises both.... but worth a try.
    Also, when you open the web page with a browser and view the source, do you see Utf8 mentioned in the webpage ? Maybe it's not in utf8, and you're trying to force your app to read it as such.
    Ps. we won the war... tell them to start speaking English !
    regards,
    Owen

Maybe you are looking for