[ZPT] Expanded Macro Indentation

[Michael R. Bernstein]

On Fri, 2001-10-19 at 01:14, Geir B=E6kholt wrote:
>=20
> Friday, October 19, 2001, 1:13:50, you wrote:
>=20
> MRB> What I am unfamiliar with is the issue you mentioned, namely
> MRB> "...creating HTML4 single attributes and never XHTML compliant ones.=
.."
>=20
> in  html >=3D 4.01 there are some singleton attributes ; for example :
> 'selected' , 'checked' and a couple more.
>=20
> XHTML specifies that these are to be written out as fullky qualified
> XML-attributes selected=3D"selected" etc..

Do the XHTML fully qualified attributes break any older browsers?

> I ZPT , though ' they are hardcoded in the source as getting special
> treatment , and any values passed to them with tal:attributes are
> evaluated as a boolean expression, setting them on or off. (someone
> correct me if i ma wrong here). The boolean behaviour is a cool
> concept, but they still break the spec in the output.

So ZPT will take a fully qualified attribute, and either convert it to a
singleton or remove it, correct?

> MRB> I am not sure what you mean by this, and you seem to indicate that t=
here
> MRB> are other problems with creating XHTML producing Page Templates as w=
ell.
>=20
> MRB> Could you explain what the issues are with using Page Templates to
> MRB> create XHTML?
>=20
> Not many more directly related to ZPT , but a quite a lot related to
> Zope. They are mostly annoyances you can code around instead of using
> Zope's shortcuts.
>=20
> calling image-objects for example, produces an image tag. (neat
> feature) - which even got patched to include an ending slash. - still
> it produces a border=3D"0" attribute , which is illegal in XHTML1.0
> Strict. - thus , i have to make my image tags myself , instead of the
> shortcut.
>=20
> Just a minor nuisance , of course , but there are plenty of them.
> (structured-text , for example , produces uppercase tables.. ) I'll
> try to root them all out soon , and compile a nice list of what ought
> to (in my opinion) be patched.

Lists are good. Just don't write it down as a tuple, because those are
immutable. :-)

Michael.