|We don't bite newbies here... much|
You didn't respond to what I consider the two most important reasons why Texinfo is a poor fit.
I'm curious to see your proposal for (what I believe will be a non-standard) escaping syntax so that comments that include Perl arrays don't accidentally turn into Texinfo directives.
Also, I stand by my assertion that any "solution" that doesn't allow people on any platform other than GNU/Linux to produce documents is completely unacceptable.
What if you already know and use markup X (where, I'm thinking Texinfo here)? If Perl6 Pod became "just like X", now your productivity at creating docs all of a sudden just went up substantially.
What if all of the existing Perl users have already encountered POD in its current form? Again, one of the major principles of the Perl 6 redesign is "Don't change things arbitrarily. Changes require compelling justifications of cleanliness, simplicity, discoverability, and consistency."
If Perl6 Pod went X, now the developers who were going to be reworking Perl5's POD tools are now freed-up and can instead spend time hacking Perl6.
Damian volunteered to revise POD for Perl 6. As I said before, at least three members of the Perl 6 design team have written more than one book in POD. We believe it is a solid system.
As a side note, be very careful about even intimating that you can tell a volunteer developer what he or she should work on.
The Perl community would be doing its part to stave off the "Yet Another Doc Format" situation.
As you admit, POD already exists.
So again, with licensing problems, syntax problems, and the arbitrariness of such a dramatic change in the face of little benefit (and contra the previous two problems), what exactly again is the benefit?
Also, what in the world do you mean by "reinventing the wheel"?
Also, I've tried to use info many times and found that it never lived up to its name.
(Also, it's "Perl 6".)