summaryrefslogtreecommitdiff
path: root/pod/perlunicode.pod
diff options
context:
space:
mode:
authorRafael Garcia-Suarez <rgarciasuarez@gmail.com>2002-07-07 20:31:37 +0000
committerRafael Garcia-Suarez <rgarciasuarez@gmail.com>2002-07-07 20:31:37 +0000
commitfae2c0fbfb26247eb616ab310ef74b1f4084ba68 (patch)
treecd832c0b11bee759c923fd0b3ed89b90fc048a22 /pod/perlunicode.pod
parent0622c8ef6e71e0e2e2cd320a0691e7a48e401c68 (diff)
downloadperl-fae2c0fbfb26247eb616ab310ef74b1f4084ba68.tar.gz
Replace the word "discipline" by "layer" almost everywhere,
by Elizabeth Mattijsen. p4raw-id: //depot/perl@17410
Diffstat (limited to 'pod/perlunicode.pod')
-rw-r--r--pod/perlunicode.pod4
1 files changed, 2 insertions, 2 deletions
diff --git a/pod/perlunicode.pod b/pod/perlunicode.pod
index 0aec6fee11..8489702fd5 100644
--- a/pod/perlunicode.pod
+++ b/pod/perlunicode.pod
@@ -12,7 +12,7 @@ from cover to cover, Perl does support many Unicode features.
=over 4
-=item Input and Output Disciplines
+=item Input and Output Layers
Perl knows when a filehandle uses Perl's internal Unicode encodings
(UTF-8, or UTF-EBCDIC if in EBCDIC) if the filehandle is opened with
@@ -87,7 +87,7 @@ Unless explicitly stated, Perl operators use character semantics
for Unicode data and byte semantics for non-Unicode data.
The decision to use character semantics is made transparently. If
input data comes from a Unicode source--for example, if a character
-encoding discipline is added to a filehandle or a literal Unicode
+encoding layer is added to a filehandle or a literal Unicode
string constant appears in a program--character semantics apply.
Otherwise, byte semantics are in effect. The C<bytes> pragma should
be used to force byte semantics on Unicode data.