Bruno Haible writes:
> Jim Meyering wrote:
>> > Could also be done, but since the code to remove newlines was there, I
>> > thought it is simpler to augment it to remove common garbage.
>>
>> I am reluctant to make this low-level decoding function ignore anything
>> else.
>
> I agree. If you re
Jim Meyering wrote:
> > Could also be done, but since the code to remove newlines was there, I
> > thought it is simpler to augment it to remove common garbage.
>
> I am reluctant to make this low-level decoding function ignore anything
> else.
I agree. If you remove the garbage unconditionally,
Nikos Mavrogiannopoulos wrote:
> On 01/30/2012 10:29 PM, Jim Meyering wrote:
>
>> Hi Nikos,
>> Have you considered pre-filtering the data you pass to the base64-decoding
>> function? We considered what you're proposing when adding the
>> --ignore-garbage option to the command-line base64 program:
On 01/30/2012 10:29 PM, Jim Meyering wrote:
> Hi Nikos,
> Have you considered pre-filtering the data you pass to the base64-decoding
> function? We considered what you're proposing when adding the
> --ignore-garbage option to the command-line base64 program:
Hello,
Could also be done, but sin
Nikos Mavrogiannopoulos wrote:
> This patch makes the base64 decoding tolerant on carriage returns,
> spaces and tabs. It is quite common to find PEM encoded files (base64
> with new lines) containing such characters and having a tolerant decoder
> is a plus.
Hi Nikos,
Have you considered pre-fi
Hello,
This patch makes the base64 decoding tolerant on carriage returns,
spaces and tabs. It is quite common to find PEM encoded files (base64
with new lines) containing such characters and having a tolerant decoder
is a plus.
regards,
Nikos
>From c56e7ecd745c7e49bbf17bd907c7d305009b19d9 Mon Sep
