+1 If _ stands for a function that transparently routes to lazy_gettext where applicable (if reallistically doable).
As i've mentioned the first time this was brought up, it would make the interface more consistent and free users from understanding widget/gettext internals: "Just use _ when you wan't your text translated". As a side effect, pygettext will always find all "translatable" literals. Jonathan LaCour wrote: > -1 > > I think you will find that a lot of people find this objectionable, > including myself. This is the type of thing that isn't very > difficult for you to do on your own by putting a single line at the > top of your modules whenever you need to do I18N. _ Already stands for "gettext". The problem is that it' can't be used outside a request (such as in widget initialization) as there's no session to pull the locale from, this is when you need to use lazy_gettext. Alberto
