Skip to content

Commit

Permalink
remove POD markup from verbatim sections
Browse files Browse the repository at this point in the history
Verbatim sections are rendered ... well, verbatim, so any POD markup (like `I<...>`) will show up in the output as-is (instead of being interpreted as *italics*), which looks ugly. This commit removes such markup from verbatim sections.
  • Loading branch information
mauke committed Nov 15, 2023
1 parent 2725bab commit 39a11de
Showing 1 changed file with 8 additions and 8 deletions.
16 changes: 8 additions & 8 deletions Encode.pm
Original file line number Diff line number Diff line change
Expand Up @@ -431,10 +431,10 @@ same as C<find_encoding()> but C<mime_name()> of returned object must
match to I<MIME_ENCODING>. So as opposite of C<find_encoding()>
canonical names and aliases are not used when searching for object.
find_mime_encoding("utf8"); # returns undef because "utf8" is not valid I<MIME_ENCODING>
find_mime_encoding("utf8"); # returns undef because "utf8" is not a valid MIME_ENCODING
find_mime_encoding("utf-8"); # returns encode object "utf-8-strict"
find_mime_encoding("UTF-8"); # same as "utf-8" because I<MIME_ENCODING> is case insensitive
find_mime_encoding("utf-8-strict"); returns undef because "utf-8-strict" is not valid I<MIME_ENCODING>
find_mime_encoding("UTF-8"); # same as "utf-8" because MIME_ENCODING is case insensitive
find_mime_encoding("utf-8-strict"); returns undef because "utf-8-strict" is not a valid MIME_ENCODING
=head3 from_to
Expand Down Expand Up @@ -645,7 +645,7 @@ L<Encode::Unicode> ignores I<CHECK> and it always croaks on error.
=head3 FB_DEFAULT
I<CHECK> = Encode::FB_DEFAULT ( == 0)
CHECK = Encode::FB_DEFAULT ( == 0)
If I<CHECK> is 0, encoding and decoding replace any malformed character
with a I<substitution character>. When you encode, I<SUBCHAR> is used.
Expand All @@ -655,15 +655,15 @@ warning category C<"utf8"> is given.
=head3 FB_CROAK
I<CHECK> = Encode::FB_CROAK ( == 1)
CHECK = Encode::FB_CROAK ( == 1)
If I<CHECK> is 1, methods immediately die with an error
message. Therefore, when I<CHECK> is 1, you should trap
exceptions with C<eval{}>, unless you really want to let it C<die>.
=head3 FB_QUIET
I<CHECK> = Encode::FB_QUIET
CHECK = Encode::FB_QUIET
If I<CHECK> is set to C<Encode::FB_QUIET>, encoding and decoding immediately
return the portion of the data that has been processed so far when an
Expand All @@ -682,7 +682,7 @@ code to do exactly that:
=head3 FB_WARN
I<CHECK> = Encode::FB_WARN
CHECK = Encode::FB_WARN
This is the same as C<FB_QUIET> above, except that instead of being silent
on errors, it issues a warning. This is handy for when you are debugging.
Expand Down Expand Up @@ -780,7 +780,7 @@ See L<Encode::Encoding> for details.
=head1 The UTF8 flag
Before the introduction of Unicode support in Perl, The C<eq> operator
Before the introduction of Unicode support in Perl, the C<eq> operator
just compared the strings represented by two scalars. Beginning with
Perl 5.8, C<eq> compares two strings with simultaneous consideration of
I<the UTF8 flag>. To explain why we made it so, I quote from page 402 of
Expand Down

0 comments on commit 39a11de

Please sign in to comment.