[
https://issues.apache.org/jira/browse/CODEC-88?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12986622#action_12986622
]
Sebb commented on CODEC-88:
---------------------------
I've just been taking a look - only the encode and decode routines seem to know
anything about the low level details.
The rest of the code is likely to be common.
The I/O streams likewise really only need the underlying Base64 or Base32
instance; I suspect otherwise the code will be identical.
>From [1]
BASE64 characters are 6 bits in length. They are formed by taking a block of
three octets to form a 24-bit string, which is converted into four BASE64
characters.
BASE32 characters are 5 bits in length. They are formed by taking a block of
five octets to form a 40-bit string, which is converted into eight BASE32
characters.
This will make encode and especially decode a bit longer, as they have to deal
with larger blocks of characters, but won't make things intrinsically harder.
Regarding unit tests - we need those whatever imlementation is chosen.
[1] http://www.garykessler.net/library/base64.html
> Base32 encoder
> --------------
>
> Key: CODEC-88
> URL: https://issues.apache.org/jira/browse/CODEC-88
> Project: Commons Codec
> Issue Type: New Feature
> Affects Versions: 1.x
> Reporter: Eric Olander
> Priority: Minor
> Attachments: Base32.java
>
>
> Any chance of getting Base32 encoding support along the lines of the existing
> Base64 encoder?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
