Stas Bekman wrote:
the only tweaks we are going to do are semantic ones (i.e. messing with pod tags), and that should be trivially to fix. The biggest challenge is to get a sensible conversion of the C docs to Perl docs. So I won't worry about this now. We will polish this later.
Should I then just post a patch to the PODTemplate.pm?
Feel free to ask questions and we will provide the answers. But really this is just a template to use for creating the docs.
I suppose what's confusing is that Gerald has suggested the intermediate format, which I suggest to simply drop and everything becomes simpler at once (of course at the price of having less flexible sources)
Assuming we drop the intermediate format (just for a moment) what would the "stages" of AUTOGENERATION be?
Stage 1. Pull docs into raw_src
Stage 2. Edit the docs by hand
Stage 3. Write scripts using the POD::* modules that convert the docs to alternate formats (or leave that to those who want those alternate formats)?
?
I think with all the POD::* modules available, it shouldn't be too hard to deal without the intermediate format. What was the original thinking behind having the intermediate format?
-- Jack
__________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
