The InputStreamReader and OutputStreamWriter constructors accept a string that represents the name of the character set to use, but the literals that are used for these encodings are not documented and may be platform-dependent. This leads to the possibility of non-portable applications that make API calls with an encoding string that is recognized on one platform, but not another.
This problem could be avoided if the encoding strings are documented as part of the API.
This problem could be avoided if the encoding strings are documented as part of the API.
- duplicates
-
JDK-4099902 java.io.: InputStreamReader character encodings not defined or referenced
-
- Closed
-
-
JDK-4118337 Canonical names are meaningless
-
- Closed
-
-
JDK-4138264 java.io.{InputStreamReader,OutputStreamWriter} should say UTF8, 8859_1 req'd
-
- Closed
-