On 08/31/2015 06:39 AM, Pádraig Brady wrote:
> There are probably other variants of base64 in use
> (like also transforming the '=' padding char for
> easier to read URLs), and so using the external tr
> solution is more general.
FYI, Base58, base64, and hexadecimal are fairly common
On 02/09/15 20:15, Ray Dillinger wrote:
>
>
> On 08/31/2015 06:39 AM, Pádraig Brady wrote:
>
>> There are probably other variants of base64 in use
>> (like also transforming the '=' padding char for
>> easier to read URLs), and so using the external tr
>> solution is more general.
>
>
On 09/02/2015 03:09 PM, Pádraig Brady wrote:
>> At present there are three incompatible but semi-standard
>> versions of it. Here's a handy URL:
>>
>> https://en.wikipedia.org/wiki/Base58
>>
>> Would coreutils like a command-line tool to do this?
>
> Interesting.
> I think there would need to be
On 31/08/15 15:28, Stephane Chazelas wrote:
> 2015-08-31 14:39:57 +0100, Pádraig Brady:
> [...]
>>> The problem is that `base64' doesn't support the RFC 4648
>>> standard. An obvious work around is to do something akin to
>>> "cat | sed 's/-/+/' | sed 's|_|/|' | base64 --decode"
>>> or whatever
2015-08-31 14:39:57 +0100, Pádraig Brady:
[...]
> > The problem is that `base64' doesn't support the RFC 4648
> > standard. An obvious work around is to do something akin to
> > "cat | sed 's/-/+/' | sed 's|_|/|' | base64 --decode"
> > or whatever (forgive the double sed please). However, it
>
On 31/08/15 14:09, Matt Walker wrote:
> Dear coreutils Development Team,
>
> I recently ran into a problem when using the base64 program to decode strings
> received from the GMail API. Here is a relevant Stack Overflow post:
>
>
