The following code produces the original utf-8 string after converting to base64.

But it seems overly complicated. What am I missing ?

Additionally: I can probably understand that I need to do encode_utf8 step, but why do I need to set the utf8 flag manually after explicitly encoding to utf8? 

use strict;
use warnings;
use utf8 ;

use Encode;
use Data::Dump qw/dd pp/;
use Devel::Peek;
use MIME::Base64 ;

my $str ='Ä';

warn "\n*** orig str='$str'";
Dump $str;


our $encoded = MIME::Base64::encode_base64($str);
warn "\n*** encode_b64 encoded='$encoded'";
Dump $encoded;


warn "\n*** decode_b64";
our $decoded = MIME::Base64::decode_base64($encoded);
Dump $decoded;

warn "\n*** encode_utf8";
$decoded = Encode::encode_utf8($decoded);
Dump $decoded;

warn "\n*** _utf8_on";
Encode::_utf8_on($decoded);
Dump $decoded;

[download]

*** orig str='Ä' at c:/tmp/b64_utf8.pl line 12.
SV = PV(0x54c9d8) at 0x5a8b00
  REFCNT = 1
  FLAGS = (PADMY,POK,pPOK,UTF8)
  PV = 0x5471d8 "\303\204"\0 [UTF8 "\x{c4}"]
  CUR = 2
  LEN = 16

*** encode_b64 encoded='xA==
' at c:/tmp/b64_utf8.pl line 17.
SV = PV(0x54caa8) at 0x26dbcb8
  REFCNT = 1
  FLAGS = (POK,pPOK)
  PV = 0x547478 "xA==\n"\0
  CUR = 5
  LEN = 16

*** decode_b64 at c:/tmp/b64_utf8.pl line 21.
SV = PV(0x54cb08) at 0x26da130
  REFCNT = 1
  FLAGS = (POK,pPOK)
  PV = 0x28d2b98 "\304"\0
  CUR = 1
  LEN = 16

*** encode_utf8 at c:/tmp/b64_utf8.pl line 25.
SV = PV(0x54cb08) at 0x26da130
  REFCNT = 1
  FLAGS = (POK,pPOK)
  PV = 0x28d2c28 "\303\204"\0
  CUR = 2
  LEN = 16

*** _utf8_on at c:/tmp/b64_utf8.pl line 29.
SV = PV(0x54cb08) at 0x26da130
  REFCNT = 1
  FLAGS = (POK,pPOK,UTF8)
  PV = 0x28d2c28 "\303\204"\0 [UTF8 "\x{c4}"]
  CUR = 2
  LEN = 16

[download]

Cheers Rolf
(addicted to the Perl Programming Language and ☆☆☆☆ :)
Je suis Charlie!

In reply to Converting utf-8 to base64 and back by LanX

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.