{ "content": [ { "type": "text", "text": "# perlebcdic (perldoc)\n\n## NAME\n\nperlebcdic - Considerations for running Perl on EBCDIC platforms\n\n## DESCRIPTION\n\nAn exploration of some of the issues facing Perl programmers on EBCDIC based computers.\n\n## Sections\n\n- **NAME**\n- **DESCRIPTION**\n- **COMMON CHARACTER CODE SETS** (3 subsections)\n- **SINGLE OCTET TABLES** (1 subsections)\n- **IDENTIFYING CHARACTER CODE SETS** (1 subsections)\n- **CONVERSIONS**\n- **OPERATOR DIFFERENCES**\n- **FUNCTION DIFFERENCES** (7 subsections)\n- **REGULAR EXPRESSION DIFFERENCES**\n- **SOCKETS**\n- **SORTING** (3 subsections)\n- **TRANSFORMATION FORMATS** (2 subsections)\n- **Hashing order and checksums**\n- **I18N AND L10N**\n- **MULTI-OCTET CHARACTER SETS**\n- **OS ISSUES**\n- **BUGS**\n- **SEE ALSO**\n- **REFERENCES**\n- **HISTORY**\n- **AUTHOR**\n\nUse structuredContent.sections for detailed options, examples, and full documentation.\n" } ], "structuredContent": { "command": "perlebcdic", "section": "", "mode": "perldoc", "summary": "perlebcdic - Considerations for running Perl on EBCDIC platforms", "synopsis": null, "tldr_summary": null, "tldr_examples": [], "tldr_source": null, "flags": [], "examples": [], "see_also": [], "section_outline": [ { "name": "NAME", "lines": 2, "subsections": [] }, { "name": "DESCRIPTION", "lines": 39, "subsections": [] }, { "name": "COMMON CHARACTER CODE SETS", "lines": 83, "subsections": [ { "name": "Unicode code points versus EBCDIC code points", "lines": 28 }, { "name": "Unicode and UTF", "lines": 45 }, { "name": "Using Encode", "lines": 46 } ] }, { "name": "SINGLE OCTET TABLES", "lines": 375, "subsections": [ { "name": "Table in hex, sorted in 1047 order", "lines": 267 } ] }, { "name": "IDENTIFYING CHARACTER CODE SETS", "lines": 11, "subsections": [ { "name": "chr", "lines": 29 } ] }, { "name": "CONVERSIONS", "lines": 69, "subsections": [] }, { "name": "OPERATOR DIFFERENCES", "lines": 71, "subsections": [] }, { "name": "FUNCTION DIFFERENCES", "lines": 1, "subsections": [ { "name": "chr", "lines": 4 }, { "name": "ord", "lines": 2 }, { "name": "pack", "lines": 39 }, { "name": "printf", "lines": 5 }, { "name": "sort", "lines": 2 }, { "name": "sprintf", "lines": 4 }, { "name": "unpack", "lines": 11 } ] }, { "name": "REGULAR EXPRESSION DIFFERENCES", "lines": 140, "subsections": [] }, { "name": "SOCKETS", "lines": 4, "subsections": [] }, { "name": "SORTING", "lines": 22, "subsections": [ { "name": "Ignore ASCII vs. EBCDIC sort differences.", "lines": 2 }, { "name": "Use a sort helper function", "lines": 55 }, { "name": "Perform sorting on one type of platform only.", "lines": 2 } ] }, { "name": "TRANSFORMATION FORMATS", "lines": 76, "subsections": [ { "name": "Quoted-Printable encoding and decoding", "lines": 40 }, { "name": "Caesarean ciphers", "lines": 20 } ] }, { "name": "Hashing order and checksums", "lines": 5, "subsections": [] }, { "name": "I18N AND L10N", "lines": 4, "subsections": [] }, { "name": "MULTI-OCTET CHARACTER SETS", "lines": 5, "subsections": [] }, { "name": "OS ISSUES", "lines": 45, "subsections": [] }, { "name": "BUGS", "lines": 15, "subsections": [] }, { "name": "SEE ALSO", "lines": 2, "subsections": [] }, { "name": "REFERENCES", "lines": 24, "subsections": [] }, { "name": "HISTORY", "lines": 2, "subsections": [] }, { "name": "AUTHOR", "lines": 8, "subsections": [] } ], "sections": { "NAME": { "content": "perlebcdic - Considerations for running Perl on EBCDIC platforms\n", "subsections": [] }, "DESCRIPTION": { "content": "An exploration of some of the issues facing Perl programmers on EBCDIC based computers.\n\nPortions of this document that are still incomplete are marked with XXX.\n\nEarly Perl versions worked on some EBCDIC machines, but the last known version that ran on\nEBCDIC was v5.8.7, until v5.22, when the Perl core again works on z/OS. Theoretically, it could\nwork on OS/400 or Siemens' BS2000 (or their successors), but this is untested. In v5.22 and\n5.24, not all the modules found on CPAN but shipped with core Perl work on z/OS.\n\nIf you want to use Perl on a non-z/OS EBCDIC machine, please let us know at\n.\n\nWriting Perl on an EBCDIC platform is really no different than writing on an \"ASCII\" one, but\nwith different underlying numbers, as we'll see shortly. You'll have to know something about\nthose \"ASCII\" platforms because the documentation is biased and will frequently use example\nnumbers that don't apply to EBCDIC. There are also very few CPAN modules that are written for\nEBCDIC and which don't work on ASCII; instead the vast majority of CPAN modules are written for\nASCII, and some may happen to work on EBCDIC, while a few have been designed to portably work on\nboth.\n\nIf your code just uses the 52 letters A-Z and a-z, plus SPACE, the digits 0-9, and the\npunctuation characters that Perl uses, plus a few controls that are denoted by escape sequences\nlike \"\\n\" and \"\\t\", then there's nothing special about using Perl, and your code may very well\nwork on an ASCII machine without change.\n\nBut if you write code that uses \"\\005\" to mean a TAB or \"\\xC1\" to mean an \"A\", or \"\\xDF\" to mean\na \"ÿ\" (small \"y\" with a diaeresis), then your code may well work on your EBCDIC platform, but\nnot on an ASCII one. That's fine to do if no one will ever want to run your code on an ASCII\nplatform; but the bias in this document will be towards writing code portable between EBCDIC and\nASCII systems. Again, if every character you care about is easily enterable from your keyboard,\nyou don't have to know anything about ASCII, but many keyboards don't easily allow you to\ndirectly enter, say, the character \"\\xDF\", so you have to specify it indirectly, such as by\nusing the \"\\xDF\" escape sequence. In those cases it's easiest to know something about the\nASCII/Unicode character sets. If you know that the small \"ÿ\" is \"U+00FF\", then you can instead\nspecify it as \"\\N{U+FF}\", and have the computer automatically translate it to \"\\xDF\" on your\nplatform, and leave it as \"\\xFF\" on ASCII ones. Or you could specify it by name, \"\\N{LATIN SMALL\nLETTER Y WITH DIAERESIS\" and not have to know the numbers. Either way works, but both require\nfamiliarity with Unicode.\n", "subsections": [] }, "COMMON CHARACTER CODE SETS": { "content": "ASCII\nThe American Standard Code for Information Interchange (ASCII or US-ASCII) is a set of integers\nrunning from 0 to 127 (decimal) that have standardized interpretations by the computers which\nuse ASCII. For example, 65 means the letter \"A\". The range 0..127 can be covered by setting\nvarious bits in a 7-bit binary digit, hence the set is sometimes referred to as \"7-bit ASCII\".\nASCII was described by the American National Standards Institute document ANSI X3.4-1986. It was\nalso described by ISO 646:1991 (with localization for currency symbols). The full ASCII set is\ngiven in the table below as the first 128 elements. Languages that can be written adequately\nwith the characters in ASCII include English, Hawaiian, Indonesian, Swahili and some Native\nAmerican languages.\n\nMost non-EBCDIC character sets are supersets of ASCII. That is the integers 0-127 mean what\nASCII says they mean. But integers 128 and above are specific to the character set.\n\nMany of these fit entirely into 8 bits, using ASCII as 0-127, while specifying what 128-255\nmean, and not using anything above 255. Thus, these are single-byte (or octet if you prefer)\ncharacter sets. One important one (since Unicode is a superset of it) is the ISO 8859-1\ncharacter set.\n\nISO 8859\nThe ISO 8859-*$n* are a collection of character code sets from the International Organization\nfor Standardization (ISO), each of which adds characters to the ASCII set that are typically\nfound in various languages, many of which are based on the Roman, or Latin, alphabet. Most are\nfor European languages, but there are also ones for Arabic, Greek, Hebrew, and Thai. There are\ngood references on the web about all these.\n\nLatin 1 (ISO 8859-1)\nA particular 8-bit extension to ASCII that includes grave and acute accented Latin characters.\nLanguages that can employ ISO 8859-1 include all the languages covered by ASCII as well as\nAfrikaans, Albanian, Basque, Catalan, Danish, Faroese, Finnish, Norwegian, Portuguese, Spanish,\nand Swedish. Dutch is covered albeit without the ij ligature. French is covered too but without\nthe oe ligature. German can use ISO 8859-1 but must do so without German-style quotation marks.\nThis set is based on Western European extensions to ASCII and is commonly encountered in world\nwide web work. In IBM character code set identification terminology, ISO 8859-1 is also known as\nCCSID 819 (or sometimes 0819 or even 00819).\n\nEBCDIC\nThe Extended Binary Coded Decimal Interchange Code refers to a large collection of single- and\nmulti-byte coded character sets that are quite different from ASCII and ISO 8859-1, and are all\nslightly different from each other; they typically run on host computers. The EBCDIC encodings\nderive from 8-bit byte extensions of Hollerith punched card encodings, which long predate ASCII.\nThe layout on the cards was such that high bits were set for the upper and lower case alphabetic\ncharacters \"[a-z]\" and \"[A-Z]\", but there were gaps within each Latin alphabet range, visible in\nthe table below. These gaps can cause complications.\n\nSome IBM EBCDIC character sets may be known by character code set identification numbers (CCSID\nnumbers) or code page numbers.\n\nPerl can be compiled on platforms that run any of three commonly used EBCDIC character sets,\nlisted below.\n\nThe 13 variant characters\nAmong IBM EBCDIC character code sets there are 13 characters that are often mapped to different\ninteger values. Those characters are known as the 13 \"variant\" characters and are:\n\n\\ [ ] { } ^ ~ ! # | $ @ `\n\nWhen Perl is compiled for a platform, it looks at all of these characters to guess which EBCDIC\ncharacter set the platform uses, and adapts itself accordingly to that platform. If the platform\nuses a character set that is not one of the three Perl knows about, Perl will either fail to\ncompile, or mistakenly and silently choose one of the three.\n\nThe Line Feed (LF) character is actually a 14th variant character, and Perl checks for that as\nwell.\n\nEBCDIC code sets recognized by Perl\n0037\nCharacter code set ID 0037 is a mapping of the ASCII plus Latin-1 characters (i.e. ISO\n8859-1) to an EBCDIC set. 0037 is used in North American English locales on the OS/400\noperating system that runs on AS/400 computers. CCSID 0037 differs from ISO 8859-1 in 236\nplaces; in other words they agree on only 20 code point values.\n\n1047\nCharacter code set ID 1047 is also a mapping of the ASCII plus Latin-1 characters (i.e. ISO\n8859-1) to an EBCDIC set. 1047 is used under Unix System Services for OS/390 or z/OS, and\nOpenEdition for VM/ESA. CCSID 1047 differs from CCSID 0037 in eight places, and from ISO\n8859-1 in 236.\n\nPOSIX-BC\nThe EBCDIC code page in use on Siemens' BS2000 system is distinct from 1047 and 0037. It is\nidentified below as the POSIX-BC set. Like 0037 and 1047, it is the same as ISO 8859-1 in 20\ncode point values.\n", "subsections": [ { "name": "Unicode code points versus EBCDIC code points", "content": "In Unicode terminology a *code point* is the number assigned to a character: for example, in\nEBCDIC the character \"A\" is usually assigned the number 193. In Unicode, the character \"A\" is\nassigned the number 65. All the code points in ASCII and Latin-1 (ISO 8859-1) have the same\nmeaning in Unicode. All three of the recognized EBCDIC code sets have 256 code points, and in\neach code set, all 256 code points are mapped to equivalent Latin1 code points. Obviously, \"A\"\nwill map to \"A\", \"B\" => \"B\", \"%\" => \"%\", etc., for all printable characters in Latin1 and these\ncode pages.\n\nIt also turns out that EBCDIC has nearly precise equivalents for the ASCII/Latin1 C0 controls\nand the DELETE control. (The C0 controls are those whose ASCII code points are 0..0x1F; things\nlike TAB, ACK, BEL, etc.) A mapping is set up between these ASCII/EBCDIC controls. There isn't\nsuch a precise mapping between the C1 controls on ASCII platforms and the remaining EBCDIC\ncontrols. What has been done is to map these controls, mostly arbitrarily, to some otherwise\nunmatched character in the other character set. Most of these are very very rarely used nowadays\nin EBCDIC anyway, and their names have been dropped, without much complaint. For example the EO\n(Eight Ones) EBCDIC control (consisting of eight one bits = 0xFF) is mapped to the C1 APC\ncontrol (0x9F), and you can't use the name \"EO\".\n\nThe EBCDIC controls provide three possible line terminator characters, CR (0x0D), LF (0x25), and\nNL (0x15). On ASCII platforms, the symbols \"NL\" and \"LF\" refer to the same character, but in\nstrict EBCDIC terminology they are different ones. The EBCDIC NL is mapped to the C1 control\ncalled \"NEL\" (\"Next Line\"; here's a case where the mapping makes quite a bit of sense, and hence\nisn't just arbitrary). On some EBCDIC platforms, this NL or NEL is the typical line terminator.\nThis is true of z/OS and BS2000. In these platforms, the C compilers will swap the LF and NEL\ncode points, so that \"\\n\" is 0x15, and refers to NL. Perl does that too; you can see it in the\ncode chart below. This makes things generally \"just work\" without you even having to be aware\nthat there is a swap.\n" }, { "name": "Unicode and UTF", "content": "UTF stands for \"Unicode Transformation Format\". UTF-8 is an encoding of Unicode into a sequence\nof 8-bit byte chunks, based on ASCII and Latin-1. The length of a sequence required to represent\na Unicode code point depends on the ordinal number of that code point, with larger numbers\nrequiring more bytes. UTF-EBCDIC is like UTF-8, but based on EBCDIC. They are enough alike that\noften, casual usage will conflate the two terms, and use \"UTF-8\" to mean both the UTF-8 found on\nASCII platforms, and the UTF-EBCDIC found on EBCDIC ones.\n\nYou may see the term \"invariant\" character or code point. This simply means that the character\nhas the same numeric value and representation when encoded in UTF-8 (or UTF-EBCDIC) as when not.\n(Note that this is a very different concept from \"The 13 variant characters\" mentioned above.\nCareful prose will use the term \"UTF-8 invariant\" instead of just \"invariant\", but most often\nyou'll see just \"invariant\".) For example, the ordinal value of \"A\" is 193 in most EBCDIC code\npages, and also is 193 when encoded in UTF-EBCDIC. All UTF-8 (or UTF-EBCDIC) variant code points\noccupy at least two bytes when encoded in UTF-8 (or UTF-EBCDIC); by definition, the UTF-8 (or\nUTF-EBCDIC) invariant code points are exactly one byte whether encoded in UTF-8 (or UTF-EBCDIC),\nor not. (By now you see why people typically just say \"UTF-8\" when they also mean \"UTF-EBCDIC\".\nFor the rest of this document, we'll mostly be casual about it too.) In ASCII UTF-8, the code\npoints corresponding to the lowest 128 ordinal numbers (0 - 127: the ASCII characters) are\ninvariant. In UTF-EBCDIC, there are 160 invariant characters. (If you care, the EBCDIC\ninvariants are those characters which have ASCII equivalents, plus those that correspond to the\nC1 controls (128 - 159 on ASCII platforms).)\n\nA string encoded in UTF-EBCDIC may be longer (very rarely shorter) than one encoded in UTF-8.\nPerl extends both UTF-8 and UTF-EBCDIC so that they can encode code points above the Unicode\nmaximum of U+10FFFF. Both extensions are constructed to allow encoding of any code point that\nfits in a 64-bit word.\n\nUTF-EBCDIC is defined by Unicode Technical Report #16 \n(often referred to as just TR16). It is defined based on CCSID 1047, not allowing for the\ndifferences for other code pages. This allows for easy interchange of text between computers\nrunning different code pages, but makes it unusable, without adaptation, for Perl on those other\ncode pages.\n\nThe reason for this unusability is that a fundamental assumption of Perl is that the characters\nit cares about for parsing and lexical analysis are the same whether or not the text is in\nUTF-8. For example, Perl expects the character \"[\" to have the same representation, no matter if\nthe string containing it (or program text) is UTF-8 encoded or not. To ensure this, Perl adapts\nUTF-EBCDIC to the particular code page so that all characters it expects to be UTF-8 invariant\nare in fact UTF-8 invariant. This means that text generated on a computer running one version of\nPerl's UTF-EBCDIC has to be translated to be intelligible to a computer running another.\n\nTR16 implies a method to extend UTF-EBCDIC to encode points up through \"2 31 - 1\". Perl uses\nthis method for code points up through \"2 30 - 1\", but uses an incompatible method for larger\nones, to enable it to handle much larger code points than otherwise.\n" }, { "name": "Using Encode", "content": "Starting from Perl 5.8 you can use the standard module Encode to translate from EBCDIC to\nLatin-1 code points. Encode knows about more EBCDIC character sets than Perl can currently be\ncompiled to run on.\n\nuse Encode 'fromto';\n\nmy %ebcdic = ( 176 => 'cp37', 95 => 'cp1047', 106 => 'posix-bc' );\n\n# $a is in EBCDIC code points\nfromto($a, $ebcdic{ord '^'}, 'latin1');\n# $a is ISO 8859-1 code points\n\nand from Latin-1 code points to EBCDIC code points\n\nuse Encode 'fromto';\n\nmy %ebcdic = ( 176 => 'cp37', 95 => 'cp1047', 106 => 'posix-bc' );\n\n# $a is ISO 8859-1 code points\nfromto($a, 'latin1', $ebcdic{ord '^'});\n# $a is in EBCDIC code points\n\nFor doing I/O it is suggested that you use the autotranslating features of PerlIO, see\nperluniintro.\n\nSince version 5.8 Perl uses the PerlIO I/O library. This enables you to use different encodings\nper IO channel. For example you may use\n\nuse Encode;\nopen($f, \">:encoding(ascii)\", \"test.ascii\");\nprint $f \"Hello World!\\n\";\nopen($f, \">:encoding(cp37)\", \"test.ebcdic\");\nprint $f \"Hello World!\\n\";\nopen($f, \">:encoding(latin1)\", \"test.latin1\");\nprint $f \"Hello World!\\n\";\nopen($f, \">:encoding(utf8)\", \"test.utf8\");\nprint $f \"Hello World!\\n\";\n\nto get four files containing \"Hello World!\\n\" in ASCII, CP 0037 EBCDIC, ISO 8859-1 (Latin-1) (in\nthis example identical to ASCII since only ASCII characters were printed), and UTF-EBCDIC (in\nthis example identical to normal EBCDIC since only characters that don't differ between EBCDIC\nand UTF-EBCDIC were printed). See the documentation of Encode::PerlIO for details.\n\nAs the PerlIO layer uses raw IO (bytes) internally, all this totally ignores things like the\ntype of your filesystem (ASCII or EBCDIC).\n" } ] }, "SINGLE OCTET TABLES": { "content": "The following tables list the ASCII and Latin 1 ordered sets including the subsets: C0 controls\n(0..31), ASCII graphics (32..7e), delete (7f), C1 controls (80..9f), and Latin-1 (a.k.a. ISO\n8859-1) (a0..ff). In the table names of the Latin 1 extensions to ASCII have been labelled with\ncharacter names roughly corresponding to *The Unicode Standard, Version 6.1* albeit with\nsubstitutions such as \"s/LATIN//\" and \"s/VULGAR//\" in all cases; \"s/CAPITAL LETTER//\" in some\ncases; and \"s/SMALL LETTER ([A-Z])/\\l$1/\" in some other cases. Controls are listed using their\nUnicode 6.2 abbreviations. The differences between the 0037 and 1047 sets are flagged with \"\".\nThe differences between the 1047 and POSIX-BC sets are flagged with \"##.\" All ord() numbers\nlisted are decimal. If you would rather see this table listing octal values, then run the table\n(that is, the pod source text of this document, since this recipe may not work with a\npod2otherformat translation) through:\n\nrecipe 0\n\nperl -ne 'if(/(.{29})(\\d+)\\s+(\\d+)\\s+(\\d+)\\s+(\\d+)/)' \\\n-e '{printf(\"%s%-5.03o%-5.03o%-5.03o%.03o\\n\",$1,$2,$3,$4,$5)}' \\\nperlebcdic.pod\n\nIf you want to retain the UTF-x code points then in script form you might want to write:\n\nrecipe 1\n\nopen(FH,\") {\nif (/(.{29})(\\d+)\\s+(\\d+)\\s+(\\d+)\\s+(\\d+)\\s+(\\d+)\\.?(\\d*)\n\\s+(\\d+)\\.?(\\d*)/x)\n{\nif ($7 ne '' && $9 ne '') {\nprintf(\n\"%s%-5.03o%-5.03o%-5.03o%-5.03o%-3o.%-5o%-3o.%.03o\\n\",\n$1,$2,$3,$4,$5,$6,$7,$8,$9);\n}\nelsif ($7 ne '') {\nprintf(\"%s%-5.03o%-5.03o%-5.03o%-5.03o%-3o.%-5o%.03o\\n\",\n$1,$2,$3,$4,$5,$6,$7,$8);\n}\nelse {\nprintf(\"%s%-5.03o%-5.03o%-5.03o%-5.03o%-5.03o%.03o\\n\",\n$1,$2,$3,$4,$5,$6,$8);\n}\n}\n}\n\nIf you would rather see this table listing hexadecimal values then run the table through:\n\nrecipe 2\n\nperl -ne 'if(/(.{29})(\\d+)\\s+(\\d+)\\s+(\\d+)\\s+(\\d+)/)' \\\n-e '{printf(\"%s%-5.02X%-5.02X%-5.02X%.02X\\n\",$1,$2,$3,$4,$5)}' \\\nperlebcdic.pod\n\nOr, in order to retain the UTF-x code points in hexadecimal:\n\nrecipe 3\n\nopen(FH,\") {\nif (/(.{29})(\\d+)\\s+(\\d+)\\s+(\\d+)\\s+(\\d+)\\s+(\\d+)\\.?(\\d*)\n\\s+(\\d+)\\.?(\\d*)/x)\n{\nif ($7 ne '' && $9 ne '') {\nprintf(\n\"%s%-5.02X%-5.02X%-5.02X%-5.02X%-2X.%-6.02X%02X.%02X\\n\",\n$1,$2,$3,$4,$5,$6,$7,$8,$9);\n}\nelsif ($7 ne '') {\nprintf(\"%s%-5.02X%-5.02X%-5.02X%-5.02X%-2X.%-6.02X%02X\\n\",\n$1,$2,$3,$4,$5,$6,$7,$8);\n}\nelse {\nprintf(\"%s%-5.02X%-5.02X%-5.02X%-5.02X%-5.02X%02X\\n\",\n$1,$2,$3,$4,$5,$6,$8);\n}\n}\n}\n\n\nISO\n8859-1 POS- CCSID\nCCSID CCSID CCSID IX- 1047\nchr 0819 0037 1047 BC UTF-8 UTF-EBCDIC\n---------------------------------------------------------------------\n 0 0 0 0 0 0\n 1 1 1 1 1 1\n 2 2 2 2 2 2\n 3 3 3 3 3 3\n 4 55 55 55 4 55\n 5 45 45 45 5 45\n 6 46 46 46 6 46\n 7 47 47 47 7 47\n 8 22 22 22 8 22\n 9 5 5 5 9 5\n 10 37 21 21 10 21\n 11 11 11 11 11 11\n 12 12 12 12 12 12\n 13 13 13 13 13 13\n 14 14 14 14 14 14\n 15 15 15 15 15 15\n 16 16 16 16 16 16\n 17 17 17 17 17 17\n 18 18 18 18 18 18\n 19 19 19 19 19 19\n 20 60 60 60 20 60\n 21 61 61 61 21 61\n 22 50 50 50 22 50\n 23 38 38 38 23 38\n 24 24 24 24 24 24\n 25 25 25 25 25 25\n 26 63 63 63 26 63\n 27 39 39 39 27 39\n 28 28 28 28 28 28\n 29 29 29 29 29 29\n 30 30 30 30 30 30\n 31 31 31 31 31 31\n 32 64 64 64 32 64\n! 33 90 90 90 33 90\n\" 34 127 127 127 34 127\n# 35 123 123 123 35 123\n$ 36 91 91 91 36 91\n% 37 108 108 108 37 108\n& 38 80 80 80 38 80\n' 39 125 125 125 39 125\n( 40 77 77 77 40 77\n) 41 93 93 93 41 93\n* 42 92 92 92 42 92\n+ 43 78 78 78 43 78\n, 44 107 107 107 44 107\n- 45 96 96 96 45 96\n. 46 75 75 75 46 75\n/ 47 97 97 97 47 97\n0 48 240 240 240 48 240\n1 49 241 241 241 49 241\n2 50 242 242 242 50 242\n3 51 243 243 243 51 243\n4 52 244 244 244 52 244\n5 53 245 245 245 53 245\n6 54 246 246 246 54 246\n7 55 247 247 247 55 247\n8 56 248 248 248 56 248\n9 57 249 249 249 57 249\n: 58 122 122 122 58 122\n; 59 94 94 94 59 94\n< 60 76 76 76 60 76\n= 61 126 126 126 61 126\n> 62 110 110 110 62 110\n? 63 111 111 111 63 111\n@ 64 124 124 124 64 124\nA 65 193 193 193 65 193\nB 66 194 194 194 66 194\nC 67 195 195 195 67 195\nD 68 196 196 196 68 196\nE 69 197 197 197 69 197\nF 70 198 198 198 70 198\nG 71 199 199 199 71 199\nH 72 200 200 200 72 200\nI 73 201 201 201 73 201\nJ 74 209 209 209 74 209\nK 75 210 210 210 75 210\nL 76 211 211 211 76 211\nM 77 212 212 212 77 212\nN 78 213 213 213 78 213\nO 79 214 214 214 79 214\nP 80 215 215 215 80 215\nQ 81 216 216 216 81 216\nR 82 217 217 217 82 217\nS 83 226 226 226 83 226\nT 84 227 227 227 84 227\nU 85 228 228 228 85 228\nV 86 229 229 229 86 229\nW 87 230 230 230 87 230\nX 88 231 231 231 88 231\nY 89 232 232 232 89 232\nZ 90 233 233 233 90 233\n[ 91 186 173 187 91 173 ##\n\\ 92 224 224 188 92 224 ##\n] 93 187 189 189 93 189\n^ 94 176 95 106 94 95 ##\n95 109 109 109 95 109\n` 96 121 121 74 96 121 ##\na 97 129 129 129 97 129\nb 98 130 130 130 98 130\nc 99 131 131 131 99 131\nd 100 132 132 132 100 132\ne 101 133 133 133 101 133\nf 102 134 134 134 102 134\ng 103 135 135 135 103 135\nh 104 136 136 136 104 136\ni 105 137 137 137 105 137\nj 106 145 145 145 106 145\nk 107 146 146 146 107 146\nl 108 147 147 147 108 147\nm 109 148 148 148 109 148\nn 110 149 149 149 110 149\no 111 150 150 150 111 150\np 112 151 151 151 112 151\nq 113 152 152 152 113 152\nr 114 153 153 153 114 153\ns 115 162 162 162 115 162\nt 116 163 163 163 116 163\nu 117 164 164 164 117 164\nv 118 165 165 165 118 165\nw 119 166 166 166 119 166\nx 120 167 167 167 120 167\ny 121 168 168 168 121 168\nz 122 169 169 169 122 169\n{ 123 192 192 251 123 192 ##\n| 124 79 79 79 124 79\n} 125 208 208 253 125 208 ##\n~ 126 161 161 255 126 161 ##\n 127 7 7 7 127 7\n 128 32 32 32 194.128 32\n 129 33 33 33 194.129 33\n 130 34 34 34 194.130 34\n 131 35 35 35 194.131 35\n 132 36 36 36 194.132 36\n 133 21 37 37 194.133 37\n 134 6 6 6 194.134 6\n 135 23 23 23 194.135 23\n 136 40 40 40 194.136 40\n 137 41 41 41 194.137 41\n 138 42 42 42 194.138 42\n 139 43 43 43 194.139 43\n 140 44 44 44 194.140 44\n 141 9 9 9 194.141 9\n 142 10 10 10 194.142 10\n 143 27 27 27 194.143 27\n 144 48 48 48 194.144 48\n 145 49 49 49 194.145 49\n 146 26 26 26 194.146 26\n 147 51 51 51 194.147 51\n 148 52 52 52 194.148 52\n 149 53 53 53 194.149 53\n 150 54 54 54 194.150 54\n 151 8 8 8 194.151 8\n 152 56 56 56 194.152 56\n 153 57 57 57 194.153 57\n 154 58 58 58 194.154 58\n 155 59 59 59 194.155 59\n 156 4 4 4 194.156 4\n 157 20 20 20 194.157 20\n 158 62 62 62 194.158 62\n 159 255 255 95 194.159 255 ##\n 160 65 65 65 194.160 128.65\n 161 170 170 170 194.161 128.66\n 162 74 74 176 194.162 128.67 ##\n 163 177 177 177 194.163 128.68\n 164 159 159 159 194.164 128.69\n 165 178 178 178 194.165 128.70\n 166 106 106 208 194.166 128.71 ##\n
167 181 181 181 194.167 128.72\n 168 189 187 121 194.168 128.73 ##\n 169 180 180 180 194.169 128.74\n 170 154 154 154 194.170 128.81\n 171 138 138 138 194.171 128.82\n 172 95 176 186 194.172 128.83 ##\n 173 202 202 202 194.173 128.84\n 174 175 175 175 194.174 128.85\n 175 188 188 161 194.175 128.86 ##\n 176 144 144 144 194.176 128.87\n 177 143 143 143 194.177 128.88\n 178 234 234 234 194.178 128.89\n 179 250 250 250 194.179 128.98\n 180 190 190 190 194.180 128.99\n 181 160 160 160 194.181 128.100\n 182 182 182 182 194.182 128.101\n 183 179 179 179 194.183 128.102\n 184 157 157 157 194.184 128.103\n 185 218 218 218 194.185 128.104\n 186 155 155 155 194.186 128.105\n 187 139 139 139 194.187 128.106\n 188 183 183 183 194.188 128.112\n 189 184 184 184 194.189 128.113\n 190 185 185 185 194.190 128.114\n 191 171 171 171 194.191 128.115\n 192 100 100 100 195.128 138.65\n 193 101 101 101 195.129 138.66\n 194 98 98 98 195.130 138.67\n 195 102 102 102 195.131 138.68\n 196 99 99 99 195.132 138.69\n 197 103 103 103 195.133 138.70\n 198 158 158 158 195.134 138.71\n 199 104 104 104 195.135 138.72\n 200 116 116 116 195.136 138.73\n 201 113 113 113 195.137 138.74\n 202 114 114 114 195.138 138.81\n 203 115 115 115 195.139 138.82\n 204 120 120 120 195.140 138.83\n 205 117 117 117 195.141 138.84\n 206 118 118 118 195.142 138.85\n 207 119 119 119 195.143 138.86\n 208 172 172 172 195.144 138.87\n 209 105 105 105 195.145 138.88\n 210 237 237 237 195.146 138.89\n 211 238 238 238 195.147 138.98\n 212 235 235 235 195.148 138.99\n 213 239 239 239 195.149 138.100\n 214 236 236 236 195.150 138.101\n 215 191 191 191 195.151 138.102\n 216 128 128 128 195.152 138.103\n 217 253 253 224 195.153 138.104 ##\n 218 254 254 254 195.154 138.105\n 219 251 251 221 195.155 138.106 ##\n 220 252 252 252 195.156 138.112\n 221 173 186 173 195.157 138.113 ##\n 222 174 174 174 195.158 138.114\n 223 89 89 89 195.159 138.115\n 224 68 68 68 195.160 139.65\n 225 69 69 69 195.161 139.66\n 226 66 66 66 195.162 139.67\n 227 70 70 70 195.163 139.68\n 228 67 67 67 195.164 139.69\n 229 71 71 71 195.165 139.70\n 230 156 156 156 195.166 139.71\n 231 72 72 72 195.167 139.72\n 232 84 84 84 195.168 139.73\n 233 81 81 81 195.169 139.74\n 234 82 82 82 195.170 139.81\n 235 83 83 83 195.171 139.82\n 236 88 88 88 195.172 139.83\n 237 85 85 85 195.173 139.84\n 238 86 86 86 195.174 139.85\n 239 87 87 87 195.175 139.86\n 240 140 140 140 195.176 139.87\n 241 73 73 73 195.177 139.88\n 242 205 205 205 195.178 139.89\n 243 206 206 206 195.179 139.98\n 244 203 203 203 195.180 139.99\n 245 207 207 207 195.181 139.100\n 246 204 204 204 195.182 139.101\n 247 225 225 225 195.183 139.102\n 248 112 112 112 195.184 139.103\n 249 221 221 192 195.185 139.104 ##\n 250 222 222 222 195.186 139.105\n 251 219 219 219 195.187 139.106\n 252 220 220 220 195.188 139.112\n 253 141 141 141 195.189 139.113\n 254 142 142 142 195.190 139.114\n 255 223 223 223 195.191 139.115\n\nIf you would rather see the above table in CCSID 0037 order rather than ASCII + Latin-1 order\nthen run the table through:\n\nrecipe 4\n\nperl \\\n-ne 'if(/.{29}\\d{1,3}\\s{2,4}\\d{1,3}\\s{2,4}\\d{1,3}\\s{2,4}\\d{1,3}/)'\\\n-e '{push(@l,$)}' \\\n-e 'END{print map{$->[0]}' \\\n-e ' sort{$a->[1] <=> $b->[1]}' \\\n-e ' map{[$,substr($,34,3)]}@l;}' perlebcdic.pod\n\nIf you would rather see it in CCSID 1047 order then change the number 34 in the last line to 39,\nlike this:\n\nrecipe 5\n\nperl \\\n-ne 'if(/.{29}\\d{1,3}\\s{2,4}\\d{1,3}\\s{2,4}\\d{1,3}\\s{2,4}\\d{1,3}/)'\\\n-e '{push(@l,$)}' \\\n-e 'END{print map{$->[0]}' \\\n-e ' sort{$a->[1] <=> $b->[1]}' \\\n-e ' map{[$,substr($,39,3)]}@l;}' perlebcdic.pod\n\nIf you would rather see it in POSIX-BC order then change the number 34 in the last line to 44,\nlike this:\n\nrecipe 6\n\nperl \\\n-ne 'if(/.{29}\\d{1,3}\\s{2,4}\\d{1,3}\\s{2,4}\\d{1,3}\\s{2,4}\\d{1,3}/)'\\\n-e '{push(@l,$)}' \\\n-e 'END{print map{$->[0]}' \\\n-e ' sort{$a->[1] <=> $b->[1]}' \\\n-e ' map{[$,substr($,44,3)]}@l;}' perlebcdic.pod\n", "subsections": [ { "name": "Table in hex, sorted in 1047 order", "content": "Since this document was first written, the convention has become more and more to use\nhexadecimal notation for code points. To do this with the recipes and to also sort is a\nmulti-step process, so here, for convenience, is the table from above, re-sorted to be in Code\nPage 1047 order, and using hex notation.\n\nISO\n8859-1 POS- CCSID\nCCSID CCSID CCSID IX- 1047\nchr 0819 0037 1047 BC UTF-8 UTF-EBCDIC\n---------------------------------------------------------------------\n 00 00 00 00 00 00\n 01 01 01 01 01 01\n 02 02 02 02 02 02\n 03 03 03 03 03 03\n 9C 04 04 04 C2.9C 04\n 09 05 05 05 09 05\n 86 06 06 06 C2.86 06\n 7F 07 07 07 7F 07\n 97 08 08 08 C2.97 08\n 8D 09 09 09 C2.8D 09\n 8E 0A 0A 0A C2.8E 0A\n 0B 0B 0B 0B 0B 0B\n 0C 0C 0C 0C 0C 0C\n 0D 0D 0D 0D 0D 0D\n 0E 0E 0E 0E 0E 0E\n 0F 0F 0F 0F 0F 0F\n 10 10 10 10 10 10\n 11 11 11 11 11 11\n 12 12 12 12 12 12\n 13 13 13 13 13 13\n 9D 14 14 14 C2.9D 14\n 0A 25 15 15 0A 15\n 08 16 16 16 08 16\n 87 17 17 17 C2.87 17\n 18 18 18 18 18 18\n 19 19 19 19 19 19\n 92 1A 1A 1A C2.92 1A\n 8F 1B 1B 1B C2.8F 1B\n 1C 1C 1C 1C 1C 1C\n 1D 1D 1D 1D 1D 1D\n 1E 1E 1E 1E 1E 1E\n 1F 1F 1F 1F 1F 1F\n 80 20 20 20 C2.80 20\n 81 21 21 21 C2.81 21\n 82 22 22 22 C2.82 22\n 83 23 23 23 C2.83 23\n 84 24 24 24 C2.84 24\n 85 15 25 25 C2.85 25\n 17 26 26 26 17 26\n 1B 27 27 27 1B 27\n 88 28 28 28 C2.88 28\n 89 29 29 29 C2.89 29\n 8A 2A 2A 2A C2.8A 2A\n 8B 2B 2B 2B C2.8B 2B\n 8C 2C 2C 2C C2.8C 2C\n 05 2D 2D 2D 05 2D\n 06 2E 2E 2E 06 2E\n 07 2F 2F 2F 07 2F\n 90 30 30 30 C2.90 30\n 91 31 31 31 C2.91 31\n 16 32 32 32 16 32\n 93 33 33 33 C2.93 33\n 94 34 34 34 C2.94 34\n 95 35 35 35 C2.95 35\n 96 36 36 36 C2.96 36\n 04 37 37 37 04 37\n 98 38 38 38 C2.98 38\n 99 39 39 39 C2.99 39\n 9A 3A 3A 3A C2.9A 3A\n 9B 3B 3B 3B C2.9B 3B\n 14 3C 3C 3C 14 3C\n 15 3D 3D 3D 15 3D\n 9E 3E 3E 3E C2.9E 3E\n 1A 3F 3F 3F 1A 3F\n 20 40 40 40 20 40\n A0 41 41 41 C2.A0 80.41\n E2 42 42 42 C3.A2 8B.43\n E4 43 43 43 C3.A4 8B.45\n E0 44 44 44 C3.A0 8B.41\n E1 45 45 45 C3.A1 8B.42\n E3 46 46 46 C3.A3 8B.44\n E5 47 47 47 C3.A5 8B.46\n E7 48 48 48 C3.A7 8B.48\n F1 49 49 49 C3.B1 8B.58\n A2 4A 4A B0 C2.A2 80.43 ##\n. 2E 4B 4B 4B 2E 4B\n< 3C 4C 4C 4C 3C 4C\n( 28 4D 4D 4D 28 4D\n+ 2B 4E 4E 4E 2B 4E\n| 7C 4F 4F 4F 7C 4F\n& 26 50 50 50 26 50\n E9 51 51 51 C3.A9 8B.4A\n EA 52 52 52 C3.AA 8B.51\n EB 53 53 53 C3.AB 8B.52\n E8 54 54 54 C3.A8 8B.49\n ED 55 55 55 C3.AD 8B.54\n EE 56 56 56 C3.AE 8B.55\n EF 57 57 57 C3.AF 8B.56\n EC 58 58 58 C3.AC 8B.53\n DF 59 59 59 C3.9F 8A.73\n! 21 5A 5A 5A 21 5A\n$ 24 5B 5B 5B 24 5B\n* 2A 5C 5C 5C 2A 5C\n) 29 5D 5D 5D 29 5D\n; 3B 5E 5E 5E 3B 5E\n^ 5E B0 5F 6A 5E 5F ##\n- 2D 60 60 60 2D 60\n/ 2F 61 61 61 2F 61\n C2 62 62 62 C3.82 8A.43\n C4 63 63 63 C3.84 8A.45\n C0 64 64 64 C3.80 8A.41\n C1 65 65 65 C3.81 8A.42\n C3 66 66 66 C3.83 8A.44\n C5 67 67 67 C3.85 8A.46\n C7 68 68 68 C3.87 8A.48\n D1 69 69 69 C3.91 8A.58\n A6 6A 6A D0 C2.A6 80.47 ##\n, 2C 6B 6B 6B 2C 6B\n% 25 6C 6C 6C 25 6C\n5F 6D 6D 6D 5F 6D\n> 3E 6E 6E 6E 3E 6E\n? 3F 6F 6F 6F 3F 6F\n F8 70 70 70 C3.B8 8B.67\n C9 71 71 71 C3.89 8A.4A\n CA 72 72 72 C3.8A 8A.51\n CB 73 73 73 C3.8B 8A.52\n C8 74 74 74 C3.88 8A.49\n CD 75 75 75 C3.8D 8A.54\n CE 76 76 76 C3.8E 8A.55\n CF 77 77 77 C3.8F 8A.56\n CC 78 78 78 C3.8C 8A.53\n` 60 79 79 4A 60 79 ##\n: 3A 7A 7A 7A 3A 7A\n# 23 7B 7B 7B 23 7B\n@ 40 7C 7C 7C 40 7C\n' 27 7D 7D 7D 27 7D\n= 3D 7E 7E 7E 3D 7E\n\" 22 7F 7F 7F 22 7F\n D8 80 80 80 C3.98 8A.67\na 61 81 81 81 61 81\nb 62 82 82 82 62 82\nc 63 83 83 83 63 83\nd 64 84 84 84 64 84\ne 65 85 85 85 65 85\nf 66 86 86 86 66 86\ng 67 87 87 87 67 87\nh 68 88 88 88 68 88\ni 69 89 89 89 69 89\n AB 8A 8A 8A C2.AB 80.52\n BB 8B 8B 8B C2.BB 80.6A\n F0 8C 8C 8C C3.B0 8B.57\n FD 8D 8D 8D C3.BD 8B.71\n FE 8E 8E 8E C3.BE 8B.72\n B1 8F 8F 8F C2.B1 80.58\n B0 90 90 90 C2.B0 80.57\nj 6A 91 91 91 6A 91\nk 6B 92 92 92 6B 92\nl 6C 93 93 93 6C 93\nm 6D 94 94 94 6D 94\nn 6E 95 95 95 6E 95\no 6F 96 96 96 6F 96\np 70 97 97 97 70 97\nq 71 98 98 98 71 98\nr 72 99 99 99 72 99\n AA 9A 9A 9A C2.AA 80.51\n BA 9B 9B 9B C2.BA 80.69\n E6 9C 9C 9C C3.A6 8B.47\n B8 9D 9D 9D C2.B8 80.67\n C6 9E 9E 9E C3.86 8A.47\n A4 9F 9F 9F C2.A4 80.45\n B5 A0 A0 A0 C2.B5 80.64\n~ 7E A1 A1 FF 7E A1 ##\ns 73 A2 A2 A2 73 A2\nt 74 A3 A3 A3 74 A3\nu 75 A4 A4 A4 75 A4\nv 76 A5 A5 A5 76 A5\nw 77 A6 A6 A6 77 A6\nx 78 A7 A7 A7 78 A7\ny 79 A8 A8 A8 79 A8\nz 7A A9 A9 A9 7A A9\n A1 AA AA AA C2.A1 80.42\n BF AB AB AB C2.BF 80.73\n D0 AC AC AC C3.90 8A.57\n[ 5B BA AD BB 5B AD ##\n DE AE AE AE C3.9E 8A.72\n AE AF AF AF C2.AE 80.55\n AC 5F B0 BA C2.AC 80.53 ##\n A3 B1 B1 B1 C2.A3 80.44\n A5 B2 B2 B2 C2.A5 80.46\n B7 B3 B3 B3 C2.B7 80.66\n A9 B4 B4 B4 C2.A9 80.4A\n
A7 B5 B5 B5 C2.A7 80.48\n B6 B6 B6 B6 C2.B6 80.65\n BC B7 B7 B7 C2.BC 80.70\n BD B8 B8 B8 C2.BD 80.71\n BE B9 B9 B9 C2.BE 80.72\n DD AD BA AD C3.9D 8A.71 ##\n A8 BD BB 79 C2.A8 80.49 ##\n AF BC BC A1 C2.AF 80.56 ##\n] 5D BB BD BD 5D BD\n B4 BE BE BE C2.B4 80.63\n D7 BF BF BF C3.97 8A.66\n{ 7B C0 C0 FB 7B C0 ##\nA 41 C1 C1 C1 41 C1\nB 42 C2 C2 C2 42 C2\nC 43 C3 C3 C3 43 C3\nD 44 C4 C4 C4 44 C4\nE 45 C5 C5 C5 45 C5\nF 46 C6 C6 C6 46 C6\nG 47 C7 C7 C7 47 C7\nH 48 C8 C8 C8 48 C8\nI 49 C9 C9 C9 49 C9\n AD CA CA CA C2.AD 80.54\n F4 CB CB CB C3.B4 8B.63\n F6 CC CC CC C3.B6 8B.65\n F2 CD CD CD C3.B2 8B.59\n F3 CE CE CE C3.B3 8B.62\n F5 CF CF CF C3.B5 8B.64\n} 7D D0 D0 FD 7D D0 ##\nJ 4A D1 D1 D1 4A D1\nK 4B D2 D2 D2 4B D2\nL 4C D3 D3 D3 4C D3\nM 4D D4 D4 D4 4D D4\nN 4E D5 D5 D5 4E D5\nO 4F D6 D6 D6 4F D6\nP 50 D7 D7 D7 50 D7\nQ 51 D8 D8 D8 51 D8\nR 52 D9 D9 D9 52 D9\n B9 DA DA DA C2.B9 80.68\n FB DB DB DB C3.BB 8B.6A\n FC DC DC DC C3.BC 8B.70\n F9 DD DD C0 C3.B9 8B.68 ##\n FA DE DE DE C3.BA 8B.69\n FF DF DF DF C3.BF 8B.73\n\\ 5C E0 E0 BC 5C E0 ##\n F7 E1 E1 E1 C3.B7 8B.66\nS 53 E2 E2 E2 53 E2\nT 54 E3 E3 E3 54 E3\nU 55 E4 E4 E4 55 E4\nV 56 E5 E5 E5 56 E5\nW 57 E6 E6 E6 57 E6\nX 58 E7 E7 E7 58 E7\nY 59 E8 E8 E8 59 E8\nZ 5A E9 E9 E9 5A E9\n B2 EA EA EA C2.B2 80.59\n D4 EB EB EB C3.94 8A.63\n D6 EC EC EC C3.96 8A.65\n D2 ED ED ED C3.92 8A.59\n D3 EE EE EE C3.93 8A.62\n D5 EF EF EF C3.95 8A.64\n0 30 F0 F0 F0 30 F0\n1 31 F1 F1 F1 31 F1\n2 32 F2 F2 F2 32 F2\n3 33 F3 F3 F3 33 F3\n4 34 F4 F4 F4 34 F4\n5 35 F5 F5 F5 35 F5\n6 36 F6 F6 F6 36 F6\n7 37 F7 F7 F7 37 F7\n8 38 F8 F8 F8 38 F8\n9 39 F9 F9 F9 39 F9\n B3 FA FA FA C2.B3 80.62\n DB FB FB DD C3.9B 8A.6A ##\n DC FC FC FC C3.9C 8A.70\n D9 FD FD E0 C3.99 8A.68 ##\n DA FE FE FE C3.9A 8A.69\n 9F FF FF 5F C2.9F FF ##\n" } ] }, "IDENTIFYING CHARACTER CODE SETS": { "content": "It is possible to determine which character set you are operating under. But first you need to\nbe really really sure you need to do this. Your code will be simpler and probably just as\nportable if you don't have to test the character set and do different things, depending. There\nare actually only very few circumstances where it's not easy to write straight-line code\nportable to all character sets. See \"Unicode and EBCDIC\" in perluniintro for how to portably\nspecify characters.\n\nBut there are some cases where you may want to know which character set you are running under.\nOne possible example is doing sorting in inner loops where performance is critical.\n\nTo determine if you are running under ASCII or EBCDIC, you can use the return value of ord() or", "subsections": [ { "name": "chr", "content": "$isascii = \"A\" eq chr(65);\n$isebcdic = \"A\" eq chr(193);\n$isascii = ord(\"A\") == 65;\n$isebcdic = ord(\"A\") == 193;\n\nThere's even less need to distinguish between EBCDIC code pages, but to do so try looking at one\nor more of the characters that differ between them.\n\n$isascii = ord('[') == 91;\n$isebcdic37 = ord('[') == 186;\n$isebcdic1047 = ord('[') == 173;\n$isebcdicPOSIXBC = ord('[') == 187;\n\nHowever, it would be unwise to write tests such as:\n\n$isascii = \"\\r\" ne chr(13); # WRONG\n$isascii = \"\\n\" ne chr(10); # ILL ADVISED\n\nObviously the first of these will fail to distinguish most ASCII platforms from either a CCSID\n0037, a 1047, or a POSIX-BC EBCDIC platform since \"\"\\r\" eq chr(13)\" under all of those coded\ncharacter sets. But note too that because \"\\n\" is chr(13) and \"\\r\" is chr(10) on old Macintosh\n(which is an ASCII platform) the second $isascii test will lead to trouble there.\n\nTo determine whether or not perl was built under an EBCDIC code page you can use the Config\nmodule like so:\n\nuse Config;\n$isebcdic = $Config{'ebcdic'} eq 'define';\n" } ] }, "CONVERSIONS": { "content": "utf8::unicodetonative() and utf8::nativetounicode()\nThese functions take an input numeric code point in one encoding and return what its equivalent\nvalue is in the other.\n\nSee utf8.\n\ntr///\nIn order to convert a string of characters from one character set to another a simple list of\nnumbers, such as in the right columns in the above table, along with Perl's \"tr///\" operator is\nall that is needed. The data in the table are in ASCII/Latin1 order, hence the EBCDIC columns\nprovide easy-to-use ASCII/Latin1 to EBCDIC operations that are also easily reversed.\n\nFor example, to convert ASCII/Latin1 to code page 037 take the output of the second numbers\ncolumn from the output of recipe 2 (modified to add \"\\\" characters), and use it in \"tr///\" like\nso:\n\n$cp037 =\n'\\x00\\x01\\x02\\x03\\x37\\x2D\\x2E\\x2F\\x16\\x05\\x25\\x0B\\x0C\\x0D\\x0E\\x0F' .\n'\\x10\\x11\\x12\\x13\\x3C\\x3D\\x32\\x26\\x18\\x19\\x3F\\x27\\x1C\\x1D\\x1E\\x1F' .\n'\\x40\\x5A\\x7F\\x7B\\x5B\\x6C\\x50\\x7D\\x4D\\x5D\\x5C\\x4E\\x6B\\x60\\x4B\\x61' .\n'\\xF0\\xF1\\xF2\\xF3\\xF4\\xF5\\xF6\\xF7\\xF8\\xF9\\x7A\\x5E\\x4C\\x7E\\x6E\\x6F' .\n'\\x7C\\xC1\\xC2\\xC3\\xC4\\xC5\\xC6\\xC7\\xC8\\xC9\\xD1\\xD2\\xD3\\xD4\\xD5\\xD6' .\n'\\xD7\\xD8\\xD9\\xE2\\xE3\\xE4\\xE5\\xE6\\xE7\\xE8\\xE9\\xBA\\xE0\\xBB\\xB0\\x6D' .\n'\\x79\\x81\\x82\\x83\\x84\\x85\\x86\\x87\\x88\\x89\\x91\\x92\\x93\\x94\\x95\\x96' .\n'\\x97\\x98\\x99\\xA2\\xA3\\xA4\\xA5\\xA6\\xA7\\xA8\\xA9\\xC0\\x4F\\xD0\\xA1\\x07' .\n'\\x20\\x21\\x22\\x23\\x24\\x15\\x06\\x17\\x28\\x29\\x2A\\x2B\\x2C\\x09\\x0A\\x1B' .\n'\\x30\\x31\\x1A\\x33\\x34\\x35\\x36\\x08\\x38\\x39\\x3A\\x3B\\x04\\x14\\x3E\\xFF' .\n'\\x41\\xAA\\x4A\\xB1\\x9F\\xB2\\x6A\\xB5\\xBD\\xB4\\x9A\\x8A\\x5F\\xCA\\xAF\\xBC' .\n'\\x90\\x8F\\xEA\\xFA\\xBE\\xA0\\xB6\\xB3\\x9D\\xDA\\x9B\\x8B\\xB7\\xB8\\xB9\\xAB' .\n'\\x64\\x65\\x62\\x66\\x63\\x67\\x9E\\x68\\x74\\x71\\x72\\x73\\x78\\x75\\x76\\x77' .\n'\\xAC\\x69\\xED\\xEE\\xEB\\xEF\\xEC\\xBF\\x80\\xFD\\xFE\\xFB\\xFC\\xAD\\xAE\\x59' .\n'\\x44\\x45\\x42\\x46\\x43\\x47\\x9C\\x48\\x54\\x51\\x52\\x53\\x58\\x55\\x56\\x57' .\n'\\x8C\\x49\\xCD\\xCE\\xCB\\xCF\\xCC\\xE1\\x70\\xDD\\xDE\\xDB\\xDC\\x8D\\x8E\\xDF';\n\nmy $ebcdicstring = $asciistring;\neval '$ebcdicstring =~ tr/\\000-\\377/' . $cp037 . '/';\n\nTo convert from EBCDIC 037 to ASCII just reverse the order of the tr/// arguments like so:\n\nmy $asciistring = $ebcdicstring;\neval '$asciistring =~ tr/' . $cp037 . '/\\000-\\377/';\n\nSimilarly one could take the output of the third numbers column from recipe 2 to obtain a\n$cp1047 table. The fourth numbers column of the output from recipe 2 could provide a\n$cpposixbc table suitable for transcoding as well.\n\nIf you wanted to see the inverse tables, you would first have to sort on the desired numbers\ncolumn as in recipes 4, 5 or 6, then take the output of the first numbers column.\n\niconv\nXPG operability often implies the presence of an *iconv* utility available from the shell or\nfrom the C library. Consult your system's documentation for information on iconv.\n\nOn OS/390 or z/OS see the iconv(1) manpage. One way to invoke the \"iconv\" shell utility from\nwithin perl would be to:\n\n# OS/390 or z/OS example\n$asciidata = `echo '$ebcdicdata'| iconv -f IBM-1047 -t ISO8859-1`\n\nor the inverse map:\n\n# OS/390 or z/OS example\n$ebcdicdata = `echo '$asciidata'| iconv -f ISO8859-1 -t IBM-1047`\n\nFor other Perl-based conversion options see the \"Convert::*\" modules on CPAN.\n\nC RTL\nThe OS/390 and z/OS C run-time libraries provide atoe() and etoa() functions.\n", "subsections": [] }, "OPERATOR DIFFERENCES": { "content": "The \"..\" range operator treats certain character ranges with care on EBCDIC platforms. For\nexample the following array will have twenty six elements on either an EBCDIC platform or an\nASCII platform:\n\n@alphabet = ('A'..'Z'); # $#alphabet == 25\n\nThe bitwise operators such as & ^ | may return different results when operating on string or\ncharacter data in a Perl program running on an EBCDIC platform than when run on an ASCII\nplatform. Here is an example adapted from the one in perlop:\n\n# EBCDIC-based examples\nprint \"j p \\n\" ^ \" a h\"; # prints \"JAPH\\n\"\nprint \"JA\" | \" ph\\n\"; # prints \"japh\\n\"\nprint \"JAPH\\nJunk\" & \"\\277\\277\\277\\277\\277\"; # prints \"japh\\n\";\nprint 'p N$' ^ \" E \"(chr(1)\" eq\n\"\\cA\")>, and so on. Perl on EBCDIC platforms has been ported to take \"\\c@\" to chr(0) and \"\\cA\"\nto chr(1), etc. as well, but the characters that result depend on which code page you are using.\nThe table below uses the standard acronyms for the controls. The POSIX-BC and 1047 sets are\nidentical throughout this range and differ from the 0037 set at only one spot (21 decimal). Note\nthat the line terminator character may be generated by \"\\cJ\" on ASCII platforms but by \"\\cU\" on\n1047 or POSIX-BC platforms and cannot be generated as a \"\\c.letter.\" control character on 0037\nplatforms. Note also that \"\\c\\\" cannot be the final element in a string or regex, as it will\nabsorb the terminator. But \"\\c\\*X*\" is a \"FILE SEPARATOR\" concatenated with *X* for all *X*. The\noutlier \"\\c?\" on ASCII, which yields a non-C0 control \"DEL\", yields the outlier control \"APC\" on\nEBCDIC, the one that isn't in the block of contiguous controls. Note that a subtlety of this is\nthat \"\\c?\" on ASCII platforms is an ASCII character, while it isn't equivalent to any ASCII\ncharacter in EBCDIC platforms.\n\nchr ord 8859-1 0037 1047 && POSIX-BC\n-----------------------------------------------------------------------\n\\c@ 0 \n\\cA 1 \n\\cB 2 \n\\cC 3 \n\\cD 4 \n\\cE 5 \n\\cF 6 \n\\cG 7 \n\\cH 8 \n\\cI 9 \n\\cJ 10 \n\\cK 11 \n\\cL 12 \n\\cM 13 \n\\cN 14 \n\\cO 15 \n\\cP 16 \n\\cQ 17 \n\\cR 18 \n\\cS 19 \n\\cT 20 \n\\cU 21 \n\\cV 22 \n\\cW 23 \n\\cX 24 \n\\cY 25 \n\\cZ 26 \n\\c[ 27 \n\\c\\X 28 X X X\n\\c] 29 \n\\c^ 30 \n\\c 31 \n\\c? * \n\n\"*\" Note: \"\\c?\" maps to ordinal 127 (\"DEL\") on ASCII platforms, but since ordinal 127 is a not a\ncontrol character on EBCDIC machines, \"\\c?\" instead maps on them to \"APC\", which is 255 in 0037\nand 1047, and 95 in POSIX-BC.\n", "subsections": [] }, "FUNCTION DIFFERENCES": { "content": "", "subsections": [ { "name": "chr", "content": "value on an EBCDIC platform. For example:\n\n$CAPITALLETTERA = chr(193);\n" }, { "name": "ord", "content": "$thenumber193 = ord(\"A\");\n" }, { "name": "pack", "content": "of usage on EBCDIC include:\n\n$foo = pack(\"CCCC\",193,194,195,196);\n# $foo eq \"ABCD\"\n$foo = pack(\"C4\",193,194,195,196);\n# same thing\n\n$foo = pack(\"ccxxcc\",193,194,195,196);\n# $foo eq \"AB\\0\\0CD\"\n\nThe \"U\" template has been ported to mean \"Unicode\" on all platforms so that\n\npack(\"U\", 65) eq 'A'\n\nis true on all platforms. If you want native code points for the low 256, use the \"W\"\ntemplate. This means that the equivalences\n\npack(\"W\", ord($character)) eq $character\nunpack(\"W\", $character) == ord $character\n\nwill hold.\n\nprint() One must be careful with scalars and strings that are passed to print that contain ASCII\nencodings. One common place for this to occur is in the output of the MIME type header\nfor CGI script writing. For example, many Perl programming guides recommend something\nsimilar to:\n\nprint \"Content-type:\\ttext/html\\015\\012\\015\\012\";\n# this may be wrong on EBCDIC\n\nYou can instead write\n\nprint \"Content-type:\\ttext/html\\r\\n\\r\\n\"; # OK for DGW et al\n\nand have it work portably.\n\nThat is because the translation from EBCDIC to ASCII is done by the web server in this\ncase. Consult your web server's documentation for further details.\n" }, { "name": "printf", "content": "The formats that can convert characters to numbers and vice versa will be different from\ntheir ASCII counterparts when executed on an EBCDIC platform. Examples include:\n\nprintf(\"%c%c%c\",193,194,195); # prints ABC\n" }, { "name": "sort", "content": "strings. This is discussed in more detail below.\n" }, { "name": "sprintf", "content": "See the discussion of \"printf()\" above. An example of the use of sprintf would be:\n\n$CAPITALLETTERA = sprintf(\"%c\",193);\n" }, { "name": "unpack", "content": "See the discussion of \"pack()\" above.\n\nNote that it is possible to write portable code for these by specifying things in Unicode\nnumbers, and using a conversion function:\n\nprintf(\"%c\",utf8::unicodetonative(65)); # prints A on all\n# platforms\nprint utf8::nativetounicode(ord(\"A\")); # Likewise, prints 65\n\nSee \"Unicode and EBCDIC\" in perluniintro and \"CONVERSIONS\" for other options.\n" } ] }, "REGULAR EXPRESSION DIFFERENCES": { "content": "You can write your regular expressions just like someone on an ASCII platform would do. But keep\nin mind that using octal or hex notation to specify a particular code point will give you the\ncharacter that the EBCDIC code page natively maps to it. (This is also true of all double-quoted\nstrings.) If you want to write portably, just use the \"\\N{U+...}\" notation everywhere where you\nwould have used \"\\x{...}\", and don't use octal notation at all.\n\nStarting in Perl v5.22, this applies to ranges in bracketed character classes. If you say, for\nexample, \"qr/[\\N{U+20}-\\N{U+7F}]/\", it means the characters \"\\N{U+20}\", \"\\N{U+21}\", ...,\n\"\\N{U+7F}\". This range is all the printable characters that the ASCII character set contains.\n\nPrior to v5.22, you couldn't specify any ranges portably, except (starting in Perl v5.5.3) all\nsubsets of the \"[A-Z]\" and \"[a-z]\" ranges are specially coded to not pick up gap characters. For\nexample, characters such as \"ô\" (\"o WITH CIRCUMFLEX\") that lie between \"I\" and \"J\" would not be\nmatched by the regular expression range \"/[H-K]/\". But if either of the range end points is\nexplicitly numeric (and neither is specified by \"\\N{U+...}\"), the gap characters are matched:\n\n/[\\x89-\\x91]/\n\nwill match \"\\x8e\", even though \"\\x89\" is \"i\" and \"\\x91 \" is \"j\", and \"\\x8e\" is a gap character,\nfrom the alphabetic viewpoint.\n\nAnother construct to be wary of is the inappropriate use of hex (unless you use \"\\N{U+...}\") or\noctal constants in regular expressions. Consider the following set of subs:\n\nsub isc0 {\nmy $char = substr(shift,0,1);\n$char =~ /[\\000-\\037]/;\n}\n\nsub isprintascii {\nmy $char = substr(shift,0,1);\n$char =~ /[\\040-\\176]/;\n}\n\nsub isdelete {\nmy $char = substr(shift,0,1);\n$char eq \"\\177\";\n}\n\nsub isc1 {\nmy $char = substr(shift,0,1);\n$char =~ /[\\200-\\237]/;\n}\n\nsub islatin1 { # But not ASCII; not C1\nmy $char = substr(shift,0,1);\n$char =~ /[\\240-\\377]/;\n}\n\nThese are valid only on ASCII platforms. Starting in Perl v5.22, simply changing the octal\nconstants to equivalent \"\\N{U+...}\" values makes them portable:\n\nsub isc0 {\nmy $char = substr(shift,0,1);\n$char =~ /[\\N{U+00}-\\N{U+1F}]/;\n}\n\nsub isprintascii {\nmy $char = substr(shift,0,1);\n$char =~ /[\\N{U+20}-\\N{U+7E}]/;\n}\n\nsub isdelete {\nmy $char = substr(shift,0,1);\n$char eq \"\\N{U+7F}\";\n}\n\nsub isc1 {\nmy $char = substr(shift,0,1);\n$char =~ /[\\N{U+80}-\\N{U+9F}]/;\n}\n\nsub islatin1 { # But not ASCII; not C1\nmy $char = substr(shift,0,1);\n$char =~ /[\\N{U+A0}-\\N{U+FF}]/;\n}\n\nAnd here are some alternative portable ways to write them:\n\nsub Isc0 {\nmy $char = substr(shift,0,1);\nreturn $char =~ /[[:cntrl:]]/a && ! Isdelete($char);\n\n# Alternatively:\n# return $char =~ /[[:cntrl:]]/\n# && $char =~ /[[:ascii:]]/\n# && ! Isdelete($char);\n}\n\nsub Isprintascii {\nmy $char = substr(shift,0,1);\n\nreturn $char =~ /[[:print:]]/a;\n\n# Alternatively:\n# return $char =~ /[[:print:]]/ && $char =~ /[[:ascii:]]/;\n\n# Or\n# return $char\n# =~ /[ !\"\\#\\$%&'()*+,\\-.\\/0-9:;<=>?\\@A-Z[\\\\\\]^`a-z{|}~]/;\n}\n\nsub Isdelete {\nmy $char = substr(shift,0,1);\nreturn utf8::nativetounicode(ord $char) == 0x7F;\n}\n\nsub Isc1 {\nuse feature 'unicodestrings';\nmy $char = substr(shift,0,1);\nreturn $char =~ /[[:cntrl:]]/ && $char !~ /[[:ascii:]]/;\n}\n\nsub Islatin1 { # But not ASCII; not C1\nuse feature 'unicodestrings';\nmy $char = substr(shift,0,1);\nreturn ord($char) < 256\n&& $char !~ /[[:ascii:]]/\n&& $char !~ /[[:cntrl:]]/;\n}\n\nAnother way to write Islatin1() would be to use the characters in the range explicitly:\n\nsub Islatin1 {\nmy $char = substr(shift,0,1);\n$char =~ /[ ¡¢£¤¥¦§¨©ª«¬®¯°±²³´µ¶·¸¹º»¼½¾¿ÀÁÂÃÄÅÆÇÈÉÊËÌÍÎÏ]\n[ÐÑÒÓÔÕÖ×ØÙÚÛÜÝÞßàáâãäåæçèéêëìíîïðñòóôõö÷øùúûüýþÿ]/x;\n}\n\nAlthough that form may run into trouble in network transit (due to the presence of 8 bit\ncharacters) or on non ISO-Latin character sets. But it does allow \"Isc1\" to be rewritten so it\nworks on Perls that don't have 'unicodestrings' (earlier than v5.14):\n\nsub Islatin1 { # But not ASCII; not C1\nmy $char = substr(shift,0,1);\nreturn ord($char) < 256\n&& $char !~ /[[:ascii:]]/\n&& ! Islatin1($char);\n}\n", "subsections": [] }, "SOCKETS": { "content": "Most socket programming assumes ASCII character encodings in network byte order. Exceptions can\ninclude CGI script writing under a host web server where the server may take care of translation\nfor you. Most host web servers convert EBCDIC data to ISO-8859-1 or Unicode on output.\n", "subsections": [] }, "SORTING": { "content": "One big difference between ASCII-based character sets and EBCDIC ones are the relative positions\nof the characters when sorted in native order. Of most concern are the upper- and lowercase\nletters, the digits, and the underscore (\"\"). On ASCII platforms the native sort order has the\ndigits come before the uppercase letters which come before the underscore which comes before the\nlowercase letters. On EBCDIC, the underscore comes first, then the lowercase letters, then the\nuppercase ones, and the digits last. If sorted on an ASCII-based platform, the two-letter\nabbreviation for a physician comes before the two letter abbreviation for drive; that is:\n\n@sorted = sort(qw(Dr. dr.)); # @sorted holds ('Dr.','dr.') on ASCII,\n# but ('dr.','Dr.') on EBCDIC\n\nThe property of lowercase before uppercase letters in EBCDIC is even carried to the Latin 1\nEBCDIC pages such as 0037 and 1047. An example would be that \"Ë\" (\"E WITH DIAERESIS\", 203) comes\nbefore \"ë\" (\"e WITH DIAERESIS\", 235) on an ASCII platform, but the latter (83) comes before the\nformer (115) on an EBCDIC platform. (Astute readers will note that the uppercase version of \"ß\"\n\"SMALL LETTER SHARP S\" is simply \"SS\" and that the upper case versions of \"ÿ\" (small \"y WITH\nDIAERESIS\") and \"µ\" (\"MICRO SIGN\") are not in the 0..255 range but are in Unicode, in a Unicode\nenabled Perl).\n\nThe sort order will cause differences between results obtained on ASCII platforms versus EBCDIC\nplatforms. What follows are some suggestions on how to deal with these differences.\n", "subsections": [ { "name": "Ignore ASCII vs. EBCDIC sort differences.", "content": "This is the least computationally expensive strategy. It may require some user education.\n" }, { "name": "Use a sort helper function", "content": "This is completely general, but the most computationally expensive strategy. Choose one or the\nother character set and transform to that for every sort comparison. Here's a complete example\nthat transforms to ASCII sort order:\n\nsub nativetouni($) {\nmy $string = shift;\n\n# Saves time on an ASCII platform\nreturn $string if ord 'A' == 65;\n\nmy $output = \"\";\nfor my $i (0 .. length($string) - 1) {\n$output\n.= chr(utf8::nativetounicode(ord(substr($string, $i, 1))));\n}\n\n# Preserve utf8ness of input onto the output, even if it didn't need\n# to be utf8\nutf8::upgrade($output) if utf8::isutf8($string);\n\nreturn $output;\n}\n\nsub asciiorder { # Sort helper\nreturn nativetouni($a) cmp nativetouni($b);\n}\n\nsort asciiorder @list;\n\nMONO CASE then sort data (for non-digits, non-underscore)\nIf you don't care about where digits and underscore sort to, you can do something like this\n\nsub caseinsensitiveorder { # Sort helper\nreturn lc($a) cmp lc($b)\n}\n\nsort caseinsensitiveorder @list;\n\nIf performance is an issue, and you don't care if the output is in the same case as the input,\nUse \"tr///\" to transform to the case most employed within the data. If the data are primarily\nUPPERCASE non-Latin1, then apply \"tr/[a-z]/[A-Z]/\", and then sort(). If the data are primarily\nlowercase non Latin1 then apply \"tr/[A-Z]/[a-z]/\" before sorting. If the data are primarily\nUPPERCASE and include Latin-1 characters then apply:\n\ntr/[a-z]/[A-Z]/;\ntr/[àáâãäåæçèéêëìíîïðñòóôõöøùúûüýþ]/[ÀÁÂÃÄÅÆÇÈÉÊËÌÍÎÏÐÑÒÓÔÕÖØÙÚÛÜÝÞ/;\ns/ß/SS/g;\n\nthen sort(). If you have a choice, it's better to lowercase things to avoid the problems of the\ntwo Latin-1 characters whose uppercase is outside Latin-1: \"ÿ\" (small \"y WITH DIAERESIS\") and\n\"µ\" (\"MICRO SIGN\"). If you do need to upppercase, you can; with a Unicode-enabled Perl, do:\n\ntr/ÿ/\\x{178}/;\ntr/µ/\\x{39C}/;\n" }, { "name": "Perform sorting on one type of platform only.", "content": "This strategy can employ a network connection. As such it would be computationally expensive.\n" } ] }, "TRANSFORMATION FORMATS": { "content": "There are a variety of ways of transforming data with an intra character set mapping that serve\na variety of purposes. Sorting was discussed in the previous section and a few of the other more\npopular mapping techniques are discussed next.\n\nURL decoding and encoding\nNote that some URLs have hexadecimal ASCII code points in them in an attempt to overcome\ncharacter or protocol limitation issues. For example the tilde character is not on every\nkeyboard hence a URL of the form:\n\nhttp://www.pvhp.com/~pvhp/\n\nmay also be expressed as either of:\n\nhttp://www.pvhp.com/%7Epvhp/\n\nhttp://www.pvhp.com/%7epvhp/\n\nwhere 7E is the hexadecimal ASCII code point for \"~\". Here is an example of decoding such a URL\nin any EBCDIC code page:\n\n$url = 'http://www.pvhp.com/%7Epvhp/';\n$url =~ s/%([0-9a-fA-F]{2})/\npack(\"c\",utf8::unicodetonative(hex($1)))/xge;\n\nConversely, here is a partial solution for the task of encoding such a URL in any EBCDIC code\npage:\n\n$url = 'http://www.pvhp.com/~pvhp/';\n# The following regular expression does not address the\n# mappings for: ('.' => '%2E', '/' => '%2F', ':' => '%3A')\n$url =~ s/([\\t \"#%&\\(\\),;<=>\\?\\@\\[\\\\\\]^`{|}~])/\nsprintf(\"%%%02X\",utf8::nativetounicode(ord($1)))/xge;\n\nwhere a more complete solution would split the URL into components and apply a full s///\nsubstitution only to the appropriate parts.\n\nuu encoding and decoding\nThe \"u\" template to pack() or unpack() will render EBCDIC data in EBCDIC characters equivalent\nto their ASCII counterparts. For example, the following will print \"Yes indeed\\n\" on either an\nASCII or EBCDIC computer:\n\n$allbytechrs = '';\nfor (0..255) { $allbytechrs .= chr($); }\n$uuencodebytechrs = pack('u', $allbytechrs);\n($uu = <<'ENDOFHEREDOC') =~ s/^\\s*//gm;\nM``$\"`P0%!@<(\"0H+#`T.#Q`1$A,4%187&!D:&QP='A\\@(2(C)\"4F)R@I*BLL\nM+2XO,#$R,S0U-C'EZ>WQ]?G^`@8*#A(6&\nMAXB)BHN,C8Z/D)&2DY25EI>8F9J;G)V>GZ\"AHJ.DI::GJ*FJJZRMKJ^PL;*S\nMM+6VM[BYNKN\\O;ZP,'\"P\\3%QL?(R+CY.7FY^CIZNOL[>[O\\/'R\\3U]O?X^?K[/W^P``\nENDOFHEREDOC\nif ($uuencodebytechrs eq $uu) {\nprint \"Yes \";\n}\n$uudecodebytechrs = unpack('u', $uuencodebytechrs);\nif ($uudecodebytechrs eq $allbytechrs) {\nprint \"indeed\\n\";\n}\n\nHere is a very spartan uudecoder that will work on EBCDIC:\n\n#!/usr/local/bin/perl\n$ = <> until ($mode,$file) = /^begin\\s*(\\d*)\\s*(\\S*)/;\nopen(OUT, \"> $file\") if $file ne \"\";\nwhile(<>) {\nlast if /^end/;\nnext if /[a-z]/;\nnext unless int((((utf8::nativetounicode(ord()) - 32 ) & 077)\n+ 2) / 3)\n== int(length() / 4);\nprint OUT unpack(\"u\", $);\n}\nclose(OUT);\nchmod oct($mode), $file;\n", "subsections": [ { "name": "Quoted-Printable encoding and decoding", "content": "On ASCII-encoded platforms it is possible to strip characters outside of the printable set\nusing:\n\n# This QP encoder works on ASCII only\n$qpstring =~ s/([=\\x00-\\x1F\\x80-\\xFF])/\nsprintf(\"=%02X\",ord($1))/xge;\n\nStarting in Perl v5.22, this is trivially changeable to work portably on both ASCII and EBCDIC\nplatforms.\n\n# This QP encoder works on both ASCII and EBCDIC\n$qpstring =~ s/([=\\N{U+00}-\\N{U+1F}\\N{U+80}-\\N{U+FF}])/\nsprintf(\"=%02X\",ord($1))/xge;\n\nFor earlier Perls, a QP encoder that works on both ASCII and EBCDIC platforms would look\nsomewhat like the following:\n\n$delete = utf8::unicodetonative(ord(\"\\x7F\"));\n$qpstring =~\ns/([^[:print:]$delete])/\nsprintf(\"=%02X\",utf8::nativetounicode(ord($1)))/xage;\n\n(although in production code the substitutions might be done in the EBCDIC branch with the\nfunction call and separately in the ASCII branch without the expense of the identity map; in\nPerl v5.22, the identity map is optimized out so there is no expense, but the alternative above\nis simpler and is also available in v5.22).\n\nSuch QP strings can be decoded with:\n\n# This QP decoder is limited to ASCII only\n$string =~ s/=([[:xdigit:][[:xdigit:])/chr hex $1/ge;\n$string =~ s/=[\\n\\r]+$//;\n\nWhereas a QP decoder that works on both ASCII and EBCDIC platforms would look somewhat like the\nfollowing:\n\n$string =~ s/=([[:xdigit:][:xdigit:]])/\nchr utf8::nativetounicode(hex $1)/xge;\n$string =~ s/=[\\n\\r]+$//;\n" }, { "name": "Caesarean ciphers", "content": "The practice of shifting an alphabet one or more characters for encipherment dates back\nthousands of years and was explicitly detailed by Gaius Julius Caesar in his Gallic Wars text. A\nsingle alphabet shift is sometimes referred to as a rotation and the shift amount is given as a\nnumber $n after the string 'rot' or \"rot$n\". Rot0 and rot26 would designate identity maps on the\n26-letter English version of the Latin alphabet. Rot13 has the interesting property that\nalternate subsequent invocations are identity maps (thus rot13 is its own non-trivial inverse in\nthe group of 26 alphabet rotations). Hence the following is a rot13 encoder and decoder that\nwill work on ASCII and EBCDIC platforms:\n\n#!/usr/local/bin/perl\n\nwhile(<>){\ntr/n-za-mN-ZA-M/a-zA-Z/;\nprint;\n}\n\nIn one-liner form:\n\nperl -ne 'tr/n-za-mN-ZA-M/a-zA-Z/;print'\n" } ] }, "Hashing order and checksums": { "content": "Perl deliberately randomizes hash order for security purposes on both ASCII and EBCDIC\nplatforms.\n\nEBCDIC checksums will differ for the same file translated into ASCII and vice versa.\n", "subsections": [] }, "I18N AND L10N": { "content": "Internationalization (I18N) and localization (L10N) are supported at least in principle even on\nEBCDIC platforms. The details are system-dependent and discussed under the \"OS ISSUES\" section\nbelow.\n", "subsections": [] }, "MULTI-OCTET CHARACTER SETS": { "content": "Perl works with UTF-EBCDIC, a multi-byte encoding. In Perls earlier than v5.22, there may be\nvarious bugs in this regard.\n\nLegacy multi byte EBCDIC code pages XXX.\n", "subsections": [] }, "OS ISSUES": { "content": "There may be a few system-dependent issues of concern to EBCDIC Perl programmers.\n\nOS/400\nPASE The PASE environment is a runtime environment for OS/400 that can run executables built\nfor PowerPC AIX in OS/400; see perlos400. PASE is ASCII-based, not EBCDIC-based as the\nILE.\n\nIFS access\nXXX.\n\nOS/390, z/OS\nPerl runs under Unix Systems Services or USS.\n\n\"sigaction\"\n\"SASIGINFO\" can have segmentation faults.\n\n\"chcp\" chcp is supported as a shell utility for displaying and changing one's code page. See\nalso chcp(1).\n\ndataset access\nFor sequential data set access try:\n\nmy @dsrecords = `cat //DSNAME`;\n\nor:\n\nmy @dsrecords = `cat //'HLQ.DSNAME'`;\n\nSee also the OS390::Stdio module on CPAN.\n\n\"iconv\" iconv is supported as both a shell utility and a C RTL routine. See also the iconv(1)\nand iconv(3) manual pages.\n\nlocales Locales are supported. There may be glitches when a locale is another EBCDIC code page\nwhich has some of the code-page variant characters in other positions.\n\nThere aren't currently any real UTF-8 locales, even though some locale names contain the\nstring \"UTF-8\".\n\nSee perllocale for information on locales. The L10N files are in /usr/nls/locale.\n$Config{dsetlocale} is 'define' on OS/390 or z/OS.\n\nPOSIX-BC?\nXXX.\n", "subsections": [] }, "BUGS": { "content": "* Not all shells will allow multiple \"-e\" string arguments to perl to be concatenated together\nproperly as recipes in this document 0, 2, 4, 5, and 6 might seem to imply.\n\n* There are a significant number of test failures in the CPAN modules shipped with Perl v5.22\nand 5.24. These are only in modules not primarily maintained by Perl 5 porters. Some of\nthese are failures in the tests only: they don't realize that it is proper to get different\nresults on EBCDIC platforms. And some of the failures are real bugs. If you compile and do a\n\"make test\" on Perl, all tests on the \"/cpan\" directory are skipped.\n\nEncode partially works.\n\n* In earlier Perl versions, when byte and character data were concatenated, the new string was\nsometimes created by decoding the byte strings as *ISO 8859-1 (Latin-1)*, even if the old\nUnicode string used EBCDIC.\n", "subsections": [] }, "SEE ALSO": { "content": "perllocale, perlfunc, perlunicode, utf8.\n", "subsections": [] }, "REFERENCES": { "content": "\n\n\n\n\n\n ASCII: American Standard Code for\nInformation Infiltration Tom Jennings, September 1999.\n\nThe Unicode Standard, Version 3.0 The Unicode Consortium, Lisa Moore ed., ISBN 0-201-61633-5,\nAddison Wesley Developers Press, February 2000.\n\nCDRA: IBM - Character Data Representation Architecture - Reference and Registry, IBM\nSC09-2190-00, December 1996.\n\n\"Demystifying Character Sets\", Andrea Vine, Multilingual Computing & Technology, #26 Vol. 10\nIssue 4, August/September 1999; ISSN 1523-0309; Multilingual Computing Inc. Sandpoint ID, USA.\n\nCodes, Ciphers, and Other Cryptic and Clandestine Communication Fred B. Wrixon, ISBN\n1-57912-040-7, Black Dog & Leventhal Publishers, 1998.\n\n IBM - EBCDIC and the P-bit; The biggest Computer Goof Ever\nRobert Bemer.\n", "subsections": [] }, "HISTORY": { "content": "15 April 2001: added UTF-8 and UTF-EBCDIC to main table, pvhp.\n", "subsections": [] }, "AUTHOR": { "content": "Peter Prymmer pvhp@best.com wrote this in 1999 and 2000 with CCSID 0819 and 0037 help from Chris\nLeach and André Pirard A.Pirard@ulg.ac.be as well as POSIX-BC help from Thomas Dorner\nThomas.Dorner@start.de. Thanks also to Vickie Cooper, Philip Newton, William Raffloer, and Joe\nSmith. Trademarks, registered trademarks, service marks and registered service marks used in\nthis document are the property of their respective owners.\n\nNow maintained by Perl5 Porters.\n", "subsections": [] } } } }