Hi, we are working on this i18n for JS at the moment. It was included in the additionnal functionnalities on error (it was meant to be there, but was not applied to the branch before the release). It will definitely be part of the 1.0.4 release that is coming. I don't want to give a public date yet so we have time to do things properly, but a beta cycle should be fairly quick to come.
For the moment please look at ticket http://trac.turbogears.org/ticket/1405 you will find a patch and some information on how to use it. You will also find a pointer to a discussion in this mailing list concerning the proposal (I know you participated to this discussion at some point). Hope it helps you a bit. Florent. On 8/15/07, W-Mark Kubacki <[EMAIL PROTECTED]> wrote: > Hi all, > > I experience some strange issues with i18n support in TurboGears. It is about > gettext and TG's equivalent lazytext (let's call it so). > > 1. TG's lazytext does not work in validators (errors with nosetests/doctests), > 2. therefore I had to 'from gettext import gettext as _'. Unfortunately, then > 'tg-admin i18n...' does not collect the strings to be translated. (But > they are translated properly if having been previuosly collected.) > 3. I18N with JS files is announced to work with TG 1.0.3.2. > But, how to utilize it? I didn't find any documentation and _("") does > not work there, too. > > A note: > I suspect TG's lazytext bein responsible for exceptions if both strings are > Unicode (e.g., chinese text): _("%s and me") % u'ni3' (<- in chinese, of > course) > > Thanks for your help in advance! > W-Mark Kubacki > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears?hl=en -~----------~----~----~----~------~----~------~--~---
