[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: perlpod conversion
From: |
Karl Berry |
Subject: |
Re: perlpod conversion |
Date: |
Thu, 19 Apr 2012 19:00:16 -0700 |
perl5142delta.pod
is a link to perldelta.pod
Thanks. I'm omitting *delta anyway :).
There are still some issues, one is the incorrect handling of X<> in title
bu PullParser, that I reported and will hopefully be fixed.
I suppose this is the cause of the top-level NAME entries like
* NAME debug debugger::
? (No biggie, just wondering.)
I attach the script I use, and also an enhanced script to convert each
.pod to a standalone texi.
Thanks. It went fine. Very helpful to have this.
I was thinking about putting the Info files, at least, and maybe HTML
files too, on the GNU web pages somewhere, in case others would find it
useful. What do you think?
As it stands, though, the split-by-whatever HTML can't be generated, e.g.:
$ perl $txi/tp/texi2any.pl --html --no-warn --no-validate perl_pods.texi
Could not open
perl_pods/perldiag-Ambiguous-use-of-_0027s_002f_002fle_002e_002e_002e_0027-resolved-as-_0027s_002f_002f-le_002e_002e_002e_0027_003b-Rewrite-as-_0027s_002f_002fel_0027-if-you-meant-_0027use-locale-rules-and-evaluate-rhs-as-an-expression_0027_002e-In-Perl-5_002e16_002c-it-will-be-resolved-the-other-way.html
for writing: File name too long
Maybe it would be worth arbitrarily chopping names at 255 chars. After
all, it's not like anyone is going to want to xref to a node name that
is 300+ chars long, so it's just a matter of getting the run to succeed ...
The nonsplit HTML is over 7mb, which seems rather excessive.
Thanks,
Karl