Lines Matching defs:ASCII
25 on an L</ASCII> one, but with different underlying numbers, as we'll see
26 shortly. You'll have to know something about those L</ASCII> platforms
29 modules that are written for EBCDIC and which don't work on ASCII;
30 instead the vast majority of CPAN modules are written for ASCII, and
38 work on an ASCII machine without change.
43 ASCII one. That's fine to do if no one will ever want to run your code
44 on an ASCII platform; but the bias in this document will be towards writing
45 code portable between EBCDIC and ASCII systems. Again, if every
47 don't have to know anything about ASCII, but many keyboards don't easily
50 In those cases it's easiest to know something about the ASCII/Unicode
54 C<\xFF> on ASCII ones. Or you could specify it by name, C<\N{LATIN
60 =head2 ASCII
62 The American Standard Code for Information Interchange (ASCII or
63 US-ASCII) is a set of
65 interpretations by the computers which use ASCII. For example, 65 means
68 digit, hence the set is sometimes referred to as "7-bit ASCII".
69 ASCII was described by the American National Standards Institute
71 (with localization for currency symbols). The full ASCII set is
74 can be written adequately with the characters in ASCII include
78 Most non-EBCDIC character sets are supersets of ASCII. That is the
79 integers 0-127 mean what ASCII says they mean. But integers 128 and
82 Many of these fit entirely into 8 bits, using ASCII as 0-127, while
92 characters to the ASCII set that are typically found in various
100 A particular 8-bit extension to ASCII that includes grave and acute
102 include all the languages covered by ASCII as well as Afrikaans,
108 to ASCII and is commonly encountered in world wide web work.
116 quite different from ASCII and ISO 8859-1, and are all slightly
119 card encodings, which long predate ASCII. The layout on the
155 Character code set ID 0037 is a mapping of the ASCII plus Latin-1
163 Character code set ID 1047 is also a mapping of the ASCII plus
183 All the code points in ASCII and Latin-1 (ISO 8859-1) have the same
191 ASCII/Latin1 C0 controls and the DELETE control. (The C0 controls are
192 those whose ASCII code points are 0..0x1F; things like TAB, ACK, BEL,
193 etc.) A mapping is set up between these ASCII/EBCDIC controls. There
194 isn't such a precise mapping between the C1 controls on ASCII platforms
204 CR (0x0D), LF (0x25), and NL (0x15). On ASCII platforms, the symbols
220 ASCII and Latin-1.
226 terms, and use "UTF-8" to mean both the UTF-8 found on ASCII platforms,
243 In ASCII UTF-8, the code points corresponding to the lowest 128
244 ordinal numbers (0 - 127: the ASCII characters) are invariant.
247 which have ASCII equivalents, plus those that correspond to
248 the C1 controls (128 - 159 on ASCII platforms).)
321 to get four files containing "Hello World!\n" in ASCII, CP 0037 EBCDIC,
322 ISO 8859-1 (Latin-1) (in this example identical to ASCII since only ASCII
329 ignores things like the type of your filesystem (ASCII or EBCDIC).
333 The following tables list the ASCII and Latin 1 ordered sets including
334 the subsets: C0 controls (0..31), ASCII graphics (32..7e), delete (7f),
337 extensions to ASCII have been labelled with character names roughly
696 ASCII + Latin-1 order then run the table through:
1028 To determine if you are running under ASCII or EBCDIC, you can use the
1051 Obviously the first of these will fail to distinguish most ASCII
1055 C<chr(10)> on old Macintosh (which is an ASCII platform) the second
1078 The data in the table are in ASCII/Latin1 order, hence the EBCDIC columns
1079 provide easy-to-use ASCII/Latin1 to EBCDIC operations that are also easily
1082 For example, to convert ASCII/Latin1 to code page 037 take the output of the
1107 To convert from EBCDIC 037 to ASCII just reverse the order of the tr///
1150 or an ASCII platform:
1156 on an EBCDIC platform than when run on an ASCII platform. Here is
1166 in the ASCII table is that they can "literally" be constructed
1175 may be generated by C<\cJ> on ASCII platforms but by C<\cU> on 1047 or POSIX-BC
1180 The outlier C<\c?> on ASCII, which yields a non-C0 control C<DEL>,
1183 C<\c?> on ASCII platforms is an ASCII character, while it isn't
1184 equivalent to any ASCII character in EBCDIC platforms.
1222 C<*> Note: C<\c?> maps to ordinal 127 (C<DEL>) on ASCII platforms, but
1275 print that contain ASCII encodings. One common place
1289 That is because the translation from EBCDIC to ASCII is done
1296 will be different from their ASCII counterparts when executed
1303 EBCDIC sort results may differ from ASCII sort results especially for
1331 You can write your regular expressions just like someone on an ASCII
1342 is all the printable characters that the ASCII character set contains.
1383 sub is_latin_1 { # But not ASCII; not C1
1388 These are valid only on ASCII platforms. Starting in Perl v5.22, simply
1412 sub is_latin_1 { # But not ASCII; not C1
1453 sub Is_latin_1 { # But not ASCII; not C1
1475 sub Is_latin_1 { # But not ASCII; not C1
1484 Most socket programming assumes ASCII character encodings in network
1492 One big difference between ASCII-based character sets and EBCDIC ones
1495 digits, and the underscore (C<"_">). On ASCII platforms the native sort
1499 ones, and the digits last. If sorted on an ASCII-based platform, the
1503 @sorted = sort(qw(Dr. dr.)); # @sorted holds ('Dr.','dr.') on ASCII,
1509 before "E<euml>" (C<e WITH DIAERESIS>, 235) on an ASCII platform, but
1518 ASCII platforms versus EBCDIC platforms. What follows are some suggestions
1521 =head2 Ignore ASCII vs. EBCDIC sort differences
1531 to ASCII sort order:
1536 # Saves time on an ASCII platform
1604 Note that some URLs have hexadecimal ASCII code points in them in an
1616 where 7E is the hexadecimal ASCII code point for "~". Here is an example
1638 EBCDIC characters equivalent to their ASCII counterparts. For example,
1639 the following will print "Yes indeed\n" on either an ASCII or EBCDIC
1680 On ASCII-encoded platforms it is possible to strip characters outside of
1683 # This QP encoder works on ASCII only
1688 both ASCII and EBCDIC platforms.
1690 # This QP encoder works on both ASCII and EBCDIC
1694 For earlier Perls, a QP encoder that works on both ASCII and EBCDIC
1704 ASCII branch without the expense of the identity map; in Perl v5.22, the
1710 # This QP decoder is limited to ASCII only
1714 Whereas a QP decoder that works on both ASCII and EBCDIC platforms
1732 work on ASCII and EBCDIC platforms:
1749 ASCII and EBCDIC platforms.
1751 EBCDIC checksums will differ for the same file translated into ASCII
1780 is ASCII-based, not EBCDIC-based as the ILE.
1885 B<ASCII: American Standard Code for Information Infiltration> Tom Jennings,