summaryrefslogtreecommitdiff
path: root/pod/perlunicode.pod
diff options
context:
space:
mode:
authorbrian d foy <bdfoy@cpan.org>2010-01-13 17:19:25 +0100
committerbrian d foy <bdfoy@cpan.org>2010-01-13 17:19:25 +0100
commitac0367249e563330db9a9a04f778eae30defbab0 (patch)
tree7f99b67d93a06be0fb7aa702db8dfd4e24ff501d /pod/perlunicode.pod
parent8d2e243f5816f9d2c4247f962523e4220e4a9ce8 (diff)
downloadperl-ac0367249e563330db9a9a04f778eae30defbab0.tar.gz
* Em dash cleanup in pod/
I looked at all the instances of spaces around -- and in most cases converted the sentences to use more appropriate punctuation. In general, the -- in the perl docs seem to be there only to make really complicated and really long sentences. I didn't look at the closed em-dashes. They probably have the same sentence-complexity problem. I left some open em-dashes in place. Those are the ones used in lists.
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 50a2843441..042e421ccd 100644
--- a/pod/perlunicode.pod
+++ b/pod/perlunicode.pod
@@ -31,7 +31,7 @@ To indicate that Perl source itself is in UTF-8, use C<use utf8;>.
The regular expression compiler produces polymorphic opcodes. That is,
the pattern adapts to the data and automatically switches to the Unicode
character scheme when presented with data that is internally encoded in
-UTF-8 -- or instead uses a traditional byte scheme when presented with
+UTF-8, or instead uses a traditional byte scheme when presented with
byte data.
=item C<use utf8> still needed to enable UTF-8/UTF-EBCDIC in scripts
@@ -857,7 +857,7 @@ two (or more) classes.
END
}
-It's important to remember not to use "&" for the first set -- that
+It's important to remember not to use "&" for the first set; that
would be intersecting with nothing (resulting in an empty set).
=head2 User-Defined Case Mappings