#589: FPF generates invalid xhtml
-----------------------------------------------------+----------------------
Reporter: André Fiedler <[EMAIL PROTECTED]> | Owner: david
Type: defect | Status: closed
Priority: high | Milestone: 0.11
Component: filter | Version: HEAD
Severity: critical | Resolution: wontfix
Keywords: |
-----------------------------------------------------+----------------------
Changes (by david):
* status: new => closed
* resolution: => wontfix
Comment:
This is a problem with your libxml version. Please update libxml, and the
problem will go away.
Your patch also does not cure the problem. There are many elements in HTML
that are not specified as ''EMPTY'' in the Document Type Definition. FPF
generates perfectly valid XML, but not XHTML that is valid against the
DTD, unless you load and validate against the DTD (enable some of
{{{dom_resolve_externals}}}, {{{dom_substitute_entities}}} and
{{{dom_validate_on_parse}}} to see if that helps).
Recent versions of libxml can detect XHTML from the doctype declaration
and by looking at the namespace. It will generate valid XHTML if it spots
either, but as I said, your libxml is probably too old and does not yet
have this feature. Note that loading externals potentially means that
PHP/DOM/libxml pulls the DTD over the net '''every time''' FPF runs,
unless you set up DTD caching for it (Google around to see how that works,
but... yes... try updating libxml first).
In any case, it's not an Agavi but, and nothing we can fix anyway (plus
you can work around the issue by using the configuration parameters
described above).
Thanks for the reporting the problem though :) Please refer to the mailing
lists or consult the IRC channel if you have any questions.
--
Ticket URL: <http://trac.agavi.org/ticket/589#comment:2>
Agavi <http://www.agavi.org/>
An MVC Framework for PHP5
_______________________________________________
Agavi Tickets Mailing List
[email protected]
http://lists.agavi.org/mailman/listinfo/tickets
