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

Similar Messages

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

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

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

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

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??

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?

Pages 2.0.2 has problems with German umlaut characters and hangs.

The problem has occured when I had the idea to rename the style names to have exported html files wider accepted by other browsers.
Therefore I tried to rename used style names by replacing encountered umlaut letters by their transcriptions e.g. "Überschrift 1" by "Ueberschrift 1" and so on. But when doing so, the program was freezing while the last changed style name was vanishing and did not come back at all.
Reinhard.
iMac Mac OS X (10.4.9) computer chess programming

I cannot reproduce your problem. I rename überschrift 1 to Ueberschrift. Logically it moves to the bottom of the list, but it is still there and nothing hangs.
Does this happen in all your documents or only one?
Does it happen using all templates or only one?
Are you working in German all the time, or have you switched to English in the mean time?
Do you have access to other computers with the problem, or have you seen it only on yours?
Have you renamed other styles like "Text" or "Titel" without problem?
If you start Pages in English, do you have the same problem?

Character encoding problems with weblogic stax implementation?

Hello all,
While using Stax to parse some XML, we encounter the following exception when the processor reaches the UTF-8 character C3 B1, ('ñ'):
Caused by: Error at Line:1, token:[CLOSETAGBEGIN]Unbalanced ELEMENT got:StudentRegistration expected:LastName
at weblogic.xml.babel.baseparser.BaseParser.parseSome(BaseParser.java:374)
at weblogic.xml.stax.XMLStreamReaderBase.advance(XMLStreamReaderBase.java:199)
We suspect that the processor's encoding might somehow be set to ANSI instead of UTF-8. I have read, in other posts, of a startup property related to web services:
-Dweblogic.webservice.i18n.charset=utf-8
However, this XML is not a web service request, but rather a file being read from disk after an MDB's onMessage() method is called.
Could this setting be affecting stax parsing outside of webservices? Any other ideas?
Thanks!

As far as I know, we don't support changing outbound message encoding charset in 9.x. Both 8.x and 10.x support it. Check [url http://docs-stage/wls/docs100/webserv/client.html#wp230016]here

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

Character encoding problem by Gmail set up as exchange account on IOS mail

It was maybe asked before but I could not find any solution. If someone can help I would appreciate it...
If I set up my gmail, which I use very heavily, as Gmail on the IOS mail installation it would be set up as IMAP and does not push the emails. If I choose it to install as exchange account via m.google.com everything is OK and I get my mails instantly. But the way over exchange disturbs because of the character encoding problem. IOS mail does not show me the turkish or some german characters like "ü" and the mail is almost not readable... By version 1 also as IMAP there is no problem with the characters but I must start IOS mail everytime to see if I have new mail...
Does anyone know a solution for it?
Thanks...
Mel

But I cannot set the the gmail app as standart email program, or? I mean if I want to send a page on safari and click send via email, the mail.app would start and not the gmail.app.... I am using Iphone since a few weeks and as far as I know a customisation is not possible.

Problem copying German Umlauts

Hello every one,
I have a problem copying the German Umlauts (ü,ö,ä) from a pdf file. When I simply copy the text from the pdf file to paste in a text document, they come out like this: ¨u, ¨a, ¨o
Please help me resolve this issue.
Cheers,
makky

Hi,
I have the same Problem.
I´m using Adobe Reader X (10.1.3) with OS X Lion.
If I copy a text with German Umlauts into a HTML-Editor the German 'ü' is diplayed obviously ok and the browser shows it correctly too, but when I move the cursor through the text the German ü are two overlapping letter. Normally it should be one letter, namely the same as entering an ü. (Yes, the charset of my HTML-file is UTF-8 and the file is saved in UTF-8). The first of the two overlapping letters is a "normal" 'u' and the second is the 'COMBINING DIAERESIS' (U+0308) (http://www.fileformat.info/info/unicode/char/308/index.htm).
Before I switched to OS X I used Adobe Reader with Windows 7 and I never had this problem. Strangely the problem only appears with 'ü's. 'Ä's and 'Ö's are copied correctly...
Right now, I suppose there is a bug/feature/whatever in Adobe Reader X using OS X....
Did you find a solution meanwhile?
Torsten

IPhoto doesn`t work correctly with german "umlaut" (ä,ö,ü) in keywords

iPhoto doesn`t work correctly with german "umlaut" (ä,ö,ü) in keywords. They get to ä̈,ö̈, ü̈ when I write the keyword a second time. Can anybody tell me why. Thank you. Heinz

It apparently does not like non-standard English characters - use A-Z and 0-9 adn you should be OK
report to Apple - iPhoto menu ==> provide iPhoto feedback
LN

Wrong email display name with german umlauts (MS Exchange 2003)

We use 6 iPhones with Exchange 2003 and get wrong email display names with german umlauts (ä,ü,ö) - but the email-body is right.
We get special characters instead of umlauts, so the display name split into pieces. Anwering is not posipble - we get a failure-message.
We changed the standard-internet-mailformat on the exchange-server to unicode utf-8. First it works fine, after a few hours the names displays wrong again.
So we use this hotfix:
http://support.microsoft.com/?scid=kb%3Ben-us%3B916299&x=11&y=13
Same result: First it works fine, after a few hours the names displays wrong again at the iPhone.
Any ideas?

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

Cannot renew code signing certificate - maybe bug with german Umlaut?

Hello!
Since one month I expierence a message that I should renew my code signing certificate and today I thought it is time to stop this message.
Because I could not find anything about renewing the certificate in Mountain Lion I used the KB-article that discribes the process for Lion.
http://support.apple.com/kb/HT5358
after that I get this in at my terminal:
sudo /Applications/Server.app/Contents/ServerRoot/usr/sbin/certadmin --recreate-CA-signed-certificate 'myserver.domain.de Signierungszertifikate für Code' 'IntermediateCA_MYSERVER.DOMAIN.DE_1' 7D3E2458
when I press return I get this:
/Applications/Server.app/Contents/ServerRoot/usr/sbin/certadmin Cannot find the certificate: myserver.domain.de Signierungszertifikate für Code
I checked it again and again - I cannot find any typo or something like that - so maybe Mountain Lion wants to renew the certificate in a different way or certadmin cannot cope with german "Umlaute" - "für" - in english for - but I did not gave this name it was given by the system when I setup the server one year ago.
Every hint is welcome, bye
Christoph

I am stupid - I read the KB article again and there it says
"When entering the hexadecimal serial number, ensure that all letters are entered in lower case."
I retyped the command with lower case hex numbers and everything was fine
Bye,
Christoph

Character encoding problem with german umlaut in propertie files

Similar Messages

Maybe you are looking for