diff options
| author | David Golden <dagolden@cpan.org> | 2013-05-23 18:08:48 -0400 |
|---|---|---|
| committer | David Golden <dagolden@cpan.org> | 2013-05-23 20:11:25 -0400 |
| commit | 3d6c5fec8cb3579a30be60177e31058bc31285d7 (patch) | |
| tree | bd3a0ce863e817d79188b0a232d1dfd63ae3a1e0 /pod | |
| parent | 1dcc3c19f1c031cf741527de0a2b2e4c178e9f04 (diff) | |
| download | perl-3d6c5fec8cb3579a30be60177e31058bc31285d7.tar.gz | |
fix various podcheck nits
Diffstat (limited to 'pod')
| -rw-r--r-- | pod/perldiag.pod | 6 | ||||
| -rw-r--r-- | pod/perlfunc.pod | 3 | ||||
| -rw-r--r-- | pod/perlunifaq.pod | 6 |
3 files changed, 6 insertions, 9 deletions
diff --git a/pod/perldiag.pod b/pod/perldiag.pod index 3d58c7b9b0..229ce0dc38 100644 --- a/pod/perldiag.pod +++ b/pod/perldiag.pod @@ -4662,11 +4662,7 @@ L<perlre>. (F) The end of the perl code contained within the {...} must be followed immediately by a ')'. -=item Z<>500 Server error - -See Server error. - -=item Server error +=item Server error (a.k.a. "500 Server error") (A) This is the error message generally seen in a browser window when trying to run a CGI program (including SSI) over the web. The diff --git a/pod/perlfunc.pod b/pod/perlfunc.pod index 9540a01883..5c6b4f8606 100644 --- a/pod/perlfunc.pod +++ b/pod/perlfunc.pod @@ -2471,8 +2471,7 @@ is left as an exercise to the reader. The C<POSIX::getattr> function can do this more portably on systems purporting POSIX compliance. See also the C<Term::ReadKey> -module from your nearest CPAN site; details on CPAN can be found under -L<perlmodlib/CPAN>. +module from your nearest L<CPAN|http://www.cpan.org> site. =item getlogin X<getlogin> X<login> diff --git a/pod/perlunifaq.pod b/pod/perlunifaq.pod index f952d1a3f9..93997683c4 100644 --- a/pod/perlunifaq.pod +++ b/pod/perlunifaq.pod @@ -136,8 +136,6 @@ concern, and you can just C<eval> dumped data as always. =head2 Why do regex character classes sometimes match only in the ASCII range? -=head2 Why do some characters not uppercase or lowercase correctly? - Starting in Perl 5.14 (and partially in Perl 5.12), just put a C<use feature 'unicode_strings'> near the beginning of your program. Within its lexical scope you shouldn't have this problem. It also is @@ -164,6 +162,10 @@ already been upgraded. For a more detailed discussion, see L<Unicode::Semantics> on CPAN. +=head2 Why do some characters not uppercase or lowercase correctly? + +See the answer to the previous question. + =head2 How can I determine if a string is a text string or a binary string? You can't. Some use the UTF8 flag for this, but that's misuse, and makes well |