diff options
| author | Karl Williamson <public@khwilliamson.com> | 2011-07-10 14:28:26 -0600 |
|---|---|---|
| committer | Karl Williamson <public@khwilliamson.com> | 2011-07-10 15:35:01 -0600 |
| commit | 5bff20359f7addcab31aec658577ac9469f6191a (patch) | |
| tree | 49e76b71f6cfdd810e7d8beb085cfbcf3ea44a61 /pod | |
| parent | 56e1c5aa51eb9e2d3837eb510ca49bc17cd2b036 (diff) | |
| download | perl-5bff20359f7addcab31aec658577ac9469f6191a.tar.gz | |
perlunicode: nits
Diffstat (limited to 'pod')
| -rw-r--r-- | pod/perlunicode.pod | 8 |
1 files changed, 5 insertions, 3 deletions
diff --git a/pod/perlunicode.pod b/pod/perlunicode.pod index 20dfcbd201..c7bdef4bcb 100644 --- a/pod/perlunicode.pod +++ b/pod/perlunicode.pod @@ -301,7 +301,8 @@ This formality is needed when properties are not binary; that is, if they can take on more values than just True and False. For example, the Bidi_Class (see L</"Bidirectional Character Types"> below), can take on several different values, such as Left, Right, Whitespace, and others. To match these, one needs -to specify the property name (Bidi_Class), AND the value being matched against +to specify both the property name (Bidi_Class), AND the value being +matched against (Left, Right, etc.). This is done, as in the examples above, by having the two components separated by an equal sign (or interchangeably, a colon), like C<\p{Bidi_Class: Left}>. @@ -557,8 +558,9 @@ Unicode ones, but some are genuine extensions, including several that are in the compound form. And quite a few of these are actually recommended by Unicode (in L<http://www.unicode.org/reports/tr18>). -This section gives some details on all extensions that aren't synonyms for -compound-form Unicode properties (for those, you'll have to refer to the +This section gives some details on all extensions that aren't just +synonyms for compound-form Unicode properties +(for those properties, you'll have to refer to the L<Unicode Standard|http://www.unicode.org/reports/tr44>. =over |