[
https://issues.apache.org/jira/browse/IO-829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17801079#comment-17801079
]
Elliotte Rusty Harold commented on IO-829:
------------------------------------------
Might be feasible to make charset another parameter on AbstractOrigin rather
than a method argument to getReader/getByteArray etc. Throw an
IllegalStateException if one is needed and not yet set. That is, an origin has
a character set that is consulted when converting bytes to chars or vice versa,
rather supplying the charset when the conversion method is called.
> Don't decode and reencode characters in a potentially different charset in
> AbstractOrigin.CharSequenceOrigin.getReader(Charset)
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: IO-829
> URL: https://issues.apache.org/jira/browse/IO-829
> Project: Commons IO
> Issue Type: Bug
> Reporter: Elliotte Rusty Harold
> Priority: Blocker
> Fix For: 2.16.0
>
>
> API level problem. The default character set is used in getInputStream but
> not getReader which calls getInputStream, so there's a mismatch between the
> character sets in play.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
