Isn't there a broader problem than just django.forms? Now that Django
1.0 seems to stand on the XHTML side, it encourages re-usable app
authors to generate XHTML instead of HTML in their default templates
as well as in any markup their apps might be generating
programmatically.
I have to admit th
Here's some food for thought on the subject of HTML 4.01 in Django (as
it's been discussed a lot before):
James Bennet brought up the HTML4 argument on the Django developers
list some time ago:
http://groups.google.com/group/django-developers/browse_thread/thread/a233bb5b3b39e147/7c9bf930a533345b
On Thu, 2009-01-29 at 15:18 +0100, Gertjan Klein wrote:
> Malcolm Tredinnick wrote:
>
> >On Wed, 2009-01-28 at 14:33 +0100, Gertjan Klein wrote:
> >> Malcolm Tredinnick wrote:
> >>
> >> I disagree. When I develop web pages (using Django or otherwise) I use
> >> the Firefox HTML validator extensi
On Thu, 2009-01-29 at 06:36 -0800, Andrew Ingram wrote:
> On Jan 29, 2:18 pm, Gertjan Klein wrote:
> > This payment thing comes up regularly here, and pollutes the discussion.
> > I have been using Django for a while, and found it to have good things
> > and downsides (both IMHO). I have not even
On Jan 29, 2:18 pm, Gertjan Klein wrote:
> This payment thing comes up regularly here, and pollutes the discussion.
> I have been using Django for a while, and found it to have good things
> and downsides (both IMHO). I have not even critisized Django here (yet
> ;)), just expressed mild curiousi
Malcolm Tredinnick wrote:
>On Wed, 2009-01-28 at 14:33 +0100, Gertjan Klein wrote:
>> Malcolm Tredinnick wrote:
>>
>> I disagree. When I develop web pages (using Django or otherwise) I use
>> the Firefox HTML validator extension. This helps me write
>> standards-compliant HTML -- a big red cross
On Wed, 2009-01-28 at 14:33 +0100, Gertjan Klein wrote:
> Malcolm Tredinnick wrote:
>
> >In HTML, the requirement for errors of this form ( instead of
> >), is that the parser *must* recover in a way that forces it to
> >treat it as "" -- it has to ignore the invalid characters and
> >recover in
Malcolm Tredinnick wrote:
>In HTML, the requirement for errors of this form ( instead of
>), is that the parser *must* recover in a way that forces it to
>treat it as "" -- it has to ignore the invalid characters and
>recover in a particular, well-defined fashion.
Do you have a reference for tha
On Mon, 2009-01-26 at 10:35 -0800, Ty wrote:
> Thanks for the link.
> I'm supprised there nothing "built-in" to allow this. Django's
> essentally pushing you to use XHTML over HTML.
>
> Not really a big deal though, I suppose.
Precisely.
In XHTML, validity errors must be handled by not parsing
Thanks for the link.
I'm supprised there nothing "built-in" to allow this. Django's
essentally pushing you to use XHTML over HTML.
Not really a big deal though, I suppose. I'm just starting the project
out so it won't take much to convert the whole page to XHTML. I'll
probably just go that route.
On Mon, Jan 26, 2009 at 4:23 PM, Ty wrote:
>
> I write HTML 4.01 strict documents and I'm using the django.forms form-
> handling library.
>
> Currently when printing input fields on the template, the output
> includes the ending slash: "".
>
> Is there any way, other then manually writing the in
I write HTML 4.01 strict documents and I'm using the django.forms form-
handling library.
Currently when printing input fields on the template, the output
includes the ending slash: "".
Is there any way, other then manually writing the input field to the
template, to get these variables to outpu
12 matches
Mail list logo
