Hi, I noticed that the HTML generated by the Zope management interface is rather low quality, with lots of color,align, etc. attributes (which are deprecated in favor of CSS), and unclosed option tags etc. Of course I can fix this myself in my local Zope, but are there any plans to aim for, say, XHTML compliance? Keeping up with standards makes more sense than staying 100% compatible with obsolete browsers IMHO. Best regards, Jacob
On 2/4/00 7:08 AM, Jacob Gorm Hansen at jg@ioi.dk wrote:
Hi,
I noticed that the HTML generated by the Zope management interface is rather low quality, with lots of color,align, etc. attributes (which are deprecated in favor of CSS), and unclosed option tags etc.
Yes, and CSS has 100x the problems of cross-platform compliance, unfortunately. Netscape only implements some .05% of the standard, and that piece is wrong :-) Having said that, we agree that CSS is definitely favorable, but right now it's a bit shakey.
Of course I can fix this myself in my local Zope, but are there any plans to aim for, say, XHTML compliance? Keeping up with standards makes more sense than staying 100% compatible with obsolete browsers IMHO.
Perhaps you could provide us a patch set that fixes the current situation to replace it all with CSS? That would be a start. As for XHTML/etc we're waiting for more implementations before chasing theoretical standards (ISO is the "standard" for networking, but how many companies use it?) We are heavily investing in Mozilla and trying to use XUL to develop a much richer interface. However, we can only take a subset of: * Netscape 4.x on Mac, PC, UNIX * IE 4.x/5.x on Mac, PC The intersection is what we have to follow. Chris -- | Christopher Petrilli Python Powered Digital Creations, Inc. | petrilli@digicool.com http://www.digicool.com
At 10:57 AM 2/4/00 -0500, you wrote:
On 2/4/00 7:08 AM, Jacob Gorm Hansen at jg@ioi.dk wrote:
Of course I can fix this myself in my local Zope, but are there any plans to aim for, say, XHTML compliance? Keeping up with standards makes more sense than staying 100% compatible with obsolete browsers IMHO.
Perhaps you could provide us a patch set that fixes the current situation to replace it all with CSS? That would be a start. As for XHTML/etc we're waiting for more implementations before chasing theoretical standards (ISO is the "standard" for networking, but how many companies use it?) We are heavily investing in Mozilla and trying to use XUL to develop a much richer interface. However, we can only take a subset of:
* Netscape 4.x on Mac, PC, UNIX * IE 4.x/5.x on Mac, PC
The intersection is what we have to follow.
One of the requirements of XHTML is little things like making sure the tag names are lowercase, attributes use quoted values, etc. It would seem that Zope HTML could at least be cleaned up to that level. Zope HTML should also make sure that any optional closing tags be included. This would go a long way to making sure that Zope HTML is XHTML compliant without breaking lesser browsers. James W. Howe mailto:jwh@allencreek.com Allen Creek Software, Inc. pgpkey: http://ic.net/~jwh/pgpkey.html Ann Arbor, MI 48103
On 2/4/00 11:20 AM, James W. Howe at jwh@allencreek.com wrote:
One of the requirements of XHTML is little things like making sure the tag names are lowercase, attributes use quoted values, etc. It would seem that Zope HTML could at least be cleaned up to that level. Zope HTML should also make sure that any optional closing tags be included. This would go a long way to making sure that Zope HTML is XHTML compliant without breaking lesser browsers.
There is no disagreement with this, it's just simply no a priority, but obviously is something that someone in the community concerned with this could easily provide a set of patches for. Chris -- | Christopher Petrilli Python Powered Digital Creations, Inc. | petrilli@digicool.com http://www.digicool.com
Christopher Petrilli wrote:
On 2/4/00 11:20 AM, James W. Howe at jwh@allencreek.com wrote:
One of the requirements of XHTML is little things like making sure the tag names are lowercase, attributes use quoted values, etc. It would seem that Zope HTML could at least be cleaned up to that level. Zope HTML should also make sure that any optional closing tags be included. This would go a long way to making sure that Zope HTML is XHTML compliant without breaking lesser browsers.
There is no disagreement with this, it's just simply no a priority, but obviously is something that someone in the community concerned with this could easily provide a set of patches for.
I guess much of it can be automated, using find and tidy. -------------- Hannu
participants (4)
-
Christopher Petrilli -
Hannu Krosing -
Jacob Gorm Hansen -
James W. Howe