heh, I bet I wrote that code. One thing I learned since then is that :raw:encoding(...) disables buffering. You want :raw:perlio:encoding(...).

You probably want to specify UTF-16le instead of UTF-16 since you probably want UTF-16le and not UTF-16be.

The snippet is already producing a copy, so all you need to do to make it move is to delete the source once the copy is created. 

#!/usr/bin/perl
use strict;
use warnings;

my ($src_qfn, $dst_qfn) = @ARGV;

open(my $src_fh, "<:raw:perlio:encoding(UTF-8)", $src_qfn)
   or die("Can't open \"$src_qfn\": $!\n");

open(my $dst_fh, ">:raw:perlio:encoding(UTF-16le)", $dst_qfn)
   or die("Can't open \"$src_qfn\": $!\n");

print $dst_fh $_ while <$src_fh>;

unlink($src_fh);

[download]

In reply to Re: encode files to utf-16 and then move by ikegami
in thread encode files to utf-16 and then move by tannx

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.