I like this idea. Of course, this means module authors will also have
to create and maintain multiple PODs :-) Should h2xs be patched to
create stub files for alternate languages/encodings.. something like:
h2xs -<your normal switches> -l zh_TW,Big5 Foo::Bar
Which would create Foo/Bar.zh_TW.pod and Foo/Bar.Big5.pod?
This would at least encourage people to do this. I would, though, get
nervous that if I was seeing the Big5 POD, and it wasn't kept up to
date, I would be missing info contained in the 'default' POD.
Cheers,
Kevin
On Wed, Jan 29, 2003 at 11:58:31PM +0800, Autrijus Tang
(autrijus(_at_)autrijus(_dot_)org) said something similar to:
Hi folks. What do you think about a localized 'perldoc', e.g.:
env LC_MESSAGES=zh_TW.Big5 perldoc DBI
looks for DBI.zh_TW.pod and display its result, re-encoded in Big5
encoding from the default utf8?
This way we can distribute documents in several language alongside
each module; the recoding part I've already sent as a patch to Sean
Burke's Pod::Perldoc.
Thoughts,
/Autrijus/
--
[Writing CGI Applications with Perl - http://perlcgi-book.com]
I invented the cordless extension cord.
-- Steven Wright
