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 'ä' 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

Similar Messages

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

XML and german Umlaut

Hello everyone,
i am writing a little application that uses SAX to parse XML documents and i am having a bit of a problem with german Umlaut (e.g. �, �, �). I looked up the entities that are commonly used in the internet, so for example � becomes either ä or ä , but now for some incomprehensible weird reason those entities are changed into something like for example ä...
Could anybody help me out with this problem? I am completely lost and don't even know what's going on here any more. Maybe my PC is developing a vicious life of its own...
Thanks
Chris

Here's what's happening, then.
Your XML is being written in UTF-8. This is the default encoding for XML and it represents characters that aren't in the ASCII character set by 2 or more bytes. For Latin accented characters it uses 2 bytes. When you read that file back into your program, you must specify the encoding; if you don't, then the system will incorrectly assume that the file is encoded in whatever is the default for your system. To do this:Reader r = new InputStreamReader(new FileInputStream(yourFile), "UTF-8");

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

German Umlaute don't work after upgrading to Yosemite with Japanese Romaji Layout set on U.S.

Hi everyone,
previously i could just use [ALT] + [U] and then press [A] / [a] / [U] / [u] / [O] / [o] to generate the german umlaut version.
After installing Yosemite this does not work anymore, which is kinda frustrating. Cause it forces me to add another keyboard layout and switch when i have to write a german umlaut.
I was previously using 'Input Source' > 'Japanese' > Enabled Romaji (Romaji layout was set to U.S.) & Hiragana.
For testing purpose i added the Standard U.S. Layout and writing the Umlaut with the keyboard shortcut still works there. So that's why i think this is a Romaji specific bug.
Has anyone any idea what's wrong ? Did Apple change something ?
Best Regards

Before I stumbled upon this thread, there was no flag at all. I had the character viewer there because pre-Yosemite it was the only way to access emoji (and things like arrows and other special symbols) in many apps (and still is for my Adobe CS5 apps). Additionally, I would use the keyboard viewer from time to time as a way to learn which keys to use for other special symbols (bring up the keyboard viewer and press option or shift-option or other combinations and it would show you a preview of what each key would generate).
While reading this thread, I added more input sources (US International and US Extended) and would see the flags. The flags replaced the previous character/keyboard viewer menu icon. I switched between each flag to test my issue under each, to no avail. Then I tried adding the Spanish keyboard but still had the same issue.
Now I've removed all the input sources except the primary US keyboard. There is no longer a flag in my menu, it's gone back to the character viewer icon.
The issue is still there. When I type option-r, u, or g, in any app nothing happens at all.
Unfortunately, neither auto-substitution nor press-and-hold work in Adobe CS5 apps, which is where I need to use these special characters the most.
Thank you for reaching out

Legend map request with german umlaut

Hello,
i have a problem sending a legend map request that contains a german umlaut.
I'm trying to use the pl/sql function for sending and parsing a xml request from the mapviewer documentation (chapter 3.1.16, example 3-19).
my request looks like this
<map_request datasource="mvdemo" format="PNG_URL">
<legend bgstyle="fill:#ffffff;stroke:#ffffff" profile="MEDIUM">
    <column>
      <entry style="C.YELLOW" text="Übernahme"/>
    </column>
</legend>
</map_request>The resulting image does not contain the umlaut Ü but a little square instead.
I tried replacing the Ü with Ü ;
<map_request datasource="mvdemo" format="PNG_URL">
<legend bgstyle="fill:#ffffff;stroke:#ffffff" profile="MEDIUM">
    <column>
      <entry style="C.YELLOW" text="Übernahme"/>
    </column>
</legend>
</map_request>This works when i manually send the request on the mapviewer map request page, but it doesn't work when i use the pl/sql function.
The documentation says that the request has to be url encoded, so i tried using utl_url.escape on the whole request and on only the umlaut. Both doesn't work.
Thanks for help in advance,
Dirk

Hi Cleber,
which MapViewer version are you using? This may be related with the PDF graphics library version. This library has been modified to better handle the legend texts. I tested your request and it appears to be OK with the current library. You can send me (by email) a picture of your legend, and I will confirm if this has been fixed.
Joao

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 OK in Test Environment, Question Marks (??) in production

Hi Sun Forums,
I have a simple Java application that uses JFrame for a window, a JTextArea for console output. While running my application in test mode (that is, run locally within Eclipse development environment) the software properly handles all German Umlauts in the JTextArea (also using Log4J to write the same output to file-- that too is OK). In fact, the application is flawless from this perspective.
However, when I deploy the application to multiple environments, the Umlauts are displayed as ??. Deployment is destined for Mac OS X (10.4/10.5) and Windows-based computers. (XP, Vista) with a requirement of Java 1.5 at the minimum.
On the test computer (Mac OS X 10.5), the test environment is OK, but running the application as a runnable jar, german umlauts become question marks ??. I use Jar Bundler on Mac to produce an application object, and Launch4J to build a Windows executables.
I am setting the default encoding to UTF-8 at the start of my app. Other international characters treated OK after deployment (e, a with accents). It seems to be localized to german umlaut type characters where the app fails.
I have encoded my source files as UTF-8 in Eclipse. I am having a hard time understanding what the root cause is. I suspect it is the default encoding on the computer the software is running on. If this is true, then how do I force the application to honor german umlauts?
Thanks very much,
Ryan Allaby
RA-CC.COM
J2EE/Java Developer
Edited by: RyanAllaby on Jul 10, 2009 2:50 PM

So you start with a string called "input"; where did that come from? As far as we know, it could already have been corrupted. ByteBuffer inputBuffer = ByteBuffer.wrap( input.getBytes() ); Here you convert the string to to a byte array using the default encoding. You say you've set the default to UTF-8, but how do you know it worked on the customer's machine? When we advise you not to rely on the default encoding, we don't mean you should override that system property, we mean you should always specify the encoding in your code. There's a getBytes() method that lets you do that.
CharBuffer data = utf8charset.decode( inputBuffer ); Now you decode the byte[] that you think is UTF-8, as UTF-8. If getBytes() did in fact encode the string as UTF-8, this is a wash; you just wasted a lot of time and ended up with the exact same string you started with. On the other hand, if getBytes() used something other than UTF-8, you've just created a load of garbage. ByteBuffer outputBuffer = iso88591charset.encode( data );Next you create yet another byte array, this time using the ISO-8859-1 encoding. If the string was valid to begin with, and the previous steps didn't corrupt it, there could be characters in it that can't be encoded in ISO-8859-1. Those characters will be lost.
byte[] outputData = outputBuffer.array();
return new String( outputData ); Finally, you decode the byte[] once more, this time using the default encoding. As with getBytes(), there's a String constructor that lets you specify the encoding, but it doesn't really matter. For the previous steps to have worked, the default had to be UTF-8. That means you have a byte[] that's encoded as ISO-8859-1 and you're decoding it as UTF-8. What's wrong with this picture?
This whole sequence makes no sense anyway; at best, it's a huge waste of clock cycles. It looks like you're trying to change the encoding of the string, which is impossible. No matter what platform it runs on, Java always uses the same encoding for strings. That encoding is UTF-16, but you don't really need to know that. You should only have to deal with character encodings when your app communicates with something outside itself, like a network or a file system.
What's the real problem you're trying to solve?

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

German Umlauts

The chart does not display German umlauts. Only English characters are displayed correctly. Is there a codepage problem?

Hi,
Usually this is caused by a missing or wrong configuration of the IGS fonts. Make sure that both chart interpreters are configured as desribed in note 596825 (gfwchart) and note 531668 (xmlchart).
Most UNIX boxes do not have TrueType font files. Therefore it's important to have the SAP IGS font files: note 1028690 tells you where to get the four Arial Unicode font files from and how to configure them appropriately.
Thanks,
Venkat

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

SimpleBulkloader and German Umlauts?

Hi all,
i have used the SimpleBulkLoader Sample with success, but when i would like to upload a xml-file with german umlauts i get the following error message:
Has anybody a solution for me????
Many Thanks
Achim
java.sql.SQLException: Keine weiteren Daten aus Socket zu lesen
     void oracle.jdbc.dbaccess.DBError.throwSqlException(java.lang.String, java.lang.String, int)
          DBError.java:134
     void oracle.jdbc.dbaccess.DBError.throwSqlException(int, java.lang.Object)
          DBError.java:179
     void oracle.jdbc.dbaccess.DBError.check_error(int)
          DBError.java:1160
     short oracle.jdbc.ttc7.MAREngine.unmarshalUB1()
          MAREngine.java:963
     byte oracle.jdbc.ttc7.MAREngine.unmarshalSB1()
          MAREngine.java:893
     void oracle.jdbc.ttc7.Oall7.receive()
          Oall7.java:369
     void oracle.jdbc.ttc7.TTC7Protocol.doOall7(byte, byte, int, byte[], oracle.jdbc.dbaccess.DBType[], oracle.jdbc.dbaccess.DBData[], int, oracle.jdbc.dbaccess.DBType[], oracle.jdbc.dbaccess.DBData[], int)
          TTC7Protocol.java:1889
     int oracle.jdbc.ttc7.TTC7Protocol.executeFetch(oracle.jdbc.dbaccess.DBStatement, byte, oracle.jdbc.dbaccess.DBDataSet, int, oracle.jdbc.dbaccess.DBDataSet, int)
          TTC7Protocol.java:955
     void oracle.jdbc.driver.OracleStatement.executeNonQuery(boolean)
          OracleStatement.java:2053
     void oracle.jdbc.driver.OracleStatement.doExecuteOther(boolean)
          OracleStatement.java:1940
     void oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout()
          OracleStatement.java:2709
     int oracle.jdbc.driver.OraclePreparedStatement.executeUpdate()
          OraclePreparedStatement.java:589
     boolean oracle.jdbc.driver.OraclePreparedStatement.execute()
          OraclePreparedStatement.java:656
     void oracle.otnsamples.xmldb.simplebulkloader.examples.SimpleBulkLoader.uploadXMLFile(java.sql.Connection, oracle.sql.CLOB, java.io.File)
          SimpleBulkLoader.java:187
     int oracle.otnsamples.xmldb.simplebulkloader.examples.SimpleBulkLoader.uploadDirectory(java.sql.Connection, oracle.sql.CLOB, java.io.File)
          SimpleBulkLoader.java:143
     void oracle.otnsamples.xmldb.simplebulkloader.examples.SimpleBulkLoader.doBulkLoad(java.lang.String[])
          SimpleBulkLoader.java:94
     void oracle.otnsamples.xmldb.simplebulkloader.examples.SimpleBulkLoader.main(java.lang.String[])
          SimpleBulkLoader.java:205

I know there are various versions of ldapsearch which have differing qualifiers. The one that comes with SUN ONE or iPlanet has the qualifier of -e which means that it will print out german characters. We had this trouble with spanish characters.
However other versions of ldapsearch do not have this qualifier and hence any such data comes out as binary.
If your java application uses ldapsearch it must have a qualifier like this. Perhaps the java application can call the ldapsearch function provided by SUN ONE.
John reddington

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

German umlauts and WLS...... (once again)

Hi
i'm using wls6.0 sp1 on a NT(4.0 Sp6) and on a Sun Solaris 6. if i try
to POST (using jsp) some data containing umlauts, an invalid character
('?') will be showed instead of the umlaut on solaris. the same
procedure works well on NT.
simply try the http://[myServer]:7001/console/..... application and
enter a "ä" in a "notes" tab of the wls server settings (wherever you
like).
is this a bug or a feature ? .->
idealy i would like to use german-umlauts.... so HELP !
thanx 4 ur answer
rsc

Hello Rolf,
It looks to me that the code conversion table between Unicode and the german
code page in JDK is not correct, or you may be running on the wrong locale
(codepage).
To verify that, use native2ascii.
1. Edit a file that has the german-umlauts and save it
2. execute native2ascii filename_input filename_output
3. execute native2ascii -reverse filename_output filename_output2
4. Open filename_output2 to see if it goes to ?
If it went to ?, you are in one of the above.
Reiji

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

Wrong coding of german umlaut in XML/XSLT output

Similar Messages

Maybe you are looking for