Manual Pages for UNIX Darwin command on man Encode
MyWebUniversity

Manual Pages for UNIX Darwin command on man Encode

Encode(3pm) Perl Programmers Reference Guide Encode(3pm)

NAME

Encode - character encodings

SYNOPSIS

use Encode;

TTaabbllee ooff CCoonntteennttss

Encode consists of a collection of modules whose details are too big to

fit in one document. This POD itself explains the top-level APIs and

general topics at a glance. For other topics and more details, see the PODs below: Name Description

----------------------------

Encode::Alias Alias definitions to encodings

Encode::Encoding Encode Implementation Base Class

Encode::Supported List of Supported Encodings

Encode::CN Simplified Chinese Encodings

Encode::JP Japanese Encodings

Encode::KR Korean Encodings

Encode::TW Traditional Chinese Encodings

----------------------------

DESCRIPTION

The "Encode" module provides the interfaces between Perl's strings and

the rest of the system. Perl strings are sequences of cchhaarraacctteerrss. The repertoire of characters that Perl can represent is at least that defined by the Unicode Consortium. On most platforms the ordinal values of the characters (as returned by "ord(ch)") is the "Unicode codepoint" for the character (the exceptions are those platforms where the legacy

encoding is some variant of EBCDIC rather than a super-set of ASCII -

see perlebcdic).

Traditionally, computer data has been moved around in 8-bit chunks

often called "bytes". These chunks are also known as "octets" in net-

working standards. Perl is widely used to manipulate data of many types

- not only strings of characters representing human or computer lan-

guages but also "binary" data being the machine's representation of

numbers, pixels in an image - or just about anything.

When Perl is processing "binary data", the programmer wants Perl to

process "sequences of bytes". This is not a problem for Perl - as a

byte has 256 possible values, it easily fits in Perl's much larger "logical character". TTEERRMMIINNOOLLOOGGYY

+o character: a character in the range 0..(2**32-1) (or more). (What

Perl's strings are made of.)

+o byte: a character in the range 0..255 (A special case of a Perl char-

acter.) +o octet: 8 bits of data, with ordinal values 0..255 (Term for bytes

passed to or from a non-Perl context, e.g. a disk file.)

PPEERRLL EENNCCOODDIINNGG AAPPII

$octets = encode(ENCODING, $string [, CHECK])

Encodes a string from Perl's internal form into ENCODING and returns

a sequence of octets. ENCODING can be either a canonical name or an alias. For encoding names and aliases, see "Defining Aliases". For CHECK, see "Handling Malformed Data". For example, to convert a string from Perl's internal format to

iso-8859-1 (also known as Latin1),

$octets = encode("iso-8859-1", $string);

CCAAVVEEAATT: When you run "$octets = encode("utf8", $string)", then

$octets mmaayy nnoott bbee eeqquuaall ttoo $string. Though they both contain the

same data, the utf8 flag for $octets is aallwwaayyss off. When you encode

anything, utf8 flag of the result is always off, even when it con-

tains completely valid utf8 string. See "The UTF-8 flag" below.

If the $string is "undef" then "undef" is returned.

$string = decode(ENCODING, $octets [, CHECK])

Decodes a sequence of octets assumed to be in ENCODING into Perl's internal form and returns the resulting string. As in encode(), ENCODING can be either a canonical name or an alias. For encoding names and aliases, see "Defining Aliases". For CHECK, see "Handling Malformed Data".

For example, to convert ISO-8859-1 data to a string in Perl's inter-

nal format:

$string = decode("iso-8859-1", $octets);

CCAAVVEEAATT: When you run "$string = decode("utf8", $octets)", then

$string mmaayy nnoott bbee eeqquuaall ttoo $octets. Though they both contain the

same data, the utf8 flag for $string is on unless $octets entirely

consists of ASCII data (or EBCDIC on EBCDIC machines). See "The

UTF-8 flag" below.

If the $string is "undef" then "undef" is returned.

[$length =] fromto($octets, FROMENC, TOENC [, CHECK])

Converts iinn-ppllaaccee data between two encodings. The data in $octets

must be encoded as octets and not as characters in Perl's internal

format. For example, to convert ISO-8859-1 data to Microsoft's CP1250

encoding:

fromto($octets, "iso-8859-1", "cp1250");

and to convert it back:

fromto($octets, "cp1250", "iso-8859-1");

Note that because the conversion happens in place, the data to be converted cannot be a string constant; it must be a scalar variable. fromto() returns the length of the converted string in octets on success, undef on error. CCAAVVEEAATT: The following operations look the same but are not quite so;

fromto($data, "iso-8859-1", "utf8"); #1

$data = decode("iso-8859-1", $data); #2

Both #1 and #2 make $data consist of a completely valid UTF-8 string

but only #2 turns utf8 flag on. #1 is equivalent to

$data = encode("utf8", decode("iso-8859-1", $data));

See "The UTF-8 flag" below.

$octets = encodeutf8($string);

Equivalent to "$octets = encode("utf8", $string);" The characters

that comprise $string are encoded in Perl's internal format and the

result is returned as a sequence of octets. All possible characters

have a UTF-8 representation so this function cannot fail.

$string = decodeutf8($octets [, CHECK]);

equivalent to "$string = decode("utf8", $octets [, CHECK])". The

sequence of octets represented by $octets is decoded from UTF-8 into

a sequence of logical characters. Not all sequences of octets form

valid UTF-8 encodings, so it is possible for this call to fail. For

CHECK, see "Handling Malformed Data". LLiissttiinngg aavvaaiillaabbllee eennccooddiinnggss

use Encode;

@list = Encode->encodings();

Returns a list of the canonical names of the available encodings that are loaded. To get a list of all available encodings including the ones that are not loaded yet, say

@allencodings = Encode->encodings(":all");

Or you can give the name of a specific module.

@withjp = Encode->encodings("Encode::JP");

When "::" is not in the name, "Encode::" is assumed.

@ebcdic = Encode->encodings("EBCDIC");

To find out in detail which encodings are supported by this package,

see Encode::Supported.

DDeeffiinniinngg AAlliiaasseess To add a new alias to a given encoding, use:

use Encode;

use Encode::Alias;

definealias(newName => ENCODING); After that, newName can be used as an alias for ENCODING. ENCODING may be either the name of an encoding or an encoding object But before you do so, make sure the alias is nonexistent with "resolvealias()", which returns the canonical name thereof. i.e.

Encode::resolvealias("latin1") eq "iso-8859-1" # true

Encode::resolvealias("iso-8859-12") # false; nonexistent

Encode::resolvealias($name) eq $name # true if $name is canonical

resolvealias() does not need "use Encode::Alias"; it can be exported

via "use Encode qw(resolvealias)".

See Encode::Alias for details.

EEnnccooddiinngg vviiaa PPeerrllIIOO

If your perl supports PerlIO (which is the default), you can use a Per-

lIO layer to decode and encode directly via a filehandle. The follow-

ing two examples are totally identical in their functionality.

# via PerlIO

open my $in, "<:encoding(shiftjis)", $infile or die;

open my $out, ">:encoding(euc-jp)", $outfile or die;

while(<$in>){ print $out $; }

# via fromto

open my $in, "<", $infile or die;

open my $out, ">", $outfile or die;

while(<$in>){

fromto($, "shiftjis", "euc-jp", 1);

print $out $;

}

Unfortunately, it may be that encodings are PerlIO-savvy. You can

check if your encoding is supported by PerlIO by calling the "per-

liook" method.

Encode::perliook("hz"); # False

findencoding("euc-cn")->perliook; # True where PerlIO is available

use Encode qw(perliook); # exported upon request

perliook("euc-jp")

Fortunately, all encodings that come with Encode core are PerlIO-savvy

except for hz and ISO-2022-kr. For gory details, see Encode::Encoding

and Encode::PerlIO.

HHaannddlliinngg MMaallffoorrmmeedd DDaattaa

The optional CHECK argument tells Encode what to do when it encounters

malformed data. Without CHECK, Encode::FBDEFAULT ( == 0 ) is assumed.

As of version 2.12 Encode supports coderef values for CHECK. See

below. NNOOTTEE:: Not all encoding support this feature

Some encodings ignore CHECK argument. For example, Encode::Unicode

ignores CHECK and it always croaks on error. Now here is the list of CHECK values available

CHECK = Encode::FBDEFAULT ( == 0)

If CHECK is 0, (en|de)code will put a substitution character in place of a malformed character. When you encode, will be used.

When you decode the code point 0xFFFD is used. If the data is sup-

posed to be UTF-8, an optional lexical warning (category utf8) is

given.

CHECK = Encode::FBCROAK ( == 1)

If CHECK is 1, methods will die on error immediately with an error message. Therefore, when CHECK is set to 1, you should trap the error with eval{} unless you really want to let it die.

CHECK = Encode::FBQUIET

If CHECK is set to Encode::FBQUIET, (en|de)code will immediately

return the portion of the data that has been processed so far when an error occurs. The data argument will be overwritten with everything after that point (that is, the unprocessed part of data). This is handy when you have to call decode repeatedly in the case where your

source data may contain partial multi-byte character sequences, (i.e.

you are reading with a fixed-width buffer). Here is a sample code

that does exactly this:

my $buffer = ''; my $string = '';

while(read $fh, $buffer, 256, length($buffer)){

$string .= decode($encoding, $buffer, Encode::FBQUIET);

# $buffer now contains the unprocessed partial character

}

CHECK = Encode::FBWARN

This is the same as above, except that it warns on error. Handy when you are debugging the mode above.

perlqq mode (CHECK = Encode::FBPERLQQ)

HTML charref mode (CHECK = Encode::FBHTMLCREF)

XML charref mode (CHECK = Encode::FBXMLCREF)

For encodings that are implemented by Encode::XS, CHECK ==

Encode::FBPERLQQ turns (en|de)code into "perlqq" fallback mode.

When you decode, "\xHH" will be inserted for a malformed character, where HH is the hex representation of the octet that could not be decoded to utf8. And when you encode, "\x{HHHH}" will be inserted, where HHHH is the Unicode ID of the character that cannot be found in the character repertoire of the encoding. HTML/XML character reference modes are about the same, in place of

"\x{HHHH}", HTML uses "&#NNN;" where NNN is a decimal number and XML

uses "&#xHHHH;" where HHHH is the hexadecimal number.

In Encode 2.10 or later, "LEAVESRC" is also implied.

The bitmask These modes are actually set via a bitmask. Here is how the FBXX constants are laid out. You can import the FBXX constants via "use

Encode qw(:fallbacks)"; you can import the generic bitmask constants

via "use Encode qw(:fallbackall)".

FBDEFAULT FBCROAK FBQUIET FBWARN FBPERLQQ DIEONERR 0x0001 X WARNONERR 0x0002 X RETURNONERR 0x0004 X X LEAVESRC 0x0008 X PERLQQ 0x0100 X HTMLCREF 0x0200 XMLCREF 0x0400 ccooddeerreeff ffoorr CCHHEECCKK

As of Encode 2.12 CHECK can also be a code reference which takes the

ord value of unmapped caharacter as an argument and returns a string that represents the fallback character. For instance,

$ascii = encode("ascii", $utf8, sub{ sprintf "", shift });

Acts like FBPERLQQ but is used instead of \x{XXXX}. DDeeffiinniinngg EEnnccooddiinnggss To define a new encoding, use:

use Encode qw(defineencoding);

defineencoding($object, 'canonicalName' [, alias...]);

canonicalName will be associated with $object. The object should pro-

vide the interface described in Encode::Encoding. If more than two

arguments are provided then additional arguments are taken as aliases

for $object.

See Encode::Encoding for more details.

The UTF8 flag Before the introduction of utf8 support in perl, The "eq" operator just compared the strings represented by two scalars. Beginning with perl 5.8, "eq" compares two strings with simultaneous consideration of the

utf8 flag. To explain why we made it so, I will quote page 402 of "Pro-

gramming Perl, 3rd ed."

Goal #1:

Old byte-oriented programs should not spontaneously break on the old

byte-oriented data they used to work on.

Goal #2:

Old byte-oriented programs should magically start working on the new

character-oriented data when appropriate.

Goal #3:

Programs should run just as fast in the new character-oriented mode

as in the old byte-oriented mode.

Goal #4:

Perl should remain one language, rather than forking into a byte-ori-

ented Perl and a character-oriented Perl.

Back when "Programming Perl, 3rd ed." was written, not even Perl 5.6.0

was born and many features documented in the book remained unimple-

mented for a long time. Perl 5.8 corrected this and the introduction

of the UTF-8 flag is one of them. You can think of this perl notion as

of a byte-oriented mode (utf8 flag off) and a character-oriented mode

(utf8 flag on).

Here is how Encode takes care of the utf8 flag.

+o When you encode, the resulting utf8 flag is always off.

+o When you decode, the resulting utf8 flag is on unless you can unam-

biguously represent data. Here is the definition of dis-ambiguity.

After "$utf8 = decode('foo', $octet);",

When $octet is... The utf8 flag in $utf8 is

-----------------------

In ASCII only (or EBCDIC only) OFF

In ISO-8859-1 ON

In any other Encoding ON

-----------------------

As you see, there is one exception, In ASCII. That way you can

assume Goal #1. And with Encode Goal #2 is assumed but you still

have to be careful in such cases mentioned in CCAAVVEEAATT paragraphs. This utf8 flag is not visible in perl scripts, exactly for the same reason you cannot (or you don't have to) see if a scalar contains a string, integer, or floating point number. But you can still peek and poke these if you will. See the section below. MMeessssiinngg wwiitthh PPeerrll''ss IInntteerrnnaallss

The following API uses parts of Perl's internals in the current imple-

mentation. As such, they are efficient but may change. isutf8(STRING [, CHECK])

[INTERNAL] Tests whether the UTF-8 flag is turned on in the STRING.

If CHECK is true, also checks the data in STRING for being well-

formed UTF-8. Returns true if successful, false otherwise.

As of perl 5.8.1, utf8 also has utf8::isutf8(). utf8on(STRING)

[INTERNAL] Turns on the UTF-8 flag in STRING. The data in STRING is

nnoott checked for being well-formed UTF-8. Do not use unless you kknnooww

that the STRING is well-formed UTF-8. Returns the previous state of

the UTF-8 flag (so please don't treat the return value as indicating

success or failure), or "undef" if STRING is not a string. utf8off(STRING)

[INTERNAL] Turns off the UTF-8 flag in STRING. Do not use

frivolously. Returns the previous state of the UTF-8 flag (so please

don't treat the return value as indicating success or failure), or "undef" if STRING is not a string.

UUTTFF-88 vvss.. uuttff88

....We now view strings not as sequences of bytes, but as sequences

of numbers in the range 0 .. 2**32-1 (or in the case of 64-bit

computers, 0 .. 2**64-1) - Programming Perl, 3rd ed.

That has been the perl's notion of UTF-8 but official UTF-8 is more

strict; Its ranges is much narrower (0 .. 10FFFF), some sequences are not allowed (i.e. Those used in the surrogate pair, 0xFFFE, et al). Now that is overruled by Larry Wall himself. From: Larry Wall Date: December 04, 2004 11:51:58 JST

To: perl-unicode@perl.org

Subject: Re: Make Encode.pm support the real UTF-8

Message-Id: <20041204025158.GA28754@wall.org>

On Fri, Dec 03, 2004 at 10:12:12PM +0000, Tim Bunce wrote: : I've no problem with 'utf8' being perl's unrestricted uft8 encoding,

: but "UTF-8" is the name of the standard and should give the

: corresponding behaviour. For what it's worth, that's how I've always kept them straight in my head. Also for what it's worth, Perl 6 will mostly default to strict but make it easy to switch back to lax. Larry

Do you copy? As of Perl 5.8.7, UUTTFF-88 means strict, official UTF-8

while uuttff88 means liberal, lax, version thereof. And Encode version

2.10 or later thus groks the difference between "UTF-8" and C"utf8".

encode("utf8", "\x{FFFFFFFF}", 1); # okay

encode("UTF-8", "\x{FFFFFFFF}", 1); # croaks

"UTF-8" in Encode is actually a canonical name for "utf-8-strict".

Yes, the hyphen between "UTF" and "8" is important. Without it Encode

goes "liberal"

findencoding("UTF-8")->name # is 'utf-8-strict'

findencoding("utf-8")->name # ditto. names are case insensitive

findencoding("utf8")->name # ditto. "" are treated as "-"

findencoding("UTF8")->name # is 'utf8'.

SEE ALSO

Encode::Encoding, Encode::Supported, Encode::PerlIO, encoding, per-

lebcdic, "open" in perlfunc, perlunicode, utf8, the Perl Unicode Mail-

ing List

MMAAIINNTTAAIINNEERR

This project was originated by Nick Ing-Simmons and later maintained by

Dan Kogai . See AUTHORS for a full list of people

involved. For any questions, use so we can all

share.

perl v5.8.8 2001-09-21 Encode(3pm)




Contact us      |      About us      |      Term of use      |       Copyright © 2000-2019 MyWebUniversity.com ™