Home/ Questions/Q 499261
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T05:58:03+00:00

I have a problem with turkish special characters on different machines. The following code:

  • 0

I have a problem with turkish special characters on different machines. The following code:

String turkish = "ğüşçĞÜŞÇı";

String test1 = new String(turkish.getBytes());
String test2 = new String(turkish.getBytes("UTF-8"));
String test3 = new String(turkish.getBytes("UTF-8"), "UTF-8");

System.out.println(test1);
System.out.println(test2);
System.out.println(test3);

On a Mac the three Strings are the same as the original string. On a Windows machine the three lines are (Printed with the Netbeans 6.7 console): 

?ü?ç?Ü?Ç?
ğüşçĞÜŞÇı
?ü?ç?Ü?Ç?

I don’t get the problem.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team
    String test1 = new String(turkish.getBytes());

    You’re taking the Unicode String including the Turkish characters, and turning it into bytes using the default encoding (using the default encoding is usually a mistake). You’re then taking those bytes and decoding them back into a String, again using the default encoding. The result is you’ve achieved nothing (except losing any characters that don’t fit in the default encoding); whether you have put a String through an encode/decode cycle has no effect on what the following System.out.println(test1) does because that’s still printing a String and not bytes.

    String test2 = new String(turkish.getBytes("UTF-8"));

    Encodes as UTF-8 and then decodes using the default encoding. On Mac the default encoding is UTF-8 so this does nothing. On Windows the default encoding is never UTF-8 so the result is the wrong characters.

    String test3 = new String(turkish.getBytes("UTF-8"), "UTF-8");

    Does precisely nothing.

    To write Strings to stdout with a different encoding than the default encoding, you’d create a encoder something like new OutputStreamWriter(System.out, "cp1252") and send the string content to that.

    However in this case, it looks like the console is using Windows code page 1252 Western European (+1 ATorres). There is no encoding mismatch issue here at all, so you won’t be able to solve it by re-encoding strings!

    The default encoding cp1252 matches the console’s encoding, it’s just that cp1252 doesn’t contain the Turkish characters ğşĞŞı at all. You can see the other characters that are in cp1252, üçÜÇ, come through just fine. Unless you can reconfigure the console to use a different encoding that does include all the characters you want, there is no way you’ll be able to output those characters.

    Presumably on a Turkish Windows install, the default code page will be cp1254 instead and you will get the characters you expect (but other characters don’t work). You can test this by changing the ‘Language to use for non-Unicode applications’ setting in the Regional and Language Options Control Panel app.

    Unfortunately no Windows locale uses UTF-8 as the default code page. Putting non-ASCII output onto the console with the stdio stream functions is not something that’s really reliable at all. There is a Win32 API to write Unicode directly to the console, but unfortunately nothing much uses it.

    • 0