Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
[EXPERIMENT] the "installhtml" make target #12726
There is an C<install.html> target in the Makefile. It's marked as
1. Checking that cross linking between various parts of the
2. Improving the code that split C<perlfunc> into chunks, preferably
Challenges here are correctly identifying the groups of functions that
Note also the current code isn't ideal with the two forms of C<select>,
On Mon, Jan 21, 2013 at 5:26 PM, Ricardo SIGNES
I think it'd be a bit silly if we don't at the same time improve
On Mon, Jan 21, 2013 at 9:13 AM, Leon Timmermans <email@example.com> wrote:
You are probably thinking of this one:
At the Perl hackathon we held at Duck-Duck-Go last summer, Rik Signes
I spent several weeks giving this module the Phalanx treatment (see:
So, eventually I began to pose these questions to myself -- and now to you:
* Why is Pod::Html still part of the Perl 5 core distribution?
* Why is Pod::Html still maintained in blead, i.e., why is it still the
* Wouldn't Pod::Html be better off if it were maintained on CPAN?
* If it were maintained on CPAN, would we even need to "dual-life" it,
* Are there packagers who depend on Pod::Html, pod2html, or the
Open for discussion. But if you think this functionality still deserves
Thank you very much.
On Tue, Jan 22, 2013 at 1:21 AM, James E Keenan via RT
Module::Build uses it if the perl was configured to have a location to
Because no one has taken it over.
HTML > manpages. We're living in the 21st century, and our hypertext
On 1/21/13 7:41 PM, Leon Timmermans wrote:
Can you elaborate on that? I wouldn't think that HTML would be used as
Thank you very much.
* James E Keenan <firstname.lastname@example.org> [2013-01-21T21:55:19]
Just this week (or maybe last) we had someone write in because our
A while back, we were really hesitant to break apart some very large documents
We are in an awkward position where our documentation is very bounded by the
I'm not saying we must keep installhtml, or must get rid of it, or anything
All that said: if nobody is going to do any work to maintain, support, or
Note that everyone is conflating HTML install targets, pod2html and Pod::HTML
It's possible to toss Pod::HTML completely but keep the other two functional
On Tue, Jan 22, 2013 at 01:41:23AM +0100, Leon Timmermans wrote:
Would it be better if it died?
On Mon, Jan 21, 2013 at 10:40:03PM -0500, Ricardo Signes wrote:
So would be the best plan of attack be to redo HTML documentation building
[Obviously this needs /volunteer+/ to work on it, but as it's not a task
* Nicholas Clark <email@example.com> [2013-01-22T08:06:34]
It's true, but to what extent would a "convert all the documents in these
Pod::Simple::XHTML converts /one/ document.
Pod::Simple::HTMLBatch converts /many/. It uses (but does not subclass)
Hey, buddy, you leave me out of this. ;)
On Tue Jan 22 05:07:20 2013, nicholas wrote:
Not so. Not everyone is familiar with XHTML syntax. :-)