headers
William McKee | 1 Mar 05:42
Favicon

Processing HTML

Hi Jean-Michel,

I'm working on writing some reviews about Petal for CPAN and a wiki that
I frequent[1]. In so doing, I was reading your Summary from the pod and
have a question about the following line:

  "Petal is a XML based templating engine that is able to process any
  kind of XML, XHTML and HTML."

Now, to my understanding, I'm under the impression that Petal cannot do
HTML without the help of HTML::TreeBuilder. This requires the use of
Petal::Parser::HTB, right? Should that line be rephrased or a footnote
added to explain how HTML is handled?

I cringe to bring up this issue since I know you're hesitant to continue
supporting Petal::Parser::HTB. Is anyone else on the list using a
version of Petal <2.00 or using the HTB parser with Petal 2+? I'm
slowing bringing some of my original websites up to well-formed XHTML
but haven't even switched my production server to 2.02 yet so am not
ready for losing access to HTB.

Thanks,
William

[1] http://cgi-app.org

--

-- 
Knowmad Services Inc.
http://www.knowmad.com
(Continue reading)

Permalink | Reply |
headers
Jean-Michel Hiver | 1 Mar 15:08

Re: Processing HTML

William McKee wrote:

>Hi Jean-Michel,
>
>I'm working on writing some reviews about Petal for CPAN and a wiki that
>I frequent[1]. In so doing, I was reading your Summary from the pod and
>have a question about the following line:
>
>  "Petal is a XML based templating engine that is able to process any
>  kind of XML, XHTML and HTML."
>
>Now, to my understanding, I'm under the impression that Petal cannot do
>HTML without the help of HTML::TreeBuilder. This requires the use of
>Petal::Parser::HTB, right? Should that line be rephrased or a footnote
>added to explain how HTML is handled?
>  
>
I suppose this is deprecated. I'll have to update the docs.

I am really sorry I am unable to support the HTML parser as it should 
be. I would like to hightlight that:

* We do not use HTML anywhere in MKDoc, only XML / XHTML. Hence HTML is 
of no interest to me. It was just put there merely as a niceness / proof 
of concept of the multiple parsing backend functionality.

* I am in the process of re-factoring MKDoc into a bunch of modules and 
releasing them on CPAN, which simply takes enormous amounts of time.

* I have to do some paid work sometimes too, and there's only so many
(Continue reading)

Permalink | Reply |

Gmane