Beefy Boxes and Bandwidth Generously Provided by pair Networks
Clear questions and runnable code
get the best and fastest answer

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??


You want domain_to_unicode from Net::IDN::Encode, I believe.

use utf8;
use open ':std', ':encoding(UTF-8)';
use URI;
use Net::IDN::Encode 'domain_to_unicode';
use strict;
use warnings;

my $href="https://マリウス.com/";
print $href,"\n";

my $uri = URI->new($href);

my $punycode = $uri->host;

print ":",$punycode,"\n";

my $domain = domain_to_unicode($punycode);

print $domain, "\n";



Hope this helps!

Edit: ++haukex posted while I was composing my reply

The way forward always starts with a minimal test.

In reply to Re: CPAN's versus Japanese as Unicode? by 1nickt
in thread CPAN's versus Japanese as Unicode? by mldvx4

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

  • 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.
Log In?

What's my password?
Create A New User
Domain Nodelet?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others scrutinizing the Monastery: (2)
As of 2024-04-17 04:00 GMT
Find Nodes?
    Voting Booth?

    No recent polls found