I wanted to publicly apologize for the framing of my question... I
meant it to be humorously provocative but I fear it could be easily
misread to be rude and annoying, and not easily turned into something
productive. That wasn't my intention.
I am curious if anyone thinks having support for outputting html4
compliant markup in Django is a good thing? And if so, what can I do
to help make that become a reality?
In searching for previous discussions I found one that I brought up in
Jan 2007 that never got traction, though most people seemed to agree
that there was some merit to the argument...
http://groups.google.com/group/django-developers/browse_frm/thread/b2ace4f7f69a73f6/78b927bc18d093d5
There was also some discussion (and I believe an attempt) to making
templatetags for newforms, I believe, based on Simon Willison's
suggestion:
http://groups.google.com/group/django-developers/browse_frm/thread/5f3694b8a19fb9a1
Is this important for anyone else besides me?
My humble apologies,
Rob
I for one would appreciate it, because I'm abotu to switch back to
HTML4 Strict and I'm having to write some support code to handle that.
--
"Bureaucrat Conrad, you are technically correct -- the best kind of correct."
It's not unimportant - there is certainly an idea in here that
warrants some further discussion.
However, if we _ever_ want to get v1.0 out the door, we're going to
have to draw the line somewhere. This wouldn't be a trivial change -
at the very least, it will require a bit of discussion to work out
exactly what we should be doing. If we spend our time having those
discussions and implementing the result, thats time that isn't being
spent finishing newforms-admin, nailing the stray bugs post-qsrf, or
doing any of the other tasks on the v1.0 todo list.
Can I suggest that you log this as a ticket, mark it someday/maybe,
summarize your thoughts if you feel so enthused, and put a pin in it
until post v1.0. Once we have that out the door, we'll be looking for
something to do, and a HTML4 transition of some sort could be it.
Yours,
Russ Magee %-)
I agree any sort of transition should be tabled for now. And a
transition to HTML4 will also likely lead to discussions of having
XHTML support as an alternative.
And supporting HTML4 "in the meantime" (weird, that song by Helmet is
playing in shuffle mode as I typed that) would be nice if it were
easier, but there are some hackish ways to get it to work as is, so
maybe it's not worth the effort of distracting devs when a 1.0 push is
on.
-Rob