German Umlaute ö ü ä on US keyboard

What do I have to do on a US keyboard to get these Umlaute? In windows it works with alt and a number, but that does not work on my mac?
Thanks for your help!!!!!!!!

To expand on Partick's post… you need to press option-u and then the letter you want the umlaut above. So, to do a ü you type option-u and then u.

Similar Messages

[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)

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

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

How to type German Umlauts on an hp desktop

How do I type German umlauts with an English hp desktop keyboard?

The best way to use all kinds of non-english symbols is to go to your keyboard settings and switch your keyboard settings to international. This way you don't have to use codes for everything.
ControlPanel -> Region and Language -> Keyboards and Languages (the tab) -> Change Keyboards -> Add
Pick out "United States - International "
Here is microsoft's guide to using international characters with this keyboard setting: http://support.microsoft.com/kb/306560
You can also use the same path to switch entirely over to a german keyboard configuration, though this can be confusing if you don't have that completely memorized.
I work on behalf of HP (But this isn't my job)
Mark my post as “Accept as Solution" if you feel my post solved your issue, so that others with the same question can find the answer.
Please give me Kudos if I wrote something that helped you.

German umlaute in resource bundles

Hi,
I am localizing an app in german. On windows I can use wordpad or Netbeans to type german umlaute (��) directly into the resource bundles (I have a german keyboard). But I fear, if someone runs this app on e.g. Linux, this does not work. I remember opening such files with an editor on Linux and the umlaute turned into some other strange letters. I think the same happens on english windows installs?
How can I do this right, to be able to run this app on Linux later?
Ingo

Ok, I am answering my own question here, just in case anybody else has the same problem. The solution is: use the native2ascii tool to covert files written with notepad into unicode. Or, use Netbeans to edit the resource Bundles (property files), it saves them in unicode from the beginning.
Ingo

German "Umlaute" in IOS 4.2.1

Hi Apple Team,
If I used German "Umlaute" ‘ä’ <ae>, ‘ü’ <ue>, ‘ö’ <oe> ect. in the past on my iPad I had to hold the letter e.g. the "a" a popup directly show as the first choice the ‘ä’ <ae> or other needet "Umalut".
Since updating my iPad and also iPhone 4 to IOs 4.2.1 I hold the "a" again, the popup with “Umaulte” came up but now I have to go to the right or left to chose the correct letter.
The first choice in the popup is the letter which I already hold to get the popup! More or less this is just one unnecessary step more in getting the correct letter…
This isn’t really an “Apple” innovation I expected in the IOS update!
Could you please fix this for the next IOS update release?
Many thanks
Best regards
Manfred

Hi Craig,
If you choose "German Keyboard" within the settings, it could be directly the wanted “Umlaut”. Simply other characters may shown directly by using other keyboard settings at first.
By the way this was already featured in IOS 3.2 without any issues.
Therefore this is a deterioration comparing usability in IOS 3.1 vs. IOS 4.2.1
Best regards
Manfred

How to add German Umlaut to iWeb?

Hi,
My default language on my site is English. But I want to add German Umlauts to a word. I copied and pasted it from a German site, but Google doesn't recognize the word.
So, is there a way to insert other language characters and still get word recognition by Google?
Thanks
Lars

Hi, my website is http://www.ethnicyum.com/
On the Welcome.html page I am using the word Schwarzwälder Kirsch Torte. The US Google only recognizes Schwarzw as a keyword, but not the entire word.
I used the Keyboard Viewer on the Mac to insert the ä. Is there another way to do it so that Google recognizes the word?

Numbers don't show german umlaut but quick view does

I do have a problem opening CSV files in Numbers.
I have a shared folder with VirtualBox. The virtual HD is formatted in FAT32. With Windows I created a CSV file which contains german umlauts like ÄÖÜ.
When I open the CSV with the "quick view" (press space when file is selected in finder, the CSV is displayed as a nice Table and all Umlauts are OK.
When I double click the CSV file to open it in Numbers, the Umlauts are not displayed. Opening in Text Edit is the same result, no Umlauts.
ö = ^
ß = fl
ü = ¸
ä = ‰
I think this is an encoding problem, but why is "quick view" displaying it correct. I'm confused.
Thanks for any help.

Hello
I cannot find any encoding settings for opening files in Numbers 09.
A simple and obvious solution would be to save CSV file in UTF-8 in FAT32 volume in VirtualBox if possible.
One other method is to copy the CSV file to HFS+ volume and set its extended attributes to specify its text encoding. This method is only changing the metadata of the file and so is less intrusive than to convert the data itself to different text encoding. When text encoding extended attribute is properly set, Numbers 09 (and TextEdit.app set to use "Automatic" encoding option in opening files) will open it in the specified text encoding.
The following AppleScript script might help to set the extended attributes (OSX 10.5 or later only). Recipe is as follows.
A1) Open /Applications/Utilities/AppleScript Editor.app, copy the code of set_latin1_xattr.applescript listed below and save it as application (bundle) in the folder where target CSV files reside.
A2) Double click the saved applet and it will set the com.apple.TextEncoding extended attribute of the *.csv and *.txt files in the same folder where the applet resides to Latin 1 when they are recognised as 'ISO-8859 text' by file(1) command.
-- set_latin1_xattr.applescript
_main()
on _main()
    set p2m to (path to me)'s POSIX path
    if p2m ends with "/" then set p2m to p2m's text 1 thru -2
    set sh to "
# set current directory to parent directory of script (or die)
cd \"${0%/*}\" || exit 1
# add com.apple.TextEnncoding xattr for Latin-1
# for *.csv and *.txt files, of which file info contains 'ISO-8859 text', in current directory
for f in *.{csv,txt}
do
    if [[ $(file \"$f\") =~ 'ISO-8859 text' ]]
    then
        xattr -w com.apple.TextEncoding \"WINDOWS-1252;$((0x0500))\" \"$f\"
    fi
done
    do shell script "/bin/bash -c " & sh's quoted form & " " & p2m's quoted form
end _main
Another method is to convert the text encoding itself as you have already done using TextEdit.app.
The following AppleScript might help to convert text encoding from latin-1 to utf-8 in bulk. Recipe is basically the same as the above.
B1) Open /Applications/Utilities/AppleScript Editor.app, copy the code of convert_latin1_to_utf8.applescript listed below and save it as application (bundle) in the folder where target CSV files reside.
B2) Double click the saved applet and it will convert the text encoding of the *.csv and *.txt files in the same folder where the applet resides to UTF-8 when they are recognised as 'ISO-8859 text' by file(1) command. Also it sets the extended attribute for text encoding accordingly.
-- convert_latin1_to_utf8.applescript
_main()
on _main()
    set p2m to (path to me)'s POSIX path
    if p2m ends with "/" then set p2m to p2m's text 1 thru -2
    set sh to "
# set current directory to parent directory of script (or die)
cd \"${0%/*}\" || exit 1
# make temporary directory
temp=$(mktemp -d /tmp/\"${0##*/}\".XXXXXX) || exit 1
# convert text encoding from ISO-8859-1 to UTF-8
# for *.csv and *.txt files, of which file info contains 'ISO-8859 text', in current directory
for f in *.{csv,txt}
do
    if [[ $(file \"$f\") =~ 'ISO-8859 text' ]]
    then
        iconv -f ISO-8859-1 -t UTF-8 \"$f\" > \"$temp/$f\" \\
        && xattr -w com.apple.TextEncoding \"UTF-8;$((0x08000100))\" \"$temp/$f\" \\
        && mv -f \"$temp/$f\" \"$f\"
    fi
done
# clean up temporary directory
rm -rf \"$temp\"
    do shell script "/bin/bash -c " & sh's quoted form & " " & p2m's quoted form
end _main
Note that the extended attribute is not supported in FAT32 and so the above methods only work in HFS+ formatted volume.
Scripts are briefly tested with Numbers 2.0.5 under OSX 10.5.8 and 10.6.5. Please make sure you have backup CSV files before applying the above scripts.
Good luck,
H

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

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

Adobe Dreamweaver FTP connection doesn't work with german "Umlaut" like "ö" in the severadress

Hi
Today I tried to establish a FTP connection to the serveradress "ftp.möbelverwandlung.com", but I get the error message that the program couldn't connect to the host. As Dreamweaver works perfectly with other serveradresses and I managed to establish a connection to "ftp.möbelverwandlung.com" with other programs, I think that the problem is the german "Umlaut" "ö". Did anyone recognize the same problem and does someone know a solution?
Thank you very much for your help

Here is the English translation of your previous post -
Hello Maximilian,
I got a even looked at my provider. Usually there must pay the original domain for the agreed period and agree a new. However, they show a accommodating for so short "duration" of a few hours like you. Try to contact your ISP phone support.
MfG
Hans-Günter
Anyhow, I think you have covered the options!

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

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

German Umlaute ö ü ä on US keyboard

Similar Messages

Maybe you are looking for