<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<title>Summaries of supported encodings</title>
</head>
<body><div class="manualnavbar" style="text-align: center;">
<div class="prev" style="text-align: left; float: left;"><a href="mbstring.constants.html">Predefined Constants</a></div>
<div class="next" style="text-align: right; float: right;"><a href="mbstring.ja-basic.html">Basics of Japanese multi-byte encodings</a></div>
<div class="up"><a href="book.mbstring.html">Multibyte String</a></div>
<div class="home"><a href="index.html">PHP Manual</a></div>
</div><hr /><div id="mbstring.encodings" class="chapter">
<h1>Summaries of supported encodings</h1>
<table class="segmentedlist">
<caption><strong>Summaries of supported encodings</strong></caption>
<thead><tr><th>Name in the IANA character set registry</th>
<th>Underlying character set</th>
<th>Description</th>
<th>Additional note</th>
</tr></thead><tbody><tr class="seglistitem">
<td class="seg">ISO-10646-UCS-4</td>
<td class="seg">ISO 10646</td>
<td class="seg">
The Universal Character Set with 31-bit code space, standardized as UCS-4
by ISO/IEC 10646. It is kept synchronized with the latest version of the
Unicode code map.
</td>
<td class="seg">
If this name is used in the encoding conversion facility,
the converter attempts to identify by the preceding BOM
(byte order mark)in which endian the subsequent bytes
are represented.
</td>
</tr>
<tr class="seglistitem">
<td class="seg">ISO-10646-UCS-4</td>
<td class="seg">UCS-4</td>
<td class="seg">
See above.
</td>
<td class="seg">
In contrast to <em>UCS-4</em>, strings are always assumed
to be in big endian form.
</td>
</tr>
<tr class="seglistitem">
<td class="seg">ISO-10646-UCS-4</td>
<td class="seg">UCS-4</td>
<td class="seg">
See above.
</td>
<td class="seg">
In contrast to <em>UCS-4</em>, strings are always assumed
to be in little endian form.
</td>
</tr>
<tr class="seglistitem">
<td class="seg">ISO-10646-UCS-2</td>
<td class="seg">UCS-2</td>
<td class="seg">
The Universal Character Set with 16-bit code space, standardized as UCS-2
by ISO/IEC 10646. It is kept synchronized with the latest version of the
unicode code map.
</td>
<td class="seg">
If this name is used in the encoding conversion facility,
the converter attempts to identify by the preceding BOM
(byte order mark)in which endian the subsequent bytes
are represented.
</td>
</tr>
<tr class="seglistitem">
<td class="seg">ISO-10646-UCS-2</td>
<td class="seg">UCS-2</td>
<td class="seg">
See above.
</td>
<td class="seg">
In contrast to <em>UCS-2</em>, strings are always assumed
to be in big endian form.
</td>
</tr>
<tr class="seglistitem">
<td class="seg">ISO-10646-UCS-2</td>
<td class="seg">UCS-2</td>
<td class="seg">
See above.
</td>
<td class="seg">
In contrast to <em>UCS-2</em>, strings are always assumed
to be in little endian form.
</td>
</tr>
<tr class="seglistitem">
<td class="seg">UTF-32</td>
<td class="seg">Unicode</td>
<td class="seg">
Unicode Transformation Format of 32-bit unit width, whose encoding space
refers to the Unicode's codeset standard. This encoding scheme wasn't
identical to UCS-4 because the code space of Unicode were limited to
a 21-bit value.
</td>
<td class="seg">
If this name is used in the encoding conversion facility,
the converter attempts to identify by the preceding BOM
(byte order mark)in which endian the subsequent bytes
are represented.
</td>
</tr>
<tr class="seglistitem">
<td class="seg">UTF-32BE</td>
<td class="seg">Unicode</td>
<td class="seg">See above</td>
<td class="seg">
In contrast to <em>UTF-32</em>, strings are always assumed
to be in big endian form.
</td>
</tr>
<tr class="seglistitem">
<td class="seg">UTF-32LE</td>
<td class="seg">Unicode</td>
<td class="seg">See above</td>
<td class="seg">
In contrast to <em>UTF-32</em>, strings are always assumed
to be in little endian form.
</td>
</tr>
<tr class="seglistitem">
<td class="seg">UTF-16</td>
<td class="seg">Unicode</td>
<td class="seg">
Unicode Transformation Format of 16-bit unit width. It's worth a note
that UTF-16 is no longer the same specification as UCS-2 because the
surrogate mechanism has been introduced since Unicode 2.0 and
UTF-16 now refers to a 21-bit code space.
</td>
<td class="seg">
If this name is used in the encoding conversion facility,
the converter attempts to identify by the preceding BOM
(byte order mark)in which endian the subsequent bytes
are represented.
</td>
</tr>
<tr class="seglistitem">
<td class="seg">UTF-16BE</td>
<td class="seg">Unicode</td>
<td class="seg">
See above.
</td>
<td class="seg">
In contrast to <em>UTF-16</em>, strings are always assumed
to be in big endian form.
</td>
</tr>
<tr class="seglistitem">
<td class="seg">UTF-16LE</td>
<td class="seg">Unicode</td>
<td class="seg">
See above.
</td>
<td class="seg">
In contrast to <em>UTF-16</em>, strings are always assumed
to be in little endian form.
</td>
</tr>
<tr class="seglistitem">
<td class="seg">UTF-8</td>
<td class="seg">Unicode / UCS</td>
<td class="seg">
Unicode Transformation Format of 8-bit unit width.
</td>
<td class="seg">none</td>
</tr>
<tr class="seglistitem">
<td class="seg">UTF-7</td>
<td class="seg">Unicode</td>
<td class="seg">
A mail-safe transformation format of Unicode, specified in
<a href="http://www.faqs.org/rfcs/rfc2152" class="link external">» RFC2152</a>.
</td>
<td class="seg">none</td>
</tr>
<tr class="seglistitem">
<td class="seg">(none)</td>
<td class="seg">Unicode</td>
<td class="seg">
A variant of UTF-7 which is specialized for use in the
<a href="http://www.faqs.org/rfcs/rfc3501" class="link external">» IMAP protocol</a>.
</td>
<td class="seg">none</td>
</tr>
<tr class="seglistitem">
<td class="seg">
US-ASCII (preferred MIME name) / iso-ir-6 / ANSI_X3.4-1986 /
ISO_646.irv:1991 / ASCII / ISO646-US / us / IBM367 / CP367 / csASCII
</td>
<td class="seg">ASCII / ISO 646</td>
<td class="seg">
American Standard Code for Information Interchange is a commonly-used
7-bit encoding. Also standardized as an international standard, ISO 646.
</td>
<td class="seg">(none)</td>
</tr>
<tr class="seglistitem">
<td class="seg">
EUC-JP (preferred MIME name) /
Extended_UNIX_Code_Packed_Format_for_Japanese / csEUCPkdFmtJapanese
</td>
<td class="seg">
Compound of US-ASCII / JIS X0201:1997 (hankaku kana part) /
JIS X0208:1990 / JIS X0212:1990
</td>
<td class="seg">
As you see the name is derived from an abbreviation of Extended UNIX Code
Packed Format for Japanese, this encoding is mostly used on UNIX or
alike platforms. The original encoding scheme, Extended UNIX Code, is
designed on the basis of ISO 2022.
</td>
<td class="seg">
The character set referred to by EUC-JP is different to IBM932 / CP932,
which are used by OS/2® and Microsoft® Windows®.
For information interchange with those platforms, use EUCJP-WIN instead.
</td>
</tr>
<tr class="seglistitem">
<td class="seg">Shift_JIS (preferred MIME name) / MS_Kanji / csShift_JIS</td>
<td class="seg">Compound of JIS X0201:1997 / JIS X0208:1997</td>
<td class="seg">
Shift_JIS was developed in early 80's, at the time personal Japanese word
processors were brought into the market, in order to maintain
compatiblities with the legacy encoding scheme JIS X 0201:1976.
According to the IANA definition the codeset of Shift_JIS is slightly
different to IBM932 / CP932. However, the names "SJIS" / "Shift_JIS" are
often wrongly used to refer to these codesets.
</td>
<td class="seg">For the CP932 codemap, use SJIS-WIN instead.</td>
</tr>
<tr class="seglistitem">
<td class="seg">(none)</td>
<td class="seg">
Compound of JIS X0201:1997 / JIS X0208:1997 / IBM extensions / NEC extensions
</td>
<td class="seg">
While this "encoding" uses the same encoding scheme as EUC-JP,
the underlying character set is different. That is, some code points map
to different characters than EUC-JP.
</td>
<td class="seg">none</td>
</tr>
<tr class="seglistitem">
<td class="seg">Windows-31J / csWindows31J</td>
<td class="seg">
Compound of JIS X0201:1997 / JIS X0208:1997 / IBM extensions / NEC extensions
</td>
<td class="seg">
While this "encoding" uses the same encoding scheme as
Shift_JIS, the underlying character set is different. That means some code
points map to different characters than Shift_JIS.
</td>
<td class="seg">(none)</td>
</tr>
<tr class="seglistitem">
<td class="seg">ISO-2022-JP (preferred MIME name) / csISO2022JP</td>
<td class="seg">
US-ASCII / JIS X0201:1976 / JIS X0208:1978 / JIS X0208:1983
</td>
<td class="seg"><a href="http://www.faqs.org/rfcs/rfc1468" class="link external">» RFC1468</a></td>
<td class="seg">(none)</td>
</tr>
<tr class="seglistitem">
<td class="seg">JIS</td>
<td class="seg">
<td class="seg">
<td class="seg">
</tr>
<tr class="seglistitem">
<td class="seg">ISO-8859-1</td>
<td class="seg">
<td class="seg">
<td class="seg">
</tr>
<tr class="seglistitem">
<td class="seg">ISO-8859-2</td>
<td class="seg">
<td class="seg">
<td class="seg">
</tr>
<tr class="seglistitem">
<td class="seg">ISO-8859-3</td>
<td class="seg">
<td class="seg">
<td class="seg">
</tr>
<tr class="seglistitem">
<td class="seg">ISO-8859-4</td>
<td class="seg">
<td class="seg">
<td class="seg">
</tr>
<tr class="seglistitem">
<td class="seg">ISO-8859-5</td>
<td class="seg">
<td class="seg">
<td class="seg">
</tr>
<tr class="seglistitem">
<td class="seg">ISO-8859-6</td>
<td class="seg">
<td class="seg">
<td class="seg">
</tr>
<tr class="seglistitem">
<td class="seg">ISO-8859-7</td>
<td class="seg">
<td class="seg">
<td class="seg">
</tr>
<tr class="seglistitem">
<td class="seg">ISO-8859-8</td>
<td class="seg">
<td class="seg">
<td class="seg">
</tr>
<tr class="seglistitem">
<td class="seg">ISO-8859-9</td>
<td class="seg">
<td class="seg">
<td class="seg">
</tr>
<tr class="seglistitem">
<td class="seg">ISO-8859-10</td>
<td class="seg">
<td class="seg">
<td class="seg">
</tr>
<tr class="seglistitem">
<td class="seg">ISO-8859-13</td>
<td class="seg">
<td class="seg">
<td class="seg">
</tr>
<tr class="seglistitem">
<td class="seg">ISO-8859-14</td>
<td class="seg">
<td class="seg">
<td class="seg">
</tr>
<tr class="seglistitem">
<td class="seg">ISO-8859-15</td>
<td class="seg">
<td class="seg">
<td class="seg">
</tr>
<tr class="seglistitem">
<td class="seg">ISO-8859-16</td>
<td class="seg">
<td class="seg">
<td class="seg">
</tr>
<tr class="seglistitem">
<td class="seg">byte2be</td>
<td class="seg">
<td class="seg">
<td class="seg">
</tr>
<tr class="seglistitem">
<td class="seg">byte2le</td>
<td class="seg">
<td class="seg">
<td class="seg">
</tr>
<tr class="seglistitem">
<td class="seg">byte4be</td>
<td class="seg">
<td class="seg">
<td class="seg">
</tr>
<tr class="seglistitem">
<td class="seg">byte4le</td>
<td class="seg">
<td class="seg">
<td class="seg">
</tr>
<tr class="seglistitem">
<td class="seg">BASE64</td>
<td class="seg">
<td class="seg">
<td class="seg">
</tr>
<tr class="seglistitem">
<td class="seg">HTML-ENTITIES</td>
<td class="seg">
<td class="seg">
<td class="seg">
</tr>
<tr class="seglistitem">
<td class="seg">7bit</td>
<td class="seg">
<td class="seg">
<td class="seg">
</tr>
<tr class="seglistitem">
<td class="seg">8bit</td>
<td class="seg">
<td class="seg">
<td class="seg">
</tr>
<tr class="seglistitem">
<td class="seg">EUC-CN</td>
<td class="seg">
<td class="seg">
<td class="seg">
</tr>
<tr class="seglistitem">
<td class="seg">CP936</td>
<td class="seg">
<td class="seg">
<td class="seg">
</tr>
<tr class="seglistitem">
<td class="seg">HZ</td>
<td class="seg">
<td class="seg">
<td class="seg">
</tr>
<tr class="seglistitem">
<td class="seg">EUC-TW</td>
<td class="seg">
<td class="seg">
<td class="seg">
</tr>
<tr class="seglistitem">
<td class="seg">CP950</td>
<td class="seg">
<td class="seg">
<td class="seg">
</tr>
<tr class="seglistitem">
<td class="seg">BIG-5</td>
<td class="seg">
<td class="seg">
<td class="seg">
</tr>
<tr class="seglistitem">
<td class="seg">EUC-KR</td>
<td class="seg">
<td class="seg">
<td class="seg">
</tr>
<tr class="seglistitem">
<td class="seg">UHC (CP949)</td>
<td class="seg">
<td class="seg">
<td class="seg">
</tr>
<tr class="seglistitem">
<td class="seg">ISO-2022-KR</td>
<td class="seg">
<td class="seg">
<td class="seg">
</tr>
<tr class="seglistitem">
<td class="seg">Windows-1251 (CP1251)</td>
<td class="seg">
<td class="seg">
<td class="seg">
</tr>
<tr class="seglistitem">
<td class="seg">Windows-1252 (CP1252)</td>
<td class="seg">
<td class="seg">
<td class="seg">
</tr>
<tr class="seglistitem">
<td class="seg">CP866 (IBM866)</td>
<td class="seg">
<td class="seg">
<td class="seg">
</tr>
<tr class="seglistitem">
<td class="seg">KOI8-R</td>
<td class="seg">
<td class="seg">
<td class="seg">
</tr>
<tr class="seglistitem">
<td class="seg">KOI8-U</td>
<td class="seg">
<td class="seg">
<td class="seg">
</tr>
</tbody></table>
</div>
<hr /><div class="manualnavbar" style="text-align: center;">
<div class="prev" style="text-align: left; float: left;"><a href="mbstring.constants.html">Predefined Constants</a></div>
<div class="next" style="text-align: right; float: right;"><a href="mbstring.ja-basic.html">Basics of Japanese multi-byte encodings</a></div>
<div class="up"><a href="book.mbstring.html">Multibyte String</a></div>
<div class="home"><a href="index.html">PHP Manual</a></div>
</div></body></html>
