15 Dec
2008
15 Dec
'08
5:48 p.m.
I've changed my mind a bit.
* I'd like to keep both XHTML and HTML parsers. They would both user
the HTMLCleaner though to fix any mistakes that the users could have
done. However it's more sensible for an API user to use the XHTML 1.0
parser to parse XHTML 1.0 content than having to use the HTML 4.01
parser
The rest stays, i.e. a single html macro.
Thanks
-Vincent
On Dec 15, 2008, at 3:13 PM, Vincent Massol wrote:
Hi devs,
We currently have 2 parsers and 2 macros depending on whether the
content is HTML 4.01 or XHTML 1.0. This is way too complex for users.
In addition the XHTML parser/macro expect the content to have the
DOCTYPE declaration + a root element which make them even harder to
use.
I propose to simply all this by doing the following:
* A single HTML parser
* A single html macro
* The HTMLCleaner is always called thus transforming HTML into clean
XHTML and not doing anything in case of clean XHTML (actually it'll
add the DOCTYPE and a root element if it's not there)
This simplifies code, documentation and more importantly its usage for
our end users.
Since the xhtml macro was released not long ago I'd rather not go
through a deprecation period and instead commit the changes above for
1.7.1 (with a nice message in the release notes).
I've started working on this (should be finished tonight). Please
shout if you don't agree.
Thanks
-Vincent