I'm having trouble passing non-ANSI data from a Perl script to the dBpoweramp Music Converter using its COM interface. Perl strings from a UTF-8 script end up expanded instead of UTF-16 encoded (e.g. \xc3 \xbc from the script appears in an MP3 tag as \xc3 \x00 \xbc \x00 instead of x\fc \x00.) Can someone please suggest how I can test this further to see whether the problem is in Win32::OLE? Are there any standard COM objects other than Microsoft Excel that are commonly used for testing this module? Thanks.
use v5.16;
use strict;
use warnings;
use utf8;
use Win32::OLE ();
my $filename = shift or die "No file specified\n";
my $dmcconverter = Win32::OLE->new('dMCScripting.Converter')
or die "Can't create dMCScripting.Converter object: $!\n";
$dmcconverter->WriteIDTag( $filename, 'artist', 'The Crüxshadows' );
UPDATE: I have verified that VB Script can read UTF-8 data from a file and set the ID tag correctly, so I believe the problem is in Win32::OLE. If someone can tell me how I might work around this problem (e.g. with Win32::OLE::Variant) I would be grateful. Thanks.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|