And while you're there, try to shut up the whiny w3c 
validator... 
 

Logged In: YES 
user_id=469548

Let's try to get to 4.01 compliance first...

Logged In: YES 
user_id=469548

I've fixed most issues, but there are some left:

- I'm not sure how to emulate wrap="hard" in CSS yet.
- The 'action' attribute is required on <form> elements.
I'll have to figure out how to refer to the current page
with TAL.
- tal:replace="structure db.user.classhelp()" gets us a page
with a javascript call, with a unencoded url as an argument.
The validator balks on this, as it can't find the 'entity'
'&property'.
- I haven't checked the '_generic.*' templates yet.

Logged In: YES 
user_id=469548

Okay, only the wrap="hard" issue is left. Could someone more
knowledgable of CSS (especially cross-browser CSS) help me
on this one.

Also, it might be good to have a script checking validation
of all templates using demo.py.

Logged In: YES 
user_id=469548

I'm reassigning this to Feature Requests: the classic
tracker is now valid HTML 4.01 Transitional (except for
wrap="hard", but it's necessary), and I'm not taking this
further yet.

Logged In: YES 
user_id=764

how well is the html 4.1 specific code encapsulated ? Would
it be possible to provide an alternative implementation that
generates valid xhtml ?
Then the choice of the formatter could be made via the
config file...

Logged In: YES 
user_id=469548

Most of the HTML is generated using templates, so an
alternative implementation should not be a problem for those
parts. There is some HTML-generation in cgi/templating.py
(the HTMLItem and HTMLProperty classes) and cgi/client.py
though.

However, I don't think there's a need for an alternative
implementation, as I would welcome patches that would bring
us to XHTML compliance.

Logged In: YES 
user_id=764

unfortunately, there needs to be some polymorphism.
I'll look into it asap and try to come up with a small patch...

Logged In: YES 
user_id=764

ok, patch sumbitted (see
https://sourceforge.net/tracker/index.php?func=detail&aid=834620&group_id=31577&atid=402790)
.

Please consider two sets of templates for the demo (to be
selected via config.py) to work on the remaining issues for
xhtml compliance.

Logged In: YES 
user_id=6405

I've barely enough time to respond to the most urgent Roundup issues 
these days, and I'm unlikely to find enough time to maintain *two* sets 
of HTML templates for the classic tracker, just so we can say it's either 
valid HTML4 *or* valid XHTML. 
 
Could we please just choose one and be happy with that? 
 
I'd be more than happy for someone else to maintain the other format 
template as a 3rd-party template. 
 

Logged In: YES 
user_id=764

understood. I'd strongly recommend to switch to xhtml, then.
The reason for me to be so keen on xhtml is that I generate
my website (http://fresco.org) entirely from xml, the issue
tracker templates (http://issues.fresco.org) are part of that.
But since with all the embedded tal: namespace its neither
valid xml nor html, I'd like to move over to xhtml, because then
I can treat it as ordinary xml.

Thanks.

Logged In: YES 
user_id=6405

xhtml seems to be the way people are going these days. I have no 
problem with making the classing template's html XHTML. 
 

Logged In: YES 
user_id=6405

ugh... braino...  
 
s/classing/classic 

Logged In: YES 
user_id=764

any chance of getting my submitted patch for xhtml/html4
compliance
into cvs any time soon ?