commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Gregory (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CODEC-239) 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
Date Mon, 25 Sep 2017 16:20:00 GMT

    [ https://issues.apache.org/jira/browse/CODEC-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16179250#comment-16179250
] 

Gary Gregory commented on CODEC-239:
------------------------------------

WRT to whether or to delete patch files. This is where GitHub is better, you just "close"
a PR or keep committing on the same one. It's all tracked. I do not think we have any guidelines
on this but it is a good question. You might as well leave the old patches around, these are
usually small anyway so should not be much of a burden on infra (I hope!) They key is giving
the patch files names that make it easy to track what is what...

> 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
>
>
> 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
(v6.4.14#64029)

Mime
View raw message