summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRicardo Signes <rjbs@cpan.org>2012-03-05 13:54:17 -0500
committerRicardo Signes <rjbs@cpan.org>2012-03-05 13:54:17 -0500
commitc85e9b4c9684bc896847f5a80e9e91b478c2fc59 (patch)
tree16d6a51b78a62ba379a66c61d433d301eba17d4a
parent4642e50d936f507ad436fe48093d9efae111f983 (diff)
downloadperl-c85e9b4c9684bc896847f5a80e9e91b478c2fc59.tar.gz
replace bogus non-ASCII dashlike char with -
This was presumably brought in when I foolishly copied and pasted the output from a version of groff that was over-eager to promote "ugly" ASCII characters to "beautiful" non-ASCII ones.
-rw-r--r--pod/perlpodspec.pod2
1 files changed, 1 insertions, 1 deletions
diff --git a/pod/perlpodspec.pod b/pod/perlpodspec.pod
index 64a38d9317..89fd9ba6f8 100644
--- a/pod/perlpodspec.pod
+++ b/pod/perlpodspec.pod
@@ -305,7 +305,7 @@ or data paragraphs. This is discussed in detail in the section
L</About Data Paragraphs and "=beginE<sol>=end" Regions>.
It is advised that formatnames match the regexp
-C<m/\A:?[−a−zA−Z0−9_]+\z/>. Everything following whitespace after the
+C<m/\A:?[-a-zA-Z0-9_]+\z/>. Everything following whitespace after the
formatname is a parameter that may be used by the formatter when dealing
with this region. This parameter must not be repeated in the "=end"
paragraph. Implementors should anticipate future expansion in the