SlickEdit Product Discussion > SlickEdit®

German Umlaute in MacOS

(1/2) > >>

The MacOS version of SlickEdit has a problem with the German Umlauts (äöüÄÖÜ). If I press the equivalent key only a small dotted box appears. However, if I enter the <ESC> key to open the command line and then press a Umlaut key the correct character appears in the command line. Has anyone a solution to this problem?

ScottW, VP of Dev:
It sounds like you need to change the font you are using in the editor window. The command line uses a different font by default.

Select Tools > Options > Font to bring up the Font Configuration dialog. Editor windows are controlled by the entry called "SBCS/DBCS Source Windows" or by "Unicode Source Windows", depending on the encoding you are using. The command line is controlled by an entry called "Command Line".

Try using the font used by the Command Line or try picking another font for your source windows that can produce the umlauts correctly.


Changing the font may not fix your problem. There is a known bug that can cause these characters to be botched on input. We will definitely fix this in the next patch/release. There are no great workarounds for this, other than to edit all your files as "UTF-8, no signature" (File>New and File>Open allow you to choose the encoding to use when creating/opening a file).



You are right. I have tried different fonts to solve the problem but no luck. Use the UTF encoding won't work for me since I am creating web pages which our server delivers as 8859-1 content. Is there any information when the patch will be released?

2 ideas:

1) As originally stated: use "UTF-8, no signature" encoding when creating/opening your files. The "no signature" part guarantees that we will not attempt to save/open the file with a signature. As long as typing your umlaute characters never generates Unicode characters (i.e. only SBCS/DBCS characters are generated), then you should be fine since you end up with a file that has no Unicode characters in it.

2) Create/open your files with the "Western European (ISO-8859-1)" encoding ("Latin 9 (ISO-8859-15)" would probably work fine too).

With both of these methods, internally, these files would be opened in a window that uses the "Unicode Source Windows" font (yes, even when specifying ISO-8859-1). If this is a proportional font on your system, and you want to change it, then you can set the font from Tools>Options>Font, pick the "Unicode Source Windows" element, set your font.



[0] Message Index

[#] Next page

Go to full version