Problem with Umlauts

Hi All,
For our customer we managed a german application inside APEX, unfortunately we have some problems with showing the umlauts in the application.
By showing a interactive report the umlauts in the data and in the column names are shown correct. But when I pressed the green wheel I saw Zurücksetzen instead of zurucksetzen.
This problem also occured by logging into the application with a wrong password (Ungültige ID-Daten für die Anmeldung) instead of Ungeltige ID Daten fur die anmeldung.
By the installation of APEX we run also the LOAD_DE.SQL script to translate the apex version. Before we run this script we set the language to german_Germany.AL32UTF8.
When I look into the HTTP server in the dads.conf file I saw the follow row: PlsqlNLSLanguage German_Germany.AL32UTF8
It seems that the problem is inside APEX instead of the application inside the APEX version (because the application shows the data correct). Is there a way to see which names are stored in the databse (to make sure that the data is stored correctly)?
Has anybody an idea how to fix this problem?
We have an Oracle 11G Database with apex version 3.2 and an HTTP Server.

I find a solution for this problem.
Below the steps we did to fix this issue
I first checked the dads.conf, if you’re weblogic is correctly configured.
Yes it was!
Then I checked, if the database is able to save Umlaute
Yes it was!
Then I checked, if the database stores the Umlaute for Apex
No it doesn't
That means, that the import (load_de) was unsuccessfull.
Then I checked the import files, which were saved on the server
Everything seems to be correct.
Then I checked other NLS related settings and found that ORA_NLS10 was set.
Although we need this setting for some reasons, it “destroyed” our load_de.sql.
Finally I unset this setting, and load the data again and now it worked.

Similar Messages

  • Ipod Video has problems with umlaut in calendar

    Can anybody here confirm that the ipod video has problems displaying umlauts (i.e ä) in the calendar, if the umlaut is the last characters of the summary. If the umlaut is in the middle of a word, it is displayed correctly.
    The summary of the ics file is encoded as Quoted-Printable.
    Here is a sample line:
    SUMMARY;ENCODING=QUOTED-PRINTABLE:Polterabend=20wal=E4
    Saddly, I didn't find a contact form or email-address of apple... So, does anybody know, how to inform apple about the problem?

    "does anybody know, how to inform apple about the problem?"
    http://www.apple.com/feedback/ipod.html

  • Problems with umlaut characters

    Hi,
    i´m on NW04 SP14 and ADS SP14.
    I have implemented a interactive form which is bound to a context node of a webdynpro application. This context node contains some attributes of type string.
    When I populate the attributes with some values containing umlaut characters the interactive form does not display them correctly (there is a space character instead of the umlaut character).
    Is this a bug in the forms solution??
    Thanks in advance.
    Regards
    Sebastian

    Hi Markus,
    ´
    the problem unfortunately still exists. Do you have any suggestions? Is it a bug or some misconfiguration in our environment?
    Thanks for your support.
    Regards
    Sebastian

  • Interactive Reports - problem with umlaute like 'ü'

    Hello,
    when i display an interactive report, all data and umlaute like "ü" was display correct.
    But when i set an filter like "häuser" and then press search, the filtertext was changed to: 'häuser'.
    Is this a language or character-set problem of the ajax engine?
    thank you for any hint.
    Daniel

    hi there,
    this helped me to solve the problem:
    http://www.oracle.com/technology/products/database/application_express/html/freq_solved_faq.html#04
    regards
    frank

  • Problems with Umlaute

    Hi,
    we have implemented a simple RFC Server in .net (using SAP .net Connector 2.0.1). It has a number of string parameters. All works well, except that when the parameters include Umlaut ä/ö/ü etc these are not transmitted to the .net RFC Server.
    The parameters generated in the .net CS look like this:
    [RfcParameter(AbapName = "DATEOFBIRTH",RfcType=RFCTYPE.RFCTYPE_STRING, Optional = false, Direction = RFCINOUT.IN)]
    [XmlElement("DATEOFBIRTH", IsNullable=false, Form=XmlSchemaForm.Unqualified)]
    string Dateofbirth
    We are initialising the RFC Server like this:
    server = new SAPRFCServer.SAP2ADSyncImpl(new string[]{"-a" + _sapConfig.ProgID ,"-g" + _sapConfig.GWHostService,"-x" + _sapConfig.GWService}
    As you can see: We are not setting the codepage. Do we have to? If so to which value?
    We tried changing the RFC Type to UNICODE (on the .net side, but there was no similar type on SAP side).
    Can anybody help?
    Thanks in advance,
    Alex

    Hi,
    we have implemented a simple RFC Server in .net (using SAP .net Connector 2.0.1). It has a number of string parameters. All works well, except that when the parameters include Umlaut ä/ö/ü etc these are not transmitted to the .net RFC Server.
    The parameters generated in the .net CS look like this:
    [RfcParameter(AbapName = "DATEOFBIRTH",RfcType=RFCTYPE.RFCTYPE_STRING, Optional = false, Direction = RFCINOUT.IN)]
    [XmlElement("DATEOFBIRTH", IsNullable=false, Form=XmlSchemaForm.Unqualified)]
    string Dateofbirth
    We are initialising the RFC Server like this:
    server = new SAPRFCServer.SAP2ADSyncImpl(new string[]{"-a" + _sapConfig.ProgID ,"-g" + _sapConfig.GWHostService,"-x" + _sapConfig.GWService}
    As you can see: We are not setting the codepage. Do we have to? If so to which value?
    We tried changing the RFC Type to UNICODE (on the .net side, but there was no similar type on SAP side).
    Can anybody help?
    Thanks in advance,
    Alex

  • 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

  • Problems with german umlauts when Migration from MS Access to Oracle

    When I make a Migration from MS Access 97 to Oracle 8.1.5, I have Problem with the germans characters (umlauts). The Oracle is using the rigth character Set for german characters. What can I do? Is it e problem from the MS Access ODBC Driver or the Oracle ODBC Driver?

    Is your character set for Oracle set up to UTF8??

  • SAP Gui 7.20 PLevel 3, ALV Problems with German Umlauts u00FCu00F6u00E4...

    Hi,
    we have updated our SAP Gui to version 7.20 lately and have some serious problems now with entering German Umlauts 'üöäÜÖÄß' into any editable ALV grid.
    This means when typing in e.g. 'ü', the grid immediately removes this character and replaces it by, well, by nothing. It just ignores this character at all.
    SAP Gui is currently at patch level 3 . The correct version is 7200.1.3.3190, build 1196830. Running German Windows XP clients with service pack 3. ERP is running SAP ECC 6.0.
    Is this a known problem? Has sbdy. a workaround this?
    Edit: Just found the release notes for SAP Gui 7.20 Lvl 3:
    2010/09/02     Texts get garbled while typing umlaut character in ALVGrid, Note 1503081
    This note, however, is not open for public view. OTH this means SAP was aware of this problem and tried to correct it to no avail so far.
    Thanks,
    Michael
    Edited by: Michael Fritz on Nov 19, 2010 11:19 AM

    Hi Martin,
    where did you get this info? Any official SAP note available? Do you encounter similar problems?
    We, too, noticed that uploading and downloading files from directories with German Umlauts, this fails now,too. There may be problems with files, too, however, we did not check this so far. The previous SAP Gui, I guess it was 7.10, didn't have any problems with this.
    I start wondering if SAP Germany have ever tested this? Or do they not use Umlauts anyway

  • 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

  • Problem with german characters (Umlaute) when working with JDev for Linux

    Hallo ...,
    i have a site in uix code under Linux. When i want to use ... confirm("...löschen...?") the JDeveloper can't handle the ö. When i want to use ö i've got an error. It's only when i work under Linux. When i make the same under Windows i can use ä, ö, ü. What can i do?
    Any help is appreciated.
    Thank you

    Tom Gewecke wrote:
    w/ all the keyboards and language settings.
    What do you mean by that? The problem being talked about here is an inability to make French accented characters on a German keyboard. What is your problem exactly?
    I've posted here because I guess it may be the same bug.
    After upgrading I wasn't able to do special characters, including some accented vocals, like "ì", very common in italian language.
    Then I've added an english keyboard, removed the italian one and added it again, so the problem with missing accented vocals was solved.
    I still have the same problem with special consonants, like "z" and "c": if I hold my thumb on such letters, I have no options like, say, "ż" (such characters are very important for my field (linguistics) and if Apple won't solve this problem I'll be forced to look elsewhere).

  • Problem with PDF export and embedded font (characters disappear)

    Designer: Crystal Reports 2008 SP 2
    Engine: CR4E 2.0 SP2 (runtime_12.2.203)
    Hi there!
    we found a problem in the pdf export. It seems like there would be a problem with the embedded fonts, the problem is as follows:
    Rpt file with, for example only a text box which contains the german string " Änderungs Schlüssel ".
    Export the Rpt file with CR4E to a pdf file.
    When we open the pdf file in Adope Reader 8, the text appears to be correct,
    but if we print the PDF file from the Adope Reader, the text changes to " nderungs Schl sselu201C,
    here we are missing ther german umlaute.
    When we open the file for example with an alternative PDF reader like Foxit Reader, there they are also missing.
    After i found some posts here in the forum, there are people facing the same problem, since i couldn't find a solution in the forum, we build a little workaround for it that works for us.
    For all of you that have the same problem here the workaround:
    We used the IText JAVA library, this jar can can help as to fix the PDF file so the text is displayed correctly.
    Here the code:
    ReportClientDocument doc = new ReportClientDocument();
    doc.setReportAppServer(ReportClientDocument.inprocConnectionString);
    doc.open("C:\XY.rpt", OpenReportOptions._openAsReadOnly);
    //... database logon,.....
    InputStream inputStream = doc.getPrintOutputController().export(ReportExportFormat.PDF);
    inputStream = PDFHealer.heal(inputStream);
    //... write the stream some where

    The helper class using IText:
    import java.io.ByteArrayInputStream;
    import java.io.ByteArrayOutputStream;
    import java.io.IOException;
    import java.io.InputStream;
    import com.lowagie.text.Document;
    import com.lowagie.text.DocumentException;
    import com.lowagie.text.pdf.PdfContentByte;
    import com.lowagie.text.pdf.PdfImportedPage;
    import com.lowagie.text.pdf.PdfReader;
    import com.lowagie.text.pdf.PdfWriter;
    public class PDFHealer
       public static InputStream heal(InputStream in) throws DocumentException, IOException
          try
             ByteArrayOutputStream out = new ByteArrayOutputStream();
             PdfReader reader = new PdfReader(in);
             // we retrieve the total number of pages
             int n = reader.getNumberOfPages();
             // step 1: creation of a document-object
             Document document = new Document();
             // step 2: we create a writer that listens to the document
             PdfWriter writer = PdfWriter.getInstance(document, out);
             // step 3: we open the document
             document.open();
             // step 4: we add content
             PdfContentByte cb = writer.getDirectContent();
             int i = 0;
             while( i < n )
                document.newPage();
                i++;
                PdfImportedPage page1 = writer.getImportedPage(reader, i);
                cb.addTemplate(page1, 0, 0);
             // step 5: we close the document
             document.close();
             ByteArrayInputStream ret = new ByteArrayInputStream(out.toByteArray());
             out.close();
             return ret;
          finally
             in.close();

  • Problems with decoding an latin1-encoded url

    Hi,
    i have a problem with decoding german umlaut-characters from an URL.
    I'm using Tomcat 5.5 on a Linux server and one on a windows machine for development. Both webapps have the same configurations.
    A servlet decodes the URL-String, parses it and stores the parsed data into a mysql-DB.
    For decoding the query-string i'm using org.apache.commons.codec.net.URLCodec.URLCodec.decode .
    Here's the code:
    String unparsedParameters = request.getQueryString();
    URLCodec codec = new URLCodec("ISO-8859-1");
    result = codec.decode(unparsedParameters);Here an example for a query-string: http://servername:8080/servlet/Import?Etwas%20wurde%20am%2025.08.2010%2010%3A16%3A50%20*ge%E4ndert*
    On the windows machine the word "*ge&auml;ndert*" is decoded correctly. But on the linux server i get "*ge?ndert*". It makes no difference if i write the result into the database or just into a logfile.
    Can anyone help?
    Thanks in advance.
    Edited by: sol1640 on Aug 26, 2010 5:59 AM

    Problem resolved.
    Instead of using the decode-method as described in my fist message now i'm doing the folowing:
    fURLDecodigCharset = "ISO8859-1";
    byte[] bytes = originalParam.getBytes(fURLDecodigCharset);
    byte[] decodeUrl = URLCodec.decodeUrl(bytes);
    result = new String (decodeUrl, fURLDecodigCharset);because the method "decode" decodes the string by using the defaultcharset. And that was the problem.
    >
    The default charset is determined during virtual-machine startup and typically depends upon the locale and charset of the underlying operating system.
    >
    Thats why i've got different behaviours on different systems.
    Thanks

  • Problems with Special Characters in DBs...

    We have just moved a set of tables from one db on one server to another db on another server. the only problem is that some special characters held within data on the tables aren't showing up properly on the new db. characters such as a circle with an 'R' in (as in registered trademark), or vowels with umlauts over them.
    THe db is used by a website and it is the development version of the website which uses the new db that is not displaying the characters properly. The characters are also displayed incorrectly within sql plus 3.3.
    If anyone could point out why the new db is not storing the characters correctly i would unmeasurably grateful.
    Thanking you in advance
    Ewan Gibb.

    Hello, thanks for you reply. I had to rewrite your code a little, and I think that your code would not really compile, if you tried yourself :-)
    I ended up with something like this:
    our environment is running in 1.4 mode, so I could not use the for-each loop :-(
    public String printEntities(String s) {
         char[] sArray = s.toCharArray();
         StringBuffer sb = new StringBuffer();
           for (int i = 0; i < sArray.length; i++) {
             if (sArray[i] > 256)
                  sb.append("&#x" + Integer.toHexString(sArray) + ";");
         } else
              sb.append(sArray[i]);
         return sb.toString();

  • Problem with mutated vowel

    Hello,
    since I use Acrobat 9.0, I have a problem with the display of one mutated vowel: when I copy a text from an Acrobat-generated PDF-document and paste it into a Word document (Office 2004 and Office X) only the display of the German "ü" is not correct, when I use the "Optima" or "Arial" fonts.
    With the Arial font an "u" followed by a square symbol is displayed.
    With the Optima font the two points are shifted to the right side.
    "ä" and "ö" and all capital letters are displayed correctly.
    When I try "find/replace" in Word, the incorrect "ü" is not found.
    Does anybody know a solution for this problem?
    Your help and hints are appreciated.
    Volker

    Hey Paul and Graffiti,
    thank you for your hints. The umlaute (mutated vowels - ä,ö,ü) are direct keys on a German keyboard. So it's not the problem to find the "ü" or a keystroke to insert. The problem seems to be in the step of conversion from the Acrobat and the display in a text editor after pasting.
    Fonts like Baskerville, Big Caslon, Courier, Futura, Geneva, Helvetica, Lucida Grande, Palatino display the lower "ü" correctly.
    Arial, Times, Times New Roman and all "TTF-fonts" don't, if I paste. When typed directly, the ü is displayed correctly.
    Unfortunately, applications to regulatory health authorities require the font Times New Roman. Of course, I could correct each vowel by deleting and typing "ü" by hand, but my manuscripts are normally about 50 pages . . .
    Volker

  • Charset Problem with WB_XML_LOAD

    Hi all
    My environment 11gr2 on Linux
    one DB with NLS_CHARACTERSET     AL32UTF8
    second DB NLS_CHARACTERSET     WE8MSWIN1252
    I have the following Problem when loading xml Files with WB_XML_LOAD:
    The code works fine as long I have no umlaut on both databases.
    With umlaut the load of the File fails on DB with AL32UTF8 , but works with WE8MSWIN1252
    I get the following error:
    ORA-20007: Error occurred while retrieving XML document.
    Base exception: null
    ORA-06512: at "OWBSYS.WB_XML_LOAD_F", line 12
    ORA-06512: at "OWBSYS.WB_XML_LOAD", line 4
    ORA-06512: at line 28
    The xml File comes with <?xml version="1.0" encoding="ISO-8859-1" standalone="yes"?>
    Any idea?
    Thanks in advance
    Patrick

    While creating XSL for use with wb_xml_load you may rely on almost all functions available in Oracle XDK. I’m not sure about calls to external Java classes (at least they should be available at you Oracle DB environment) and working with external documents (according to possible base URI resolution and resource access issues). But all standard XSL syntax will be at your service.
    As far as wb_xml_load works on top of the Oracle XSU framework you cold model and test you loading procedure with help of XSQL framework, for example. Complete documentation is available as a part of Oracle XDK distributive.

Maybe you are looking for