Created
June 18, 2013 13:57
-
-
Save zeroDivisible/5805565 to your computer and use it in GitHub Desktop.
Java encoding and String.getBytes() issues. Taken from http://stackoverflow.com/a/12659462/126781
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
It is a bit complicated ... | |
Java tries to use the default character encoding to return bytes using String.getBytes(). | |
The default charset is provided by the system file.encoding property. | |
This is cached and there is no use in changing it via the System.setProperty(..) after the JVM starts. | |
If the file.encoding property does not map to a known charset, then the UTF-8 is specified. | |
.... Here is the tricky part (which is probably never going to come into play) .... | |
If the system cannot decode or encode strings using the default charset (UTF-8 or another one), then there will be a fallback to ISO-8859-1. If the fallback does not work ... the system will fail! | |
.... Really ... (gasp!) ... Could it crash if my specified charset cannot be used, and UTF-8 or ISO-8859-1 are also unusable? | |
Yes. The Java source comments state in the StringCoding.encode(...) method: | |
// If we can not find ISO-8859-1 (a required encoding) then things are seriously wrong with the installation. | |
... and then it calls System.exit(1) | |
So, why is there an intentional fallback to ISO-8859-1 in the getBytes() method? | |
It is possible, although not probable, that the users JVM may not support decoding and encoding in UTF-8 or the charset specified on JVM startup. | |
Then, is the default charset used properly in the String class during getBytes()? | |
No. However, the better question is ... | |
Does String.getBytes() deliver what it promises? | |
The contract as defined in the Javadoc is correct. | |
The behavior of this method when this string cannot be encoded in the default charset is unspecified. The CharsetEncoder class should be used when more control over the encoding process is required. | |
The good news (and better way of doing things) | |
It is always advised to explicitly specify "ISO-8859-1" or "US-ASCII" or "UTF-8" or whatever character set you want when converting bytes into Strings of vice-versa -- unless -- you have previously obtained the default charset and made 100% sure it is the one you need. | |
Use this method instead: | |
public byte[] getBytes(String charsetName) | |
To find the default for your system, just use: | |
Charset.defaultCharset() | |
Hope that helps. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment