This works ok for the most part, but as you might know all tags in
XML/XHTML must be properly closed. I.e. the BR tag must either be
written BR/BR or more commonly used the shorthand form BR/ or
sometimes BR /.
XML and XHTML are quite different standards, though some of their
content overlaps. In XML and XHTML though, the only officially allowed tag
(from where I've read) for self-closing elements is FOO /, but not FOO
/FOO or FOO/. Just an FYI. Note though, that in XML, you can call your
tags anything you want, since they are not HTML. You can use BREAK../BREAK
or BREAK /, but for XHTML, you have to use hr /, br /, img src=...
/ and so on.
If the full expanded tag is used plucker displays one break (line feed)
and the /BR tag. If using the shorthand form plucker does'nt display any
break but the tag BR/.
I can see why it would be confused. Currently the parser doesn't speak
XHTML tags, and the '/' may be confusing it, since normally that prefaces the
actual closing element:
a href.. foo /a
^
Is there a way to make plucker interpret the BR/BR, BR/ and BR /
tags as just normal BR ?
You could add a quick hack to regex them out of the content if you
wanted to, or perhaps someone could add expat support to the Python parser, so
it can handle these natively. Hand-rolling HTML and XML parsers is a pain in
the rear. I rely on Perl's modules to handle all of that for me, SO much
easier than doing it the Python way.
/d
