On 1/13/06, Jorge Godoy <[EMAIL PROTECTED]> wrote: > And then I have this on my method: > > "data_envio":validators.DateConverter(month_style='dd/mm/yyyy'),
Ahh... So it looks like the first thing needed is a date validator that handles locales reasonably and possibly lets you override the style for a locale. That validator would be the default on the widget. > So, data_envio on my Python code contains an mx.DateTime (or > datetime.datetime) made up from the user input. > > If I could change 'ifFormat' on the template based on what locale I'm using (I > can and probably will do that using some variable to represent this format > until I find some time to contribute more with patches for this specific > thing) problem would be solved. Of course, I'd have to use the respective > language calendar JavaScript as well... if that new validator could provide format info in such a way that the widget could use it, then we don't have to worry about that format being repeated in multiple places. > Since widget had troubles -- the bug about restarts said something about it -- > I was avoiding using widgets. But for this new project I am really willing to > use them since it will make a lot of my job easier. I *think* that problem is fixed. It's worth trying. > ยน "Data" means "Date". "Envio" means "send", so this is for some > sending date... Just to let you all know... I certainly wouldn't have guessed that "envio" means send. I just know the little bit of Spanish and French that one picks up in American public schools, plus a little more German from classes in college (more than a decade ago, so you can probably imagine how much I still remember!) One wouldn't want me to do any translations on an app. I'd be worse than Google! Kevin
