A BIG +1 for me
On 29 mar, 16:34, "James Bennett" <[EMAIL PROTECTED]> wrote:
> On 3/29/07, Ted <[EMAIL PROTECTED]> wrote:
>
> > Were I work we have had to do this very thing to support I18N in our
> > forms. Something as simple as a ":" is not a given. Maybe I want a
> > " :" instead? This could
Jonas Maurus wrote:
>> I think he was suggesting in the form, not each field:
I did :)
> I see that this would allow Django to be backwards-compatible by
> introducing this new parameter, so I could go for that because I think
> backwards-compatibility is very important. I still disagree with
On 3/29/07, Ted <[EMAIL PROTECTED]> wrote:
> Were I work we have had to do this very thing to support I18N in our
> forms. Something as simple as a ":" is not a given. Maybe I want a
> " :" instead? This could be a form parameter or even a locale setting.
FWIW I think the ideal would be for the
Were I work we have had to do this very thing to support I18N in our
forms. Something as simple as a ":" is not a given. Maybe I want a
" :" instead? This could be a form parameter or even a locale setting.
My 2 cents,
Ted
On Mar 29, 9:10 am, "Todd O'Bryan" <[EMAIL PROTECTED]> wrote:
> On Thu,
I think the OP is correct, if you want the label to end with a
colon ... then add the colon to the label. It doesn't get any simpler
than that. Any other solution just gets in the way.
i.
--~--~-~--~~~---~--~~
You received this message because you are
On Thu, 2007-03-29 at 13:02 +, Jonas Maurus wrote:
> > I think there are lots of situations where you need to normalize the
> > labels with some string. Why not just make it an optional parameter to
> > the Form class with a default value.. maybe ":"?
> >
> > Rune
>
> so that would make
>
On Mar 29, 2:07 pm, "bromer" <[EMAIL PROTECTED]> wrote:
> On Mar 29, 1:38 pm, "Jonas Maurus" <[EMAIL PROTECTED]> wrote:
>
> > Also, there simply are languages where this punctuation doesn't make
> > sense. Adding it automatically then telling international users that
> > they have to write a lot
On Mar 29, 1:38 pm, "Jonas Maurus" <[EMAIL PROTECTED]> wrote:
> Also, there simply are languages where this punctuation doesn't make
> sense. Adding it automatically then telling international users that
> they have to write a lot more code, because english developers wanted
> to save one
Perhaps the user-mailinglist is a better place for this, but anyway...
> I don't think the library should add text like that, what do you
> think?
I really think it should. The methods defined in the form are some
default, that can be used if appropriate. If not newforms is usable in
any way
On Mar 28, 9:03 am, "vfoley" <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I rewrote the forms portion of an application by using newforms. It's
> pretty nice, however there is something extremely annoying: newforms
> automatically adds a colon after labels (hopefully, my formatting is
> correct):
Hello,
I rewrote the forms portion of an application by using newforms. It's
pretty nice, however there is something extremely annoying: newforms
automatically adds a colon after labels (hopefully, my formatting is
correct):
Out[58]: class ExampleForm(forms.Form):
name =
11 matches
Mail list logo
