From oleonard@athenscounty.lib.oh.us Tue May 13 07:19:54 2003
From: Owen Leonard <oleonard@athenscounty.lib.oh.us>
To: koha-devel@lists.koha-community.org
Subject: Re: [Koha-devel] Koha, coding style and templates
Date: Tue, 13 May 2003 07:20:17 +0000
Message-ID: <200305131425.h4DEPC915129@alma.athenscounty.lib.oh.us>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============7104534184550411098=="

--===============7104534184550411098==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

> One more idea :
> in templates, how to write HTML ?
...
> 3- as required in w3c html : everything in right=20
> part of a token has ""=20

I'd be all for making templates XTHML-Transitional.  Barring full compliance =

with that standard, I would suggest at the very least these guidlines:

- All HTML tags in lower case (HTML:Template tags in uppercase is fine of=20
course)
- All attribute values are quoted (<table border=3D"0"> instead of <table=20
border=3D0>
- No 'minimization' of attributes, so <input type=3D"checkbox" checked> is=20
changed to <input type=3D"checkbox" checked=3D"checked">

XHTML requires that all tags be closed, so tags like <br> become <br />  This=
=20
may be too much hassle for those who don't care about XHTML-compliance, so at=
=20
minimum that 'optional' end tags be used: <p></p> <li></li> <option></option>

These kind of changes are only a minor alteration in normal HTML markup=20
writing, and will make it easier for those who want to go as far as adding th=
e=20
XHTML DocType and moving to full XHTML compliance.

What do others think?

  -- Owen

----
Nelsonville Public Library
Koha 1.9.2


--===============7104534184550411098==--