On Tue, Mar 15, 2016 at 11:18:47AM +0100, Ionel Mugurel Ciobîcă wrote:
> On 14-03-2016, at 17h 30'55", Jon LaBadie wrote about "decoding UTF-8"
> > I frequently find headers (mostly Subject, but also From/To)
> > that I assume are some representation form f
On Tue, Mar 15, 2016 at 01:23:37PM +0100, Gabriel Philippe wrote:
>
> Quite funny, I spent some time on it yesterday...
>
> This is rfc2047 encoding [1]. It can probably use other charsets (not
> only UTF-8).
>
> The best way I found is to pipe it through perl -MEncode -ne 'print
>
On Mon, Mar 14, 2016 at 10:30 PM, Jon LaBadie wrote:
> I frequently find headers (mostly Subject, but also From/To)
> that I assume are some representation form for a UTF-8 encoded
> string as they start with "=?UTF-8?" and end with "=?= ".
> For example:
>
> To:
can encode and decode this
with base64:
# echo "something" | base64
# c29tZXRoaW5nCg==
#echo "Z3VuZGk=" | base64 -d
gundi
Ionel
On 14-03-2016, at 17h 30'55", Jon LaBadie wrote about "decoding UTF-8"
> I frequently find headers (mostly Subject, but
On 2016-03-14 at 17:30, Jon LaBadie wrote:
> Is my assumption correct? What is the representation called? Is there a
> tool to regain the original string? I believe my video system can display
> the larger character set.
You are correct, it's just the UTF-8 encoding. There is a recent thread
I frequently find headers (mostly Subject, but also From/To)
that I assume are some representation form for a UTF-8 encoded
string as they start with "=?UTF-8?" and end with "=?= ".
For example:
To: =?UTF-8?B?Z3VuZGk=?=
Is my assumption correct? What is the representation