Front page | perl.pod2 |
Postings from October 2009
Hi Adriano, happy to hear from you! :-) 2009/10/6 Adriano Ferreira <a.r.ferreira@gmail.com>: >> >> I also contacted several times Adriano Ferreira (the current >> Pod::Perldoc maintainer) since the module have to cooperate with POD2 >> packages. >> 5.10.1 Pod::Perldoc breaks POD2:: packages and also latest CPAN >> Pod::Perldoc contains several little bugs (I sent a patch to p5p >> list). >> Unfortunately he didn't respond yet to me :-\ > > I am listening. My basic point is that we need a base package like > POD2::Base which is optionally loaded by perldoc and not part of p5p core. > Why a base package? So we can sophisticate language support, with the > minimum fuss for Pod::Perldoc code which is rather clunky by now. Adding to > the top of it (without a plugin-like structure) won't make it better, but > instead harder to maintain and evolve. > Why not part of p5p core? Because p5p don't want or need more modules to > take care of. Look how CPAN.pm has a myriad of useful optional modules which > are not part of the core, and it still works. I agree with you on POD2::Base (or simpy POD2.pm), but IMHO it should be in the core! :-) The fact is that without POD2::Base, starting from Pod::Perldoc ( v > 3.14_2), the POD2 translation packages don't work. I already sent to p5p and to you a post regarding that (http://www.nntp.perl.org/group/perl.perl5.porters/2009/09/msg150704.html). The main reason is that starting from Pod::Perldoc 3.14_03, the translators are objects or, to better explain, must have new() and pod_dirs() function/methods. So, the ways to solve the problem are: 1) update POD2:: packages by adding those methods (I done as workaround for POD2::IT) 2) require POD2::Base 3) downgrade Pod::Perldoc, by re-adding pod_dirs() method I think that the 2nd is the best solution, once POD2::Base will be in the core :-) POD2::Base also should manage (by loading correct POD2::<LANG> module) all localized strings used by Pod::Perldoc and others most used Pod:: modules (like Pod::HTML that match "=head1 NAME" lines) Best - EnricoThread Previous | Thread Next