Front page | perl.perl5.porters |
Postings from March 2000
scozens <scozens@pwj.co.jp> writes: > (POD) > # Brad's PodParser code needs to become part of the core, Done. > # and the Pod::* > # and pod2* programs rewritten to use this standard parser. Done except for pod2latex and pod2html. > ! replace pod2html with new PodtoHtml? (requires other modules from CPAN) There are a few different candidates at this point, I think, but something should be done to upgrade pod2html (and pod2latex) so something that uses Pod::Parser. > # Users can't find the manpages > Fixing manpaths to include the Perl man pages to. No idea how to do > this. This is a long, long discussion with a lot of tradeoffs and counterarguments involved in it. Just putting the Perl man pages in the standard man path tends to have negative effects on very common but inferior man programs (doing man less gives you the Perl module instead of the program, for example). > Reorganising perldoc: > # Include a search tool > The idea is that all there's an index to all the POD pages by > keyword, (presumably autogenerated from individual pages) and > we can look stuff up by keyword. Has this found favour? > # Include a locate tool > I have this, but it's not integrated into perldoc. If people > want, I'll combine it in. These are sort of reinventing man features for perldoc. > # Mailing list archives > `Chaim suggests contacting egroup'. Has this been done? I'd very much prefer that we do our own archiving via one mechanism or another. All of the major list hosting facilities have various problems; either they append ads to all messages, have spamming problems, "rebrand" content in ways that a lot of list owners have problems with, or have other related problems. -- Russ Allbery (rra@stanford.edu) <http://www.eyrie.org/~eagle/>