{ "content": [ { "type": "text", "text": "# Encode::Supported (perldoc)\n\n## NAME\n\nEncode::Supported -- Encodings supported by Encode\n\n## Sections\n\n- **NAME**\n- **DESCRIPTION** (1 subsections)\n- **Supported Encodings** (4 subsections)\n- **Unsupported encodings**\n- **Encoding vs. Charset -- terminology**\n- **Encoding Classification (by Anton Tagunov and Dan Kogai)** (1 subsections)\n- **Glossary**\n- **References** (2 subsections)\n\nUse structuredContent.sections for detailed options, examples, and full documentation.\n" } ], "structuredContent": { "command": "Encode::Supported", "section": "", "mode": "perldoc", "summary": "Encode::Supported -- Encodings supported by Encode", "synopsis": null, "tldr_summary": null, "tldr_examples": [], "tldr_source": null, "flags": [], "examples": [], "see_also": [], "section_outline": [ { "name": "NAME", "lines": 2, "subsections": [] }, { "name": "DESCRIPTION", "lines": 1, "subsections": [ { "name": "Encoding Names", "lines": 22 } ] }, { "name": "Supported Encodings", "lines": 8, "subsections": [ { "name": "Built-in Encodings", "lines": 15 }, { "name": "Encode::Unicode -- other Unicode encodings", "lines": 20 }, { "name": "Encode::Byte -- Extended ASCII", "lines": 169 }, { "name": "Miscellaneous encodings", "lines": 37 } ] }, { "name": "Unsupported encodings", "lines": 69, "subsections": [] }, { "name": "Encoding vs. Charset -- terminology", "lines": 45, "subsections": [] }, { "name": "Encoding Classification (by Anton Tagunov and Dan Kogai)", "lines": 68, "subsections": [ { "name": "Microsoft-related naming mess", "lines": 50 } ] }, { "name": "Glossary", "lines": 66, "subsections": [] }, { "name": "References", "lines": 32, "subsections": [ { "name": "Other Notable Sites", "lines": 27 }, { "name": "Offline sources", "lines": 12 } ] } ], "sections": { "NAME": { "content": "Encode::Supported -- Encodings supported by Encode\n", "subsections": [] }, "DESCRIPTION": { "content": "", "subsections": [ { "name": "Encoding Names", "content": "Encoding names are case insensitive. White space in names is ignored. In addition, an encoding\nmay have aliases. Each encoding has one \"canonical\" name. The \"canonical\" name is chosen from\nthe names of the encoding by picking the first in the following sequence (with a few\nexceptions).\n\n* The name used by the Perl community. That includes 'utf8' and 'ascii'. Unlike aliases,\ncanonical names directly reach the method so such frequently used words like 'utf8' don't need\nto do alias lookups.\n\n* The MIME name as defined in IETF RFCs. This includes all \"iso-\"s.\n\n* The name in the IANA registry.\n\n* The name used by the organization that defined it.\n\nIn case *de jure* canonical names differ from that of the Encode module, they are always aliased\nif it ever be implemented. So you can safely tell if a given encoding is implemented or not just\nby passing the canonical name.\n\nBecause of all the alias issues, and because in the general case encodings have state, \"Encode\"\nuses an encoding object internally once an operation is in progress.\n" } ] }, "Supported Encodings": { "content": "As of Perl 5.8.0, at least the following encodings are recognized. Note that unless otherwise\nspecified, they are all case insensitive (via alias) and all occurrence of spaces are replaced\nwith '-'. In other words, \"ISO 8859 1\" and \"iso-8859-1\" are identical.\n\nEncodings are categorized and implemented in several different modules but you don't have to\n\"use Encode::XX\" to make them available for most cases. Encode.pm will automatically load those\nmodules on demand.\n", "subsections": [ { "name": "Built-in Encodings", "content": "The following encodings are always available.\n\nCanonical Aliases Comments & References\n----------------------------------------------------------------\nascii US-ascii ISO-646-US [ECMA]\nascii-ctrl Special Encoding\niso-8859-1 latin1 [ISO]\nnull Special Encoding\nutf8 UTF-8 [RFC2279]\n----------------------------------------------------------------\n\n*null* and *ascii-ctrl* are special. \"null\" fails for all character so when you set fallback\nmode to PERLQQ, HTMLCREF or XMLCREF, ALL CHARACTERS will fall back to character references.\nDitto for \"ascii-ctrl\" except for control characters. For fallback modes, see Encode.\n" }, { "name": "Encode::Unicode -- other Unicode encodings", "content": "Unicode coding schemes other than native utf8 are supported by Encode::Unicode, which will be\nautoloaded on demand.\n\n----------------------------------------------------------------\nUCS-2BE UCS-2, iso-10646-1 [IANA, UC]\nUCS-2LE [UC]\nUTF-16 [UC]\nUTF-16BE [UC]\nUTF-16LE [UC]\nUTF-32 [UC]\nUTF-32BE UCS-4 [UC]\nUTF-32LE [UC]\nUTF-7 [RFC2152]\n----------------------------------------------------------------\n\nTo find how (UCS-2|UTF-(16|32))(LE|BE)? differ from one another, see Encode::Unicode.\n\nUTF-7 is a special encoding which \"re-encodes\" UTF-16BE into a 7-bit encoding. It is implemented\nseparately by Encode::Unicode::UTF7.\n" }, { "name": "Encode::Byte -- Extended ASCII", "content": "Encode::Byte implements most single-byte encodings except for Symbols and EBCDIC. The following\nencodings are based on single-byte encodings implemented as extended ASCII. Most of them map\n\\x80-\\xff (upper half) to non-ASCII characters.\n\nISO-8859 and corresponding vendor mappings\nSince there are so many, they are presented in table format with languages and corresponding\nencoding names by vendors. Note that the table is sorted in order of ISO-8859 and the\ncorresponding vendor mappings are slightly different from that of ISO. See\n for details.\n\nLang/Regions ISO/Other Std. DOS Windows Macintosh Others\n----------------------------------------------------------------\nN. America (ASCII) cp437 AdobeStandardEncoding\ncp863 (DOSCanadaF)\nW. Europe iso-8859-1 cp850 cp1252 MacRoman nextstep\nhp-roman8\ncp860 (DOSPortuguese)\nCntrl. Europe iso-8859-2 cp852 cp1250 MacCentralEurRoman\nMacCroatian\nMacRomanian\nMacRumanian\nLatin3[1] iso-8859-3\nLatin4[2] iso-8859-4\nCyrillics iso-8859-5 cp855 cp1251 MacCyrillic\n(See also next section) cp866 MacUkrainian\nArabic iso-8859-6 cp864 cp1256 MacArabic\ncp1006 MacFarsi\nGreek iso-8859-7 cp737 cp1253 MacGreek\ncp869 (DOSGreek2)\nHebrew iso-8859-8 cp862 cp1255 MacHebrew\nTurkish iso-8859-9 cp857 cp1254 MacTurkish\nNordics iso-8859-10 cp865\ncp861 MacIcelandic\nMacSami\nThai iso-8859-11[3] cp874 MacThai\n(iso-8859-12 is nonexistent. Reserved for Indics?)\nBaltics iso-8859-13 cp775 cp1257\nCeltics iso-8859-14\nLatin9 [4] iso-8859-15\nLatin10 iso-8859-16\nVietnamese viscii cp1258 MacVietnamese\n----------------------------------------------------------------\n\n[1] Esperanto, Maltese, and Turkish. Turkish is now on 8859-9.\n[2] Baltics. Now on 8859-10, except for Latvian.\n[3] TIS 620 + Non-Breaking Space (0xA0 / U+00A0)\n[4] Nicknamed Latin0; the Euro sign as well as French and Finnish\nletters that are missing from 8859-1 were added.\n\nAll cp* are also available as ibm-*, ms-*, and windows-* . See also\n.\n\nMacintosh encodings don't seem to be registered in such entities as IANA. \"Canonical\" names in\nEncode are based upon Apple's Tech Note 1150. See\n for details.\n\nKOI8 - De Facto Standard for the Cyrillic world\nThough ISO-8859 does have ISO-8859-5, the KOI8 series is far more popular in the Net. Encode\ncomes with the following KOI charsets. For gory details, see\n\n\n----------------------------------------------------------------\nkoi8-f\nkoi8-r cp878 [RFC1489]\nkoi8-u [RFC2319]\n----------------------------------------------------------------\n\ngsm0338 - Hentai Latin 1\nGSM0338 is for GSM handsets. Though it shares alphanumerals with ASCII, control character ranges\nand other parts are mapped very differently, mainly to store Greek characters. There are also\nescape sequences (starting with 0x1B) to cover e.g. the Euro sign.\n\nThis was once handled by Encode::Bytes but because of all those unusual specifications, Encode\n2.20 has relocated the support to Encode::GSM0338. See Encode::GSM0338 for details.\n\ngsm0338 support before 2.19\nSome special cases like a trailing 0x00 byte or a lone 0x1B byte are not well-defined and\ndecode() will return an empty string for them. One possible workaround is\n\n$gsm =~ s/\\x00\\z/\\x00\\x00/;\n$uni = decode(\"gsm0338\", $gsm);\n$uni .= \"\\xA0\" if $gsm =~ /\\x1B\\z/;\n\nNote that the Encode implementation of GSM0338 does not implement the reuse of Latin capital\nletters as Greek capital letters (for example, the 0x5A is U+005A (LATIN CAPITAL LETTER Z),\nnot U+0396 (GREEK CAPITAL LETTER ZETA).\n\nThe GSM0338 is also covered in Encode::Byte even though it is not an \"extended ASCII\"\nencoding.\n\nCJK: Chinese, Japanese, Korean (Multibyte)\nNote that Vietnamese is listed above. Also read \"Encoding vs Charset\" below. Also note that\nthese are implemented in distinct modules by countries, due to the size concerns (simplified\nChinese is mapped to 'CN', continental China, while traditional Chinese is mapped to 'TW',\nTaiwan). Please refer to their respective documentation pages.\n\nEncode::CN -- Continental China\nStandard DOS/Win Macintosh Comment/Reference\n----------------------------------------------------------------\neuc-cn [1] MacChineseSimp\n(gbk) cp936 [2]\ngb12345-raw { GB12345 without CES }\ngb2312-raw { GB2312 without CES }\nhz\niso-ir-165\n----------------------------------------------------------------\n\n[1] GB2312 is aliased to this. See L\n[2] gbk is aliased to this. See L\n\nEncode::JP -- Japan\nStandard DOS/Win Macintosh Comment/Reference\n----------------------------------------------------------------\neuc-jp\nshiftjis cp932 macJapanese\n7bit-jis\niso-2022-jp [RFC1468]\niso-2022-jp-1 [RFC2237]\njis0201-raw { JIS X 0201 (roman + halfwidth kana) without CES }\njis0208-raw { JIS X 0208 (Kanji + fullwidth kana) without CES }\njis0212-raw { JIS X 0212 (Extended Kanji) without CES }\n----------------------------------------------------------------\n\nEncode::KR -- Korea\nStandard DOS/Win Macintosh Comment/Reference\n----------------------------------------------------------------\neuc-kr MacKorean [RFC1557]\ncp949 [1]\niso-2022-kr [RFC1557]\njohab [KS X 1001:1998, Annex 3]\nksc5601-raw { KSC5601 without CES }\n----------------------------------------------------------------\n\n[1] ksc5601-1987, (x-)?windows-949, and uhc are aliased to this.\nSee below.\n\nEncode::TW -- Taiwan\nStandard DOS/Win Macintosh Comment/Reference\n----------------------------------------------------------------\nbig5-eten cp950 MacChineseTrad {big5 aliased to big5-eten}\nbig5-hkscs\n----------------------------------------------------------------\n\nEncode::HanExtra -- More Chinese via CPAN\nDue to the size concerns, additional Chinese encodings below are distributed separately on\nCPAN, under the name Encode::HanExtra.\n\nStandard DOS/Win Macintosh Comment/Reference\n----------------------------------------------------------------\nbig5ext CMEX's Big5e Extension\nbig5plus CMEX's Big5+ Extension\ncccii Chinese Character Code for Information Interchange\neuc-tw EUC (Extended Unix Character)\ngb18030 GBK with Traditional Characters\n----------------------------------------------------------------\n\nEncode::JIS2K -- JIS X 0213 encodings via CPAN\nDue to size concerns, additional Japanese encodings below are distributed separately on CPAN,\nunder the name Encode::JIS2K.\n\nStandard DOS/Win Macintosh Comment/Reference\n----------------------------------------------------------------\neuc-jisx0213\nshiftjisx0123\niso-2022-jp-3\njis0213-1-raw\njis0213-2-raw\n----------------------------------------------------------------\n" }, { "name": "Miscellaneous encodings", "content": "Encode::EBCDIC\nSee perlebcdic for details.\n\n----------------------------------------------------------------\ncp37\ncp500\ncp875\ncp1026\ncp1047\nposix-bc\n----------------------------------------------------------------\n\nEncode::Symbols\nFor symbols and dingbats.\n\n----------------------------------------------------------------\nsymbol\ndingbats\nMacDingbats\nAdobeZdingbat\nAdobeSymbol\n----------------------------------------------------------------\n\nEncode::MIME::Header\nStrictly speaking, MIME header encoding documented in RFC 2047 is more of encapsulation than\nencoding. However, their support in modern world is imperative so they are supported.\n\n----------------------------------------------------------------\nMIME-Header [RFC2047]\nMIME-B [RFC2047]\nMIME-Q [RFC2047]\n----------------------------------------------------------------\n\nEncode::Guess\nThis one is not a name of encoding but a utility that lets you pick up the most appropriate\nencoding for a data out of given *suspects*. See Encode::Guess for details.\n" } ] }, "Unsupported encodings": { "content": "The following encodings are not supported as yet; some because they are rarely used, some\nbecause of technical difficulties. They may be supported by external modules via CPAN in the\nfuture, however.\n\nISO-2022-JP-2 [RFC1554]\nNot very popular yet. Needs Unicode Database or equivalent to implement encode() (because it\nincludes JIS X 0208/0212, KSC5601, and GB2312 simultaneously, whose code points in Unicode\noverlap. So you need to lookup the database to determine to what character set a given Unicode\ncharacter should belong).\n\nISO-2022-CN [RFC1922]\nNot very popular. Needs CNS 11643-1 and -2 which are not available in this module. CNS 11643\nis supported (via euc-tw) in Encode::HanExtra. Audrey Tang may add support for this encoding\nin her module in future.\n\nVarious HP-UX encodings\nThe following are unsupported due to the lack of mapping data.\n\n'8' - arabic8, greek8, hebrew8, kana8, thai8, and turkish8\n'15' - japanese15, korean15, and roi15\n\nCyrillic encoding ISO-IR-111\nAnton Tagunov doubts its usefulness.\n\nISO-8859-8-1 [Hebrew]\nNone of the Encode team knows Hebrew enough (ISO-8859-8, cp1255 and MacHebrew are supported\nbecause and just because there were mappings available at ).\nContributions welcome.\n\nISIRI 3342, Iran System, ISIRI 2900 [Farsi]\nDitto.\n\nThai encoding TCVN\nDitto.\n\nVietnamese encodings VPS\nThough Jungshik Shin has reported that Mozilla supports this encoding, it was too late before\n5.8.0 for us to add it. In the future, it may be available via a separate module. See\n and\n if you are interested in\nhelping us.\n\nVarious Mac encodings\nThe following are unsupported due to the lack of mapping data.\n\nMacArmenian, MacBengali, MacBurmese, MacEthiopic\nMacExtArabic, MacGeorgian, MacKannada, MacKhmer\nMacLaotian, MacMalayalam, MacMongolian, MacOriya\nMacSinhalese, MacTamil, MacTelugu, MacTibetan\nMacVietnamese\n\nThe rest which are already available are based upon the vendor mappings at\n .\n\n(Mac) Indic encodings\nThe maps for the following are available at but remain unsupported\nbecause those encodings need an algorithmical approach, currently unsupported by enc2xs:\n\nMacDevanagari\nMacGurmukhi\nMacGujarati\n\nFor details, please see \"Unicode mapping issues and notes:\" at\n .\n\nI believe this issue is prevalent not only for Mac Indics but also in other Indic encodings,\nbut the above were the only Indic encodings maps that I could find at\n .\n", "subsections": [] }, "Encoding vs. Charset -- terminology": { "content": "We are used to using the term (character) *encoding* and *character set* interchangeably. But\njust as confusing the terms byte and character is dangerous and the terms should be\ndifferentiated when needed, we need to differentiate *encoding* and *character set*.\n\nTo understand that, here is a description of how we make computers grok our characters.\n\n* First we start with which characters to include. We call this collection of characters\n*character repertoire*.\n\n* Then we have to give each character a unique ID so your computer can tell the difference\nbetween 'a' and 'A'. This itemized character repertoire is now a *character set*.\n\n* If your computer can grow the character set without further processing, you can go ahead and\nuse it. This is called a *coded character set* (CCS) or *raw character encoding*. ASCII is\nused this way for most cases.\n\n* But in many cases, especially multi-byte CJK encodings, you have to tweak a little more. Your\nnetwork connection may not accept any data with the Most Significant Bit set, and your\ncomputer may not be able to tell if a given byte is a whole character or just half of it. So\nyou have to *encode* the character set to use it.\n\nA *character encoding scheme* (CES) determines how to encode a given character set, or a set\nof multiple character sets. 7bit ISO-2022 is an example of a CES. You switch between character\nsets via *escape sequences*.\n\nTechnically, or mathematically, speaking, a character set encoded in such a CES that maps\ncharacter by character may form a CCS. EUC is such an example. The CES of EUC is as follows:\n\n* Map ASCII unchanged.\n\n* Map such a character set that consists of 94 or 96 powered by N members by adding 0x80 to each\nbyte.\n\n* You can also use 0x8e and 0x8f to indicate that the following sequence of characters belongs\nto yet another character set. To each following byte is added the value 0x80.\n\nBy carefully looking at the encoded byte sequence, you can find that the byte sequence conforms\na unique number. In that sense, EUC is a CCS generated by a CES above from up to four CCS\n(complicated?). UTF-8 falls into this category. See \"UTF-8\" in perlUnicode to find out how UTF-8\nmaps Unicode to a byte sequence.\n\nYou may also have found out by now why 7bit ISO-2022 cannot comprise a CCS. If you look at a\nbyte sequence \\x21\\x21, you can't tell if it is two !'s or IDEOGRAPHIC SPACE. EUC maps the\nlatter to \\xA1\\xA1 so you have no trouble differentiating between \"!!\". and \" \".\n", "subsections": [] }, "Encoding Classification (by Anton Tagunov and Dan Kogai)": { "content": "This section tries to classify the supported encodings by their applicability for information\nexchange over the Internet and to choose the most suitable aliases to name them in the context\nof such communication.\n\n* To (en|de)code encodings marked by \"()\", you need \"Encode::HanExtra\", available from CPAN.\n\nEncoding names\n\nUS-ASCII UTF-8 ISO-8859-* KOI8-R\nShiftJIS EUC-JP ISO-2022-JP ISO-2022-JP-1\nEUC-KR Big5 GB2312\n\nare registered with IANA as preferred MIME names and may be used over the Internet.\n\n\"ShiftJIS\" has been officialized by JIS X 0208:1997. \"Microsoft-related naming mess\" gives\ndetails.\n\n\"GB2312\" is the IANA name for \"EUC-CN\". See \"Microsoft-related naming mess\" for details.\n\n\"GB2312-80\" *raw* encoding is available as \"gb2312-raw\" with Encode. See Encode::CN for\ndetails.\n\nEUC-CN\nKOI8-U [RFC2319]\n\nhave not been registered with IANA (as of March 2002) but seem to be supported by major web\nbrowsers. The IANA name for \"EUC-CN\" is \"GB2312\".\n\nKSC5601-1987\n\nis heavily misused. See \"Microsoft-related naming mess\" for details.\n\n\"KSC5601-1987\" *raw* encoding is available as \"kcs5601-raw\" with Encode. See Encode::KR for\ndetails.\n\nUTF-16 UTF-16BE UTF-16LE\n\nare IANA-registered \"charset\"s. See [RFC 2781] for details. Jungshik Shin reports that UTF-16\nwith a BOM is well accepted by MS IE 5/6 and NS 4/6. Beware however that\n\n* \"UTF-16\" support in any software you're going to be using/interoperating with has probably\nbeen less tested then \"UTF-8\" support\n\n* \"UTF-8\" coded data seamlessly passes traditional command piping (\"cat\", \"more\", etc.) while\n\"UTF-16\" coded data is likely to cause confusion (with its zero bytes, for example)\n\n* it is beyond the power of words to describe the way HTML browsers encode non-\"ASCII\" form\ndata. To get a general impression, visit\n. While encoding of form data has\nstabilized for \"UTF-8\" encoded pages (at least IE 5/6, NS 6, and Opera 6 behave consistently),\nbe sure to expect fun (and cross-browser discrepancies) with \"UTF-16\" encoded pages!\n\nThe rule of thumb is to use \"UTF-8\" unless you know what you're doing and unless you really\nbenefit from using \"UTF-16\".\n\nISO-IR-165 [RFC1345]\nVISCII\nGB 12345\nGB 18030 () (see links below)\nEUC-TW ()\n\nare totally valid encodings but not registered at IANA. The names under which they are listed\nhere are probably the most widely-known names for these encodings and are recommended names.\n\nBIG5PLUS ()\n\nis a proprietary name.\n", "subsections": [ { "name": "Microsoft-related naming mess", "content": "Microsoft products misuse the following names:\n\nKSC5601-1987\nMicrosoft extension to \"EUC-KR\".\n\nProper names: \"CP949\", \"UHC\", \"x-windows-949\" (as used by Mozilla).\n\nSee for details.\n\nEncode aliases \"KSC5601-1987\" to \"cp949\" to reflect this common misusage. *Raw*\n\"KSC5601-1987\" encoding is available as \"kcs5601-raw\".\n\nSee Encode::KR for details.\n\nGB2312\nMicrosoft extension to \"EUC-CN\".\n\nProper names: \"CP936\", \"GBK\".\n\n\"GB2312\" has been registered in the \"EUC-CN\" meaning at IANA. This has partially repaired the\nsituation: Microsoft's \"GB2312\" has become a superset of the official \"GB2312\".\n\nEncode aliases \"GB2312\" to \"euc-cn\" in full agreement with IANA registration. \"cp936\" is\nsupported separately. *Raw* \"GB2312-80\" encoding is available as \"gb2312-raw\".\n\nSee Encode::CN for details.\n\nBig5\nMicrosoft extension to \"Big5\".\n\nProper name: \"CP950\".\n\nEncode separately supports \"Big5\" and \"cp950\".\n\nShiftJIS\nMicrosoft's understanding of \"ShiftJIS\".\n\nJIS has not endorsed the full Microsoft standard however. The official \"ShiftJIS\" includes\nonly JIS X 0201 and JIS X 0208 character sets, while Microsoft has always used \"ShiftJIS\" to\nencode a wider character repertoire. See \"IANA\" registration for \"Windows-31J\".\n\nAs a historical predecessor, Microsoft's variant probably has more rights for the name, though\nit may be objected that Microsoft shouldn't have used JIS as part of the name in the first\nplace.\n\nUnambiguous name: \"CP932\". \"IANA\" name (also used by Mozilla, and provided as an alias by\nEncode): \"Windows-31J\".\n\nEncode separately supports \"ShiftJIS\" and \"cp932\".\n" } ] }, "Glossary": { "content": "character repertoire\nA collection of unique characters. A *character* set in the strictest sense. At this stage,\ncharacters are not numbered.\n\ncoded character set (CCS)\nA character set that is mapped in a way computers can use directly. Many character encodings,\nincluding EUC, fall in this category.\n\ncharacter encoding scheme (CES)\nAn algorithm to map a character set to a byte sequence. You don't have to be able to tell\nwhich character set a given byte sequence belongs. 7-bit ISO-2022 is a CES but it cannot be a\nCCS. EUC is an example of being both a CCS and CES.\n\ncharset (in MIME context)\nhas long been used in the meaning of \"encoding\", CES.\n\nWhile the word combination \"character set\" has lost this meaning in MIME context since [RFC\n2130], the \"charset\" abbreviation has retained it. This is how [RFC 2277] and [RFC 2278] bless\n\"charset\":\n\nThis document uses the term \"charset\" to mean a set of rules for\nmapping from a sequence of octets to a sequence of characters, such\nas the combination of a coded character set and a character encoding\nscheme; this is also what is used as an identifier in MIME \"charset=\"\nparameters, and registered in the IANA charset registry ... (Note\nthat this is NOT a term used by other standards bodies, such as ISO).\n[RFC 2277]\n\nEUC\nExtended Unix Character. See ISO-2022.\n\nISO-2022\nA CES that was carefully designed to coexist with ASCII. There are a 7 bit version and an 8\nbit version.\n\nThe 7 bit version switches character set via escape sequence so it cannot form a CCS. Since\nthis is more difficult to handle in programs than the 8 bit version, the 7 bit version is not\nvery popular except for iso-2022-jp, the *de facto* standard CES for e-mails.\n\nThe 8 bit version can form a CCS. EUC and ISO-8859 are two examples thereof. Pre-5.6 perl\ncould use them as string literals.\n\nUCS\nShort for *Universal Character Set*. When you say just UCS, it means *Unicode*.\n\nUCS-2\nISO/IEC 10646 encoding form: Universal Character Set coded in two octets.\n\nUnicode\nA character set that aims to include all character repertoires of the world. Many character\nsets in various national as well as industrial standards have become, in a way, just subsets\nof Unicode.\n\nUTF\nShort for *Unicode Transformation Format*. Determines how to map a Unicode character into a\nbyte sequence.\n\nUTF-16\nA UTF in 16-bit encoding. Can either be in big endian or little endian. The big endian version\nis called UTF-16BE (equal to UCS-2 + surrogate support) and the little endian version is\ncalled UTF-16LE.\n\nSee Also\nEncode, Encode::Byte, Encode::CN, Encode::JP, Encode::KR, Encode::TW, Encode::EBCDIC,\nEncode::Symbol Encode::MIME::Header, Encode::Guess\n", "subsections": [] }, "References": { "content": "ECMA\nEuropean Computer Manufacturers Association \n\nECMA-035 (eq \"ISO-2022\")\n\n\nThe specification of ISO-2022 is available from the link above.\n\nIANA\nInternet Assigned Numbers Authority \n\nAssigned Charset Names by IANA\n\n\nMost of the \"canonical names\" in Encode derive from this list so you can directly apply the\nstring you have extracted from MIME header of mails and web pages.\n\nISO\nInternational Organization for Standardization \n\nRFC\nRequest For Comments -- need I say more? ,\n, \n\nUC\nUnicode Consortium \n\nUnicode Glossary\n\n\nThe glossary of this document is based upon this site.\n", "subsections": [ { "name": "Other Notable Sites", "content": "czyborra.com\n\n\nContains a lot of useful information, especially gory details of ISO vs. vendor mappings.\n\nCJK.inf\n\n\nSomewhat obsolete (last update in 1996), but still useful. Also try\n\n\n\nYou will find brief info on \"EUC-CN\", \"GBK\" and mostly on \"GB 18030\".\n\nJungshik Shin's Hangul FAQ\n\n\nAnd especially its subject 8.\n\n\n\nA comprehensive overview of the Korean (\"KS *\") standards.\n\ndebian.org: \"Introduction to i18n\"\nA brief description for most of the mentioned CJK encodings is contained in\n\n" }, { "name": "Offline sources", "content": "\"CJKV Information Processing\" by Ken Lunde\nCJKV Information Processing 1999 O'Reilly & Associates, ISBN : 1-56592-224-7\n\nThe modern successor of \"CJK.inf\".\n\nFeatures a comprehensive coverage of CJKV character sets and encodings along with many other\nissues faced by anyone trying to better support CJKV languages/scripts in all the areas of\ninformation processing.\n\nTo purchase this book, visit or your favourite\nbookstore.\n" } ] } } } }