On 11-08-2005, at 11:39, Nebojša Đorđević - nesh wrote:
set_translation(languages, app_name=None)
-----------------------------------------
Sets *global* translation via get_translation()
current_translation()
---------------------
Returns current *global* translation
*gettext functions
------------------
Alias to same functions in *global* translation object
Update 2:
All global translation functions and variables are not needed, if I'm
not mistaking, only places for outputting i18n texts are inside
functions that already receives translation via request object
(handler functions), see previous post about middleware i18n class.
Any translatable texts which are not inside handler functions (i.e.
validator messages) will be only marked as translatable strings
(using xpot syntax ''"foo" or ""'foo') and translated when output is
done inside handlers or templates.
This way requires less changes to existing code (not taking into
account marking translation strings and adding calls to translate
output in view functions).
I'll be sending patches soon.
---
Nebojša Đorđević - nesh
Studio Quattro - Niš - SCG
