[
https://issues.apache.org/jira/browse/IO-315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13238278#comment-13238278
]
Sebb commented on IO-315:
-------------------------
I don't think this is a good idea.
There are a lot of different encodings, and who is to say which ones are
"useful"?
There would still need to be a way to use the String encoding to allow for
encodings that are not provided by the interface.
Also, the code would still need to catch {{UnsupportedEncodingException}}.
As far as I know there is no requirement for a Java class-library to support
any specific encodings, though it would be a fairly useless implementation that
did not support UTF-8.
> Replace all "String encoding" parameters with a value type
> ----------------------------------------------------------
>
> Key: IO-315
> URL: https://issues.apache.org/jira/browse/IO-315
> Project: Commons IO
> Issue Type: New Feature
> Components: Streams/Writers
> Affects Versions: 2.1
> Reporter: Aaron Digulla
>
> Please create an interface "Encoding" plus a set of useful defaults (UTF_8,
> ISO_LATIN_1, CP_1250 and CP_1252).
> Use this interface in all places where "String encoding" is used now. This
> would make the API more reliable, improve code reuse and reduce futile catch
> blocks for {{UnsupportedEncodingException}}.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
