Regarding German Umlauts.

Dear gurus ,
   I am currently working on DATA reconcilition project which involves
the comparision of DATA from two different systems.
Well the problem is whenever a field carrying  GERMAN UMLAUTS (Ä,ó,é,í)  is being compared,
it is not recognising the filed even if they are all equal on both the system !!!
Please suggest some ideas !
Edited by: ajaysingi on Mar 9, 2011 8:25 AM

Hi ems174,
We will be fixing this issue in the next update and you can track it with bug ID 422700.
Jonathan N.
National Instruments

Similar Messages

  • German umlaut in idoc to file scenario

    Hi,
    in our scenario we send MATMAS idocs to XI, map them and create a file using file adapter.
    Settings in file receiver communication channel: file type = text and  file encoding = UTF8. I also tried file encoding = ISO-8859-1 - both with the same result:
    German umlauts are not converted. E.g. the material short text "Hängematte" is shown as "Hängematte" in the created file. The receiving system errors out. Acceptable would be
    "H& #228;ngematte". (of course without the blank but I have to add it herer else the forum would replace this by "ä" )Any help is appreciated.
    Regards,
    Philipp

    Hi,
    Follow the steps:-
    1>In your adapter -> Set File type to TEXT -> use Encoding and provide ISO-8859-1 (http://en.wikipedia.org/wiki/ISO/IEC_8859-1)
    To know more about other encoding standards refer -
    http://en.wikipedia.org/wiki/Character_encoding
    2>file type==>binary
    Regards,
    AshwinM
    Reward If helpful

  • Encoding Problem: Losing German Umlaute from gathering data from Oracle 8i

    my problem does concerns the diplay of german Umlaute such as äöüß etc. The OS is NW65 out of the box with Apache 2.0.49 and tomcat 4.1.28, JVM 1.4.2_02 and JDBC-driver Oracle 8i 8.1.7 JDBC Driver.
    The Data containing Umlaute which are retreived from the Database does somehow lose it´s Umlaute. The Umlaut which are coded in the servlet directly in order to generate the regular HTML does display the Umlaute without any problem.
    The same servlet and request from a Unix Enviroment does work fine. We have checked all Codepage settings (Java, NetWare, Tomcat etc).

    Hi Sven and Ingmar,
    I will try to kill 2 birds with one stone here. First of all you should check the definition of your current database character set and make sure that it can support all the characters that you need to store in your database.
    Please check out
    http://www.microsoft.com/globaldev/reference/iso.asp
    WE8ISO8859P9 is for Turkish and WE8ISO8859P1 is for western European (without Euro support).
    Next you need to set your client NLS_LANG character set (eg. for your SQL*Plus seesion), so that Oracle can convert your client operating system characters correctly into your database character set. The NLS_LANG character set also determines how SQL*Plus interpret/display your characters upon retrieval from the db.
    In both of your cases , I believed that the client NLS_LANG setting was not defined , hence this was defaulting to AMERICAN_AMERICA.US7ASCII. This is telling SQL*PLUS that the your client operating system can handle ASCII data only , hence all the accented characters are converted to ASCII during insertion into the database. Likewise upon data retrieval.
    If you are running SQL*PLUS client on English Windows then you NLS_LANG character set should be WE8MSWIN1252 and for Turkish Windows it should set to TR8MSWIN1254 .
    If the client character set and the database character set are the same , Oracle does not perform any data conversion, that's why if you use a US7ASCII database and set you NLS_LANG character set to US7ASCII .then you can insert all the accented Latin characters , Japanese , Chinese etc. This configuration is not supported, and it can cause many issues.
    For more information on character set configuration and possible problems.
    Please check out the white paper Database Character set migration on http://otn.oracle.com/products/oracle8i/content.html#nls
    And the Globalization Support FAQ at:
    http://technet.oracle.com/products/oracle8i/
    Regards
    Nat
    null

  • German umlauts :Sender File Adapter

    Hi,
    I am trying to configure Sender File adapter,but it is not working properly for German umlauts.
    I have tried encoding UTF-8, UTF-16, ISO-8859-1,ISO-8859-2, ISO-8859-5 but none of them are working.
    Can anyone please help me out in this.
    Thanks a lot.
    Regards,
    Shweta

    Hi Stefan,
    I have already added this module exactly in the same way.
    But can you please confirm the sequence
    Module :
    localejbs/AF_Modules/PayloadSwapBean                     Local Enterprise Bean     swap
    localejbs/AF_Modules/MessageTransformBean     Local Enterprise Bean     Transform
    localejbs/AF_Modules/MessageTransformBean     Local Enterprise Bean     Transform
    Transform.ContentType                     text/plain;charset="UTF-8"
    Transform.ContentDisposition            attachment;filename="ABC.csv"
    Also,I noticed one thing
    The content is corrupted in SXI_MONITOR but it is correct in payload of File as well as Mail adapter in Message Monitor(RWB)
    Thanks.
    Regards,
    Shweta

  • Mail Adapter - PayloadSwapBean - MessageTransformBean - German umlauts

    Hi there,
    I'm receiving mails with an attachment (.csv / .txt) that I want to process to get IDocs. Everything works fine but the conversion of German umlauts. I tried to apply several charsets (i.e. iso-8859-1, iso-8859-2, utf-8) in the contentType parameter without success. The result in my payload after swapping and transforming is a message without umlauts. All these characters have been replaced by the same 'character' that looks like a quadrangle. Therefore even the earliest possible mapping comes too late to convert this character back into umlauts, because I don't know anymore the original ones.
    When I process the same attachment with a <u>file</u> <u>adapter</u> in the same manner (until getting an IDoc) there are no problems with umlauts, the payload looks fine!
    I even checked the note 881308 (although it's said to be for the mail receiver) but it's already in the system (XI 3.0, SP 14)
    Anyone an idea to solve my problem?
    Regards,
    Ralph

    Hi Ralph,
    now I got the solution:
    Allpy the MessageTransformBean twice.
    First you set the code page for the mail attachment, how it comes to the system.
    Then you do the conversion and set the code page how the target xml should be.
    Make two entries in Module configuration:
    localejbs/AF_Modules/MessageTransformBean - contenttype
    localejbs/AF_Modules/MessageTransformBean - tranform
    as paramters you set:
    contentType - Transform.ContentType - text/plain; charset=iso-8859-1
    transform     - Transform.ContentType - text/xml; charset=UTF-8
    transform     - Transform.Class           - com.sap.aii.messaging.adapter.Conversion
    and so on.
    The problem is that outlook does not provide the content type for the attachment, so the MailTransformBean assumes UTF-8, but the attachment has iso-8859-1, so you have to set this before the conversion.
    I have tested this with XI 3.0 SP17 with note 960501 included.
    Regards
    Stefan

  • Wrong coding of german umlaut in XML/XSLT output

    I'm using Oracle 8.1.5 with XSQL Servlet.
    The contents of my database contains german
    umlaut. Visiting the HTML output using
    Netscape/WinNT seems to be correct, but when
    I save the page the saved page contains a
    unknown (for me!) hex conversion of the
    umlaut and not '&auml;' etc. The stylesheet
    uses enconding ISO-8859-1.
    I think, the problem will be found in the
    stylesheet, but I don't know where.

    Hi,
    I test on my Lync client and there is no issue about it.
    Please update to the latest version for Lync Server 2013 (the latest version is 5.0.8308.815) and then test again.
    http://support2.microsoft.com/kb/2809243
    Best Regards,
    Eason Huang
    Eason Huang
    TechNet Community Support

  • Characters With German Umlaut in webservice

    Hello,
    i have a requirement wherein i have to pass Characters With German Umlaut in my web service but when i see the trace they are getting converted into dots.
    does anyone have solution for it?
    Regards,
    Gunjan

    Hi,
    Ideally this should not be a problem. Please provide more information.
    Where you are checking trace? (PI?)
    Are you getting response or request as dots?
    Can you check encoding?
    Check this out, to me it seems problem related to encoding: http://www.sqldbu.com/eng/sections/tips/utf8.html
    The problem mainly arise because of mismatching of encoding: ISO-8859-1 and UTF-8.
    so double check encoding type provided in request and response.
    Regards,
    Gourav

  • AS2 Sender problem with German "Umlaute"

    Hello experts,
    I have an AS2 sender adapter sending orders into my SAP system. My problem is though that it deletes all German "Umlaute" before converting it into XML.
    I used to use the "CallBicXIRaBean" to do the Encoding with ISO-8859-1 and it did not work. So now I am using the "CharsetConversion" to do that but it still does not work.
    In the Module of the AS2 sender I am using:
    1) CharsetConversion
    - sourceDest --> MainDocument
    - targetDest --> MainDocument
    - sourceEnc --> ISO-8859-1
    - targetEnc --> ISO-8859-1
    2) CallBicXIRaBean
    - mappingName --> E2X_ORDERS_UN_D93A
    3) localejbs/CallSapAdapter
    - 0
    Does anyone have an idea what I have to change?
    Thank you very much for your help!
    Best regards,
    Peter

    Hello Iddo,
    Thank you for your answer.
    When I expect Umlaute in a message I always use ISO-8859-1 and not UTF-8.
    The Umlaute are actually deleted. For example the German "für" looks like this "f". Or "Präferenzsituation" looks like this: "Prerenzsituation". So it kills the Umlaut and the following character.
    The sender insists that he sends the messages with Umlaute. Now I activated the AS2 Message Dumping and hopefully will see what the message really looks like. Maybe the Umlaute are already deleted when they get to the AS2 adapter. I hope to find out soon.
    Best regards,
    Peter

  • Character encoding problem with german umlaut in propertie files

    Hi,
    I use propertie files to translate application to multiple languages.
    These files contains german umlaut (e.g.: Wareneingänge).
    If I rebuild my application then this files are copied from ../src/view to ../classes/view.
    The file in ../classes/view contains "Wareneing\ufffdnge" instead of "Wareneingänge" which is displayed as "Wareneing�nge".
    My browser-, project- and application settings are UTF8.
    Previously the settings for project and application where "Windows-1252"
    I have found an workarounds but maybe this is a bug in Jdeveloper TP4.
    Therefore I post this problem. Maybe someone can confirm this behaviour.
    Workaround:
    Replace "Wareneingänge" with "Wareneing\u00e4nge" in the ../src/view file
    (Zaval JRC Editior does this for you :-) )
    regards
    Peter

    Hi,
    I think to remember that the same was required for properties in 10.1.3 as well. Not sure if this is an issue in JDeveloper 11. I'll take anot and have a look though
    Frank

  • Problems with German umlaut in OCI query

    Hello,
    I have some problems in getting results, if I search for data with a German umlaut like "ä", "ö" or "ü".
    In SQL*Plus the following query returns on row:
    SQL> SELECT  SYSBE.ID AS SYSBE_ID
      2          , SYSBE.NACHNAME AS SYSBE_NACHNAME
      3          , SYSBE.VORNAME AS SYSBE_VORNAME
      4       FROM  SYS_BENUTZER SYSBE
      5          LEFT JOIN SYS_ABTEILUNGEN SYSAB ON SYSAB.ID = SYSBE.ABTEILUNG_ID
      6        WHERE  SYSBE.STATUS = 'aktiv'
      7           AND ((SYSAB.KUERZEL <> 'SYS') OR (SYSAB.KUERZEL IS NULL))
      8           AND SYSBE.ID NOT IN (SELECT PMPD.MITARBEITER_ID
      9                 FROM  PM_PROJEKT_MITARBEITER PMPD
    10                 WHERE  PMPD.PROJEKT_ID = 26 AND
    11                   PMPD.MITARBEITER_ID = SYSBE.ID)
    12           AND (REGEXP_LIKE(SYSBE.NACHNAME, 'hö', 'i')
    13              OR REGEXP_LIKE(SYSBE.VORNAME, 'hö', 'i'))
    14        ORDER BY SYSBE.NACHNAME, SYSBE.VORNAME;
      SYSBE_ID SYSBE_NACHNAME
    SYSBE_VORNAME
            52 Höfling
    AlexanderIf I execute this from PHP via the oci8.dll no rows will be returned. Yesterday the DBA helped me to trace the query and it looks exactly the same as above.
    Can anyone help?
    Regards,
    Stefan

    Are your NLS environment variables the same on both systems? Were they set prior to starting up Apache/IIS?

  • Wrong german umlauts

    Hi,
    we are using PI/7.0 and a customer uses XI/3.0 - we have the same SWCV installed on the machines.
    The solution sends mails via java-mail  - not via mail adpter of XI/PI.
    We are sending IDocs from R/3 to XI and the solution sends mails via java-mail to external destinations.
    Our problem is now the "german umlauts".
    On XI everything works fine - the attachment-file is ANSI and all german umlauts are correct.
    On PI the attachment is UTF-8 and all german umlauts are 2 bytes.
    I checked everything hundreds of times - and found no difference.
    The only difference is the NLS-Support of the database. On both installations there is ORACLE 9.2 and on PI (that doesn't work correctly) the NLS-LANG configuration is "US" and UTF-8,
    The installation on XI/3.0 (this works!) is german.germany and iso-8859-1.
    Is it possible that this is out problem?
    Regards
    Wolfgang

    Do you have commas in the display name? We used to have "Müller, Thomas" <[email protected]> and then got the split up and special characters you mention. Tests have shown that when leaving out the comma in the display name, e.g. "Thomas Müller" <[email protected]>, everything worked fine.
    Guess it's a question of whether a company wants to change its naming convention for a few iPhone users...
    HCD

  • No hostcontainer with german umlaut in filename

    Acrobat javascript does not recognize its hostcontainer in pdf files wih a german umlaut (ö) in the filename. Are there any solutions for this issue?

    Hi,
    Ideally this should not be a problem. Please provide more information.
    Where you are checking trace? (PI?)
    Are you getting response or request as dots?
    Can you check encoding?
    Check this out, to me it seems problem related to encoding: http://www.sqldbu.com/eng/sections/tips/utf8.html
    The problem mainly arise because of mismatching of encoding: ISO-8859-1 and UTF-8.
    so double check encoding type provided in request and response.
    Regards,
    Gourav

  • German umlauts in dialogue windows

    I installed Framemaker 8.0.4 on Solaris.
    When I enter german umlauts (or french accents) in any text field of any dialogue window, Framemaker does not echo the umlaut, but a character sequence, e.g. '%X8A', instead of an 'ä' character. This is a bit annoying, because I cannot e.g. search my document for german words containing umlauts. With Framemaker 6 I did not have this problem.
    I can cut and paste (with mouse buttons) an 'ä' character from a text editor into a FM text field, which will be echoed correctly. Entering umlauts in the document window also works well.
    How can I fix this?

    Hi Martin,
    You did not say, whether a search with "%X8A" does find occurrences of ä.
    The code is the hex code equivalent of ä - apart from that the hex code should start with \ and your example starts with %. I do not know, whether % is the correct character for Solaris.
    On Windows I can search for \x8a and find ä.
    All hex codes are listed in Character_Sets.pdf in "documents" in the FrameMaker installation folder. (Possibly the folders have different names on Solaris.)
    Best regards
    Winfried

  • German umlauts / unicode in JNLP-File

    Hi,
    in the <description kind="short">-tag of a JNLP-file I want to use a German umlaut. If I write it as the single character, WebStart cannot load the application, in the error-message the JNLP-File is show up to this character - so it breaks at this point.
    I tried to use unicode \u00fd and the html-entity &uuml; instead but this is not a solution because this strings are writen as plain text to the gui.
    Does anyone know a solution? Or should I post it as bugreport?
    Thanks for answers.
    Jens

    Hi Jens:
    I had the same problem while trying to use French accented characters, and I think it looks quite like a bug in the XML/JNLP parser. I thus suggest to submit a bug report.
    Best regards,
    Jean-Fran�ois Morin

  • Apex 4.0 Cascading Select List: ajax problem with german umlaute

    Hi everybody,
    Apex 4.0
    Dad PlsqlNLSLanguage: GERMAN_GERMANY.WE8MSWIN1252
    I have problems with german umlaute and ajax cascading select lists (Cascading LOV Parent Item).
    The data is populated without a page refresh in the select list when the parent select list changes but special signs like german umlaute are shown as weird characters.
    Seems like there is some charset problem with ajax.
    This is the only part of the application where special signs like umlaute are messed up. Everything else is fine.
    I allready tried to figure out if I can escape the umlaute in the javascript (file apex_widget_4_0.js) but no success here.
    Can anybody help me with this issue?
    Thanks in advance,
    Markus

    Hi Markus,
    your specified character set in your DAD is wrong. As mentioned in the installation instructions at http://download.oracle.com/docs/cd/E17556_01/doc/install.40/e15513/otn_install.htm#CHDHCBGI , Oracle APEX always requires AL32UTF8.
    >
    3. Locate the line containing PlsqlNLSLanguage.
    The PlsqlNLSLanguage setting determines the language setting of the DAD. The character set portion of the PlsqlNLSLanguage value must be set to AL32UTF8,
    regardless of whether or not the database character set is AL32UTF8. For example:Regards
    Patrick
    My Blog: http://www.inside-oracle-apex.com
    APEX 4.0 Plug-Ins: http://apex.oracle.com/plugins
    Twitter: http://www.twitter.com/patrickwolf

Maybe you are looking for