Ricardo Signes wrote:
I would like to refactor the code as I work so that methods are easier to find,
use, and replace as needed. Maybe I can fill in some of the to do
documentation, once I understand what the hell is going on.
Is anyone going to be put off by these kinds of changes *in
I recently got my Advent calendar converted entirely to Pod::Simple where it
had previously used Pod::Parser. I needed two features added.
I sent Allison and David a pull request for the first, this morning. It allows
you to say =head1 becomes h2 or becomes h3 and so on, which makes it
easier
* David E. Wheeler da...@kineticode.com [2009-12-11T12:56:28]
=for xhtml tag.../tag
...pass the XHTML right through. This is invaluable for producing my
colorized code samples. (I assume it also works as a begin/end block.)
If it is welcome, I will add it to Pod::Simple::XHTML
* Ricardo Signes perl@rjbs.manxome.org [2009-12-11T13:36:32]
* David E. Wheeler da...@kineticode.com [2009-12-11T12:56:28]
Sounds useful. What does the patch look like?
Right now, it's a subclass. I will make a patch in a branch on Github...
That was easy!
On Dec 11, 2009, at 10:58 AM, Ricardo Signes wrote:
http://github.com/rjbs/pod-simple/tree/xhtml-region
David and I spoke about this on AIM a little...
Right now, given this input in Pod::Simple::HTML:
=begin html
div.../div
=end html
The HTML is passed through untouched.
David E. Wheeler wrote:
On Dec 11, 2009, at 10:58 AM, Ricardo Signes wrote:
http://github.com/rjbs/pod-simple/tree/xhtml-region
David and I spoke about this on AIM a little...
Right now, given this input in Pod::Simple::HTML:
=begin html
div.../div
=end html
The HTML is passed
* David E. Wheeler da...@kineticode.com [2009-12-11T14:02:33]
I asked Graham earlier this week if he'd consider switching to
Pod::Simple::XHTML, and his comment was that, if we did that, and someone had
invalid html in a `=for html` section, it would make the whole document
invalid. Of course,
* Ricardo Signes perl@rjbs.manxome.org [2009-12-11T14:40:52]
David and I spoke on AIM. This is 99.99% a regression introduced in October!
I will fix it.
I've fixed this problem, added tests, and created a new method,
accept_targets_as_html. This acts like _as_text, but the collected texts
On Dec 11, 2009, at 12:08 PM, Ricardo Signes wrote:
I've fixed this problem, added tests, and created a new method,
accept_targets_as_html. This acts like _as_text, but the collected texts are
emitted literally, without entity escaping. The 'html' target now uses that
mechanism. I removed
On Dec 7, 2009, at 5:02 PM, David E. Wheeler wrote:
On Dec 7, 2009, at 4:44 PM, Russ Allbery wrote:
Hm, just to check, did you already talk to the folks at he.net and confirm
that they're okay with tons of Perl documents being pointed at their web
site? They may have resource constraints.
10 matches
Mail list logo
