Re: Recent pod

2013-02-25 Thread Johan Vromans 
David E. Wheeler da...@justatheory.com writes:

 On Feb 25, 2013, at 9:20 AM, Russ Allbery r...@stanford.edu wrote:

 Better (since it doesn't change the formatting):
 
=item 0Z
 
=item *Z

 I think S would work, too.

Just what we need... more obscure trickery.

Why not replace =item * by something friendly like =bullet ?

Also quite stupid:

  =over 4

  =item 1.

  First item.

  =item 1.

  Another item.

  =back

Computers are very good at numbering list items.

-- Johan

Re: Non-ASCII data in POD

2012-05-03 Thread Johan Vromans 
Grant McLean gr...@mclean.net.nz writes:

 OK, so I went ahead and implemented both the warning and the heuristic
 to guess Latin-1 vs UTF-8 (only when no encoding was specified).  The
 resulting patch is here:

   https://github.com/theory/pod-simple/pull/26

This patch enforces authors to add an =encoding UTF-8 line to
specify that the doc is, indeed, UTF-8 encoded.

Wouldn't it be far better to consider all POD documents to be Utf-8
encoded Unicode and fall back to Latin1 if invalid UTF-8 sequences are
detected? In other words, do not enforce the author to add =encoding
UTF-8 since that's the default? And only add =encoding ISO8859-1 for
Latin1 encoded documents?

Since most POD documents currently are ASCII, they won't be affected.

POD docs that are Latin1 or something similar must get an explicit
encoding line added. These are precisely the documents affected by your
patch.

-- Johan

Re: Object Oriented PODs

2003-02-21 Thread Johan Vromans 
Sean M. Burke [EMAIL PROTECTED] writes:

 What you say is undermined by one word: 90.

Even with 2 classes it would be advanteous to have the PODs inherit
just like the classes.

-- Johan