Something else I've noticed. According to perlfunc, if you try to re-open STDOUT or STDERR as an "in memory" file, you have to close it first, implying that if you want to re-open it to as a file, you DON'T need to close it first.

However, if you don't close it first, then the ':utf8' layer won't be applied:

#!/usr/bin/perl use strict; use warnings; my $utf8="\xe9"; open STDOUT, ">>:utf8", 'test.txt' or die $!; print "No close: ",$utf8,"\n"; close STDOUT; open STDOUT, ">>:utf8", 'test.txt' or die $!; print "Close: ",$utf8,"\n"; PRINTS: No close: \xe9 (not literally - prints character \xe9, not UTF- +8 encoded) Close: é

Clint

Update: Filed as bug 44703


In reply to Re: Redirecting STDERR to STDOUT with UTF8 layer by clinton
in thread Redirecting STDERR to STDOUT with UTF8 layer by clinton

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.