[
https://issues.apache.org/jira/browse/CODEC-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16940101#comment-16940101
]
Gary D. Gregory commented on CODEC-239:
---------------------------------------
[~ch...@christopherschultz.net] I still do not like it. What I can see as an
acceptable compromise would be to refactor Base32 with a new constructor that
allows you to pass in the encode table and the decode table. Then your call
site can define whatever it wants.
> Allows "look-alike" characters like 0 (digit zero) and 1 (digit one) as
> aliases for O (uppercase oh) and I (uppercase eye) respectively when decoding
> -----------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CODEC-239
> URL: https://issues.apache.org/jira/browse/CODEC-239
> Project: Commons Codec
> Issue Type: Improvement
> Affects Versions: 1.10
> Reporter: Christopher Schultz
> Priority: Minor
> Labels: patch-available
> Attachments: CODEC-239-2.diff, CODEC-239.diff
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Allowing {{1}} -> {{I}} and {{0}} -> {{O}} can help usability, especially for
> human users who are entering data expected to be in base32-encoded format.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
