From: Karl Williamson <public@khwilliamson.com>
Date: Sat, 16 Feb 2013 18:04:17 +0000 (-0700)
Subject: charnames.pm: Nit in pod
X-Git-Tag: upstream/5.20.0~4013
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=2f8114fb08248fa8661a45c7e473b59c7e633458;p=platform%2Fupstream%2Fperl.git

charnames.pm: Nit in pod
---

diff --git a/lib/_charnames.pm b/lib/_charnames.pm
index 9888301..4ab9411 100644
--- a/lib/_charnames.pm
+++ b/lib/_charnames.pm
@@ -7,7 +7,7 @@ package _charnames;
 use strict;
 use warnings;
 use File::Spec;
-our $VERSION = '1.35';
+our $VERSION = '1.36';
 use unicore::Name;    # mktables-generated algorithmically-defined names
 
 use bytes ();          # for $bytes::hint_bits
diff --git a/lib/charnames.pm b/lib/charnames.pm
index a38ea7b..07ffe80 100644
--- a/lib/charnames.pm
+++ b/lib/charnames.pm
@@ -1,7 +1,7 @@
 package charnames;
 use strict;
 use warnings;
-our $VERSION = '1.35';
+our $VERSION = '1.36';
 use unicore::Name;    # mktables-generated algorithmically-defined names
 use _charnames ();    # The submodule for this where most of the work gets done
 
@@ -357,7 +357,7 @@ C<string_vianame> returns C<undef> instead of it being a syntax error.
 =head1 charnames::vianame(I<name>)
 
 This is similar to C<string_vianame>.  The main difference is that under most
-circumstances, vianame returns an ordinal code
+circumstances, C<vianame> returns an ordinal code
 point, whereas C<string_vianame> returns a string.  For example,
 
    printf "U+%04X", charnames::vianame("FOUR TEARDROP-SPOKED ASTERISK");