[solved] us-keyboard and german umlauts

hello
is it possible to get umlauts on a us keyboard? i know that debian has an us_de layout,which allows umlauts on us kbd, but i couldn't find one in arch...
any suggestions/solutions?
Last edited by kriz (2010-02-06 17:31:50)

I'm Dutch, but we also have a sort of "umlaut" on some letters, but less often than you Germans
I have this in my /etc/hal/fdi/policy/10-keymap.fdi:
<merge key="input.xkb.layout" type="string">us</merge>
<merge key="input.xkb.variant" type="string">altgr-intl</merge>
<merge key="input.xkb.options" type="string">eurosign:5</merge>
So I use the AltGr as a Compose key when I want to type some special characters.
For "ü" (we dont use that, but you do afaik?), I do:
1. Press AltGr + " # (" = Shift + ' , so it's actually: AltGr + Shift + ' ), and let go. Nothing will appear on screen yet.
2. Press u
Tadaa: ü
Just like the deadkeys you would have as a default in Windows, but then using the Compose key to get there. I happen to write code from time to time, so I like it when I can get " directly instead of having to press Space to get it on screen after pressing ".
But if you want the deadkeys behaviour, simply use that variant instead or whatever you need to get that working.
There is a nice list, I believe the exact file is listed in the wiki of Xorg somewhere at keyboard section.
Last edited by Ultraman (2010-02-05 20:58:47)

Similar Messages

Howto set up proper utf-8 locales and german umlaute?

Hi there,
have some issues here and i think it has something to do with my locales... I have them since one of the last updates i think...
First problem:
In Kopete, i can send the german "umlaute" (ä, ö, ü) to others and they are sent and displayed correctly at their side... But when they send me these characters, i get only a square and a deleted next-letter-in-the-word by them. This happens with every theme and font combination in kopete. Here is an example:
Second problem:
In Konsole, the "umlaute" are correctly displayed on my folders, but in the messages i get the chars are simply deleted and not visible. This happens in the VC and in Xorg too. Here is another example:
(It should mean "Keine Handbuch Seite für pacman.conf")
My config:
I think i have configured my System properly, well at least i hope that Here are the relevant parts of my config files:
/etc/rc.conf:
LOCALE="de_DE.utf8"
KEYMAP="de"
CONSOLEFONT=
CONSOLEMAP=
/etc/profile:
export LANG="de_DE.utf8"
export LANGUAGE="de_DE.utf8"
/etc/locale.gen:
de_DE.UTF-8 UTF-8
en_US.UTF-8 UTF-8
And "locale -a" gives me:
C
POSIX
de_DE.utf8
en_US.utf8
The fonts I use:
KDE GUI: Bitstream Vera Sans (everywhere)
Y-Terminal (Konsole) Font: Bitstream Vera Sans mono
So, how can i configure a proper german utf-8? I have already searched the forums (both here and the DE one) and the wiki, but found no solution to this....
THX
Funkyou

Thx for the suggestions, but none of them seems to solve it...
baze:
This line was already uncommented and i have generated my locales for several times now... I have updated my post with the uncommented lines in /etc/locale.gen, just to collect all information...
Romashka:
Ok, but what if the two variables contain the same content? I mean, when i define LANG="de_DE.utf8" in /etc/profile and it is then overwritten by /etc/profile.d/lang.sh with LANG="de_DE.utf8", then this is simply the same variable defined twice with the same content... I have tried to unset the one in /etc/profile, but it did not solve it...
As for CONSOLEFONT, i had never one defined, can anyone suggest me a proper one? And the other question is: Its not working on the terminals, but it is also not working in Xorg, so is this really a CONSOLEFONT issue?
I have tried another thing and switched my locales to de_DE@euro ISO-8859-15, and with this setting the chars appear correctly... But i cannot be the only one where it does not work, i feel so excluded without UTF-8
Have also tried another terminal in Xorg... In XTerm the chars are not deleted like in Kopete or on the VC, but i see an inverted question mark instead of them...

LR, PS and german umlaute

With a german umlaut (ä, ö, ü) within the directory name, I experienced (and was able to reproduce) the following issue:
When I trie to pass a photo from Lightroom 2.1 RC1 to Photoshop CS3, then Photoshop starts but instead of opening the photo it shows an input window "Open as...".
The same procedure works fine without any german umlaut.

I think by now that it is obvious that we have to accept that the narrow minded Americans at adobe do not realize, or care that there is a world outside of the US. If you stick to 7 bit ASCII and get an American keyboard you can use LR as intended, otherwise blame your self.
Lennart

RMI server and german umlaute

My rmi server does not show german umlaute after rebooting the linux box. It is started by a script in init.d/rc5. The script calls a C routine that really starts the server. The crazy thing is that if I remove the script from init.d/rc5 and call it manually after reboot everything is ok.

Sorry, I did not explain clearly, the server is the backend, the frontend is a swing application that is started by jnlp and communicates via rmi with the server. In the swing application there is a table filled with values coming from a database. In the database german umlaute are ok, in the swing frontend question marks and square boxes are shown after the linux box is rebooted.

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");

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

Resource boundles and german umlaute

Hello,
I'm new to 18n, so i have an important question. I'm developing an internationalized web application (currently for German and English Language). How do i write Umlaute like �,�,�... into the the ResourceBundle files, so that they are displayed correctly on the html pages. The Charset of teh webpages is set to: charset=iso-8859-1.
Do i have to write <code>ä</code> for �?
Thanks for your help. Nice place.
Have a nice day

hello,
there is no problem with the ressource files itself, so the application is already internationalized. But i don't think in an elegant way for the German locale. In the Res Files we write thinks like:
SOMEKEYFORIT = Bitte tragen sie eine gueltige Zahl ein.
The word "gueltige" is such a problem. Is it recommended to write the html code ü instead of "ue" at this point. Or is there another convention for German Umlaute.
So all in all it works, expect of Umlaute, that are currently not well localized.
Thank You,
Have a nice Day

[Solved] BEPO keyboard and dead keys

Hello!
So, I'm using a French BEPO keyboard, and it works pretty well, till today.
Indeed, today, I wanted to write a greek letter, µ, but I couldn't. This letter is mapped to Alt-Gr+g.
However, when loading the bepo in the console, it's working well (in a TTY). This only affects QT or GTK applications so far (X).
This is the only one not working: my other dead keys just works like a charm (-> ´+i=í…)
My final purpose is to be able to type any simple greek letter as explained here (http://bepo.fr/wiki/Lettre_grecque_sous_Linux). But I need the mu lettre to work first…
I've tried GTK_IM_MODULE=xim, but then my normal deadkeys don't work anymore nor this alt-gr+g.
By default, I use:
export GTK_IM_MODULE=ibus
export XMODIFIERS=@im=ibus
export QT_IM_MODULE=ibus
I also found out that alt-gr+/(L) is not working as a dead key (in order to type ø for example). (http://bepo.fr/wiki/Barre_inscrite)
I should, lastly, say that I use a typematrix keyboard which is build with BEPO on it.
Last edited by jiehong (2012-06-13 12:53:18)

Hi,
I aslo use the BÉPO layout.
The Alt-Gr + G key changed in xorg with the last update of the xkeyboard-config package (happened on June 02 for me): this combination was the 'μ' greek letter, now it is the 'dead_greek' dead character. It is now what it should be so that is fine.
To type the 'μ' letter, you now type Alt-Gr+G, followed by M.
Note that this dead key works for me only if I use the xim input method. With other input method, some dead keys work, some others don't.
I don't use some variables to set the input method, I use dconf-editor (package dconf),
I set the key org/gnome/desktop/interface/gtk-im-module to xim (you don't have to restart for this change to take effect).
When I was trying to configure greek letters before the xkeyboard-config update, I also found out that when I have a ~/.Xcompose file, it kills all the dead keys of my layout, I don't know if this is a bug or if I'm doing something wrong. Try to remove yours.

[Solved] how to write german "umlaute" on US keyboard?

Hi,
I am German, but I use an US-keyboard since it I like it better for writing code. Is there a simple way to map key-combinations to "Umlaute". e.g. like o+windows-key for an "ö".
I'd be happy with a sollution for thunderbird but in case there is an universal trick go for it.
Thanks in advance,
Keen
Last edited by keen90 (2012-01-15 10:02:28)

yep your link helped.
Here the summary what's to do:
1) Get your custom xmodmap
xmodmap -pke > ~/.Xmodmap
2) Use a key to toggle between modes (i used the windows key keycode:133)
change the line in your Xmodmap file to:
keycode 133 = Mode_switch NoSymbol Mode_switch
3) Change the Umlaut keys using this:
https://bbs.archlinux.org/viewtopic.php … 09#p858309
4) make your changes work
modmap ~/.Xmodmap
5) check by typing windows-key+a, windows-key+shift+o, windows-key+s
you should get: äÖß
Note: Don't use this if you run XFCE it will affect your system performance on login. (dead key combinations, freeze)
Last edited by keen90 (2012-01-16 07:21:52)

Java, ldap and german "umlauts"

Hi everybody,
Our developers ran in some problems with german characters "��"etc. They are using Java SDK 4.1 for LDAP for retrieving, creating and updating entries. If names have umlauts like in "J�RG" they are not presented right. Both systems have solaris 8 (engl) and they are using UTF-8 in the java application. As i know the server stores the values also in UTF-8, so why is the presentation wrong? Any idea?
Many thanks
Kai
PS: A perl script has no problems with umlauts.

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

Restful Webservice and German Umlaut

Hello,
i'm trying to setup a restful webservice using Apex 4.2 and Apex Listener 2, but i have problems regarding german unlaute in the json response.
To see if its a configuration error on my side, i did setup an exmaple on apex.oracle.com and there i get the same results.
I added a now row to the table emp, with just the ename as 'öäü'.
Please see the example at http://apex.oracle.com/pls/apex/dwtest/getEmp/
The result looks like this:
{"next":{"$ref":"http://apex.oracle.com/pls/apex/dwtest/getEmp/?page=1"},"items":[{"ename":"Ã¶Ã¤Ã¼"}]}It should look like this:
{"next":{"$ref":"http://apex.oracle.com/pls/apex/dwtest/getEmp/?page=1"},"items":[{"ename":"öäü"}]}The interesting fact is that i sometimes get the desired output, but its net reproducible to me. As browser i tested Firefox, Chrome, IE9 and Opera.
I wonder if i configured something wrong in my browsers or in apex.
If you would like to take a look at the webservide use these credentials:
Workspace: dwtest
Username: testuser
Password: forum
Thanks for help in advance.
Regards,
Dirk

Do you think this could be related to the problem described here? {thread:id=2519567}?
Howard

Problem with semantic search (topicmaps) and german umlauts (ä,ü,ö)

Hello,
i've implemented semantic search like it is described in "How to Enable semantic search.pdf". If i create a synonymlist with a word containing ä,ü or ö; for example "nuts;nüsse", and now i search for nuts, i get the following error message:
<<Error during search occurred - com.sapportals.wcm.WcmException: error parsing XML data (Unsupported character: 68 (:main:, row:37, col:4348)) (Errorcode 7260)>>
If i use "nuts;nuesse" everything works fine and trex finds both search terms.
Is there any possibility to solve this problem?
Thanks,
Sven

Hello Sven
You need to save the .txt-file with UTF-8 encoding. Try opening your synonym.txt-file with notepad and change the encoding to UTF-8. Then you convert the txt-file into the xtm-file and the xtm-file into .db-file.
Kind regards,
Martin

German Umlaute and SQLite3?

I'm struggling with SQLite 3 and German Umlaute (ä, ö, ü, etc.)
It seems as if I cannot do WHERE x LIKE y clauses with German Umlaute recognized. Here's a code excerpt:
const char *sql = "SELECT zip, city, number, mobile, active, remarks FROM rawData WHERE city LIKE ?";
if (sqlite3preparev2(database, sql, -1, &searchCityStatement, NULL) != SQLITE_OK) {
NSAssert1(0, @"Error: Failed to prepare statement with message '%s'.", sqlite3_errmsg(database));
sqlite3bindtext(searchCityStatement, 1, [c UTF8String], [c length], SQLITE_TRANSIENT);
So the idea here is that I search for rows WHERE city LIKE <parameter c>. It works fine without Umlaute. E.g. rows like Berlin, London, etc. are returned. However, when I search e.g. for Lünen, it does not work. I believe that the [c UTF8String] strips out Umlaute, but just using c does not work, either.
Any help?

SQLite does not properly handle accented characters. From the SQLite documentation:
The LIKE operator is not case sensitive and will match upper case characters on one side against lower case characters on the other. (A bug: SQLite only understands upper/lower case for 7-bit Latin characters. Hence the LIKE operator is case sensitive for 8-bit iso8859 characters or UTF-8 characters. For example, the expression 'a' LIKE 'A' is TRUE but 'æ' LIKE 'Æ' is FALSE.).
Although it does not explicitly state it, 'Lünen' LIKE 'Lunen' is FALSE.

German umlauts (and other foreign characters) using UK keyboard

How do I type a umlaut, o umlaut and u umlaut? Also, ss (like a B)?
Holding down Alt and a etc. does not work.

The principle of the thing is that you use the Keyboard Viewer to change the mapping of key codes to character codes, much as you would have used the KeyCaps Utility in the past.
Keyboard viewer enables you to see the results of using the option key if you don't remember the shortcuts Peter gave above. If you know those you just type them. You can also see the result of using special fonts for symbols etc. It does not change the results of hitting a particular key in a particular font.
Because the key graphics are engraved on the keys, changing the mapping of key codes to character codes does not change the key graphics.
Hand up all those who thought it would.
This is a problem for which Apple has several patents in play. These are patents for much improved input methods to interactively change the key graphics when the mapping of key codes to character codes is changed.
Which I am sure we will all enjoy seeing and paying for in the distant future

Macbook pro Late 2011 13.3 inch i7 keyboard and trackpad not working bluetooth showing a cross sign and no usb mouse is detected. Almost dead keyboard and mouse. Earlier same problem used to be solved by opening the lower cover and closing it.

My macbook pro 13.3 inch i7 late 2011 edition has previously encountered unresponsive trackpad and keyboard. To solve that, I used to open the back cover and then close it. It has been working fine since that. Yesterday, same thing happened, this time I noticed that bluetooth icon is showing a cross sign across it and keyboard and trackpad were unesponsive. After some time , everything worked fine and bluetooth sign was back to normal. Then , suddenly it went back to the problem. I shut it down by holding the power button. When I booted it again, I could not login because keyboard and trackpad were not working. I attached a HP mouse it didnt work. I opened the back cover disconnected the battery and then connected it again, didnt worked. Since then , I have tried many things and nothing has solved the problem.

@sanjampet
As you suggested I reset the smc, in the first boot nothing worked. In the second boot, it all worked like a charm. I thought that my problem is resolved now. To test it, I shut it down properly. Next morning, I powered it on, all things i.e, keyboard, trackpad, bluetooth etc. worked and I thought that problem has been solved. When I was just going to visit apple forum to reply you, the same problem reappeared. A sawtooth cross over bluetooth icon, keyboard not working, trackpad not working,no usb mouse working which worked well when it was fine. I reset smc so many times again and again but same problem continued. Isn't it a problem of the firmware?
Next time when it will work, I will update its firmware.
My macbook was bought in dec2011 so no warranty now.

[solved] us-keyboard and german umlauts

Similar Messages

Maybe you are looking for