summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
author B. Watson2016-11-06 22:57:59 +0100
committer Willy Sudiarto Raharjo2016-11-12 00:58:01 +0100
commit07a53ebdb5fd09075c876ce76adac3ee8542e11c (patch)
tree9234c781207a31e237d202ebb2fafb3e093f8029
parenteeaf70d56ef75707c746b10c57d9d21cac80cb6c (diff)
downloadslackbuilds-07a53ebdb5fd09075c876ce76adac3ee8542e11c.tar.gz
perl/perl-Net-LibIDN: Update README.
-rw-r--r--perl/perl-Net-LibIDN/README17
1 files changed, 9 insertions, 8 deletions
diff --git a/perl/perl-Net-LibIDN/README b/perl/perl-Net-LibIDN/README
index e495139df4..b437dffdf5 100644
--- a/perl/perl-Net-LibIDN/README
+++ b/perl/perl-Net-LibIDN/README
@@ -1,14 +1,15 @@
Net::LibIDN - Perl bindings for GNU Libidn
-Provides bindings for GNU Libidn, a C library for handling Internationalized
-Domain Names according to IDNA (RFC 3490), in a way very much inspired by
-Turbo Fredriksson's PHP-IDN.
-There is currently no support for Perl's unicode capabilities (man
-perlunicode). All input strings are assumed to be octet strings, all output
-strings are generated as octet strings. Thus, if you require Perl's unicode
-features, you will have to convert your strings manually. For example:
+Provides bindings for GNU Libidn, a C library for handling
+Internationalized Domain Names according to IDNA (RFC 3490), in a way
+very much inspired by Turbo Fredriksson's PHP-IDN. There is currently
+no support for Perl's unicode capabilities (man perlunicode). All input
+strings are assumed to be octet strings, all output strings are generated
+as octet strings. Thus, if you require Perl's unicode features, you will
+have to convert your strings manually. For example:
use Encode;
use Data::Dumper;
print Dumper(Net::LibIDN::idn_to_unicode('xn--uro-j50a.com', 'utf-8'));
- print Dumper(decode('utf-8', Net::LibIDN::idn_to_unicode('xn--uro-j50a.com', 'utf-8')));
+ print Dumper(decode(
+ 'utf-8', Net::LibIDN::idn_to_unicode('xn--uro-j50a.com', 'utf-8')));