Any comments on this proposal? I am reluctant to change this
in Pod-Parser, since this package is declared "dead", and I
foresee a couple of flames to change that back once I'd have
implemented that.
Nevertheless this might be sensible input for Pod::Simple
and podlators, i.e. the _new_ POD formatters.
-Marek
-----Original Message-----
From: J'raxis.Com Software [mailto
Sent: Tuesday, May 31, 2005 4:51 AM
To: Marek Rouchal
Subject: Pod::Usage I<> suggestion
[I attempted to send this to Brad Appleton <[EMAIL PROTECTED]>, the
author as listed in the documentation for this module, and the mail
bounced. Perhaps you know where to direct this mail?]
Hi,
Here's a little patch to Pod::Usage to make statements like
"--option=I<VALUE>" look better on output. Pod::Text wraps "VALUE" with
asterisks, which looks ugly and nonconventional, and in some cases can
be confusing (e.g., "2*I<VALUE>" comes out as "2**VALUE*" which makes
multiplication look like exponentiation). Since italics in manpages
usually indicate variables, angle brackets seem like the best thing IMO
to use in plaintext.
diff -Naur Pod-Parser-1.30.old/lib/Pod/Usage.pm
Pod-Parser-1.30/lib/Pod/Usage.pm
--- Pod-Parser-1.30.old/lib/Pod/Usage.pm 2005-03-12
17:07:30.000000000 +0000
+++ Pod-Parser-1.30/lib/Pod/Usage.pm 2005-05-31 02:34:03.000000000
+0000
@@ -632,4 +632,7 @@
return $self->SUPER::preprocess_paragraph($_);
}
+# override I<text> -> *text* from Pod::Text.
+sub seq_i { return '<' . $_[1] . '>' }
+
1; # keep require happy
--
J'raxis 270145
http://www.jraxis.com/
