Actually, UI scripts should not use directly pgettext, but rather the iface or toolti...
authorBastien Montagne <montagne29@wanadoo.fr>
Sun, 10 Feb 2013 10:29:38 +0000 (10:29 +0000)
committerBastien Montagne <montagne29@wanadoo.fr>
Sun, 10 Feb 2013 10:29:38 +0000 (10:29 +0000)
commitd0f4a2396b38c122b7e56de83532515ae8fa4381
treec10f9983e987090f73ce8a39e368f5d265d670ac
parent3b8a0f3d674a0da3bb17cbda30f0a2dc19a40e4f
Actually, UI scripts should not use directly pgettext, but rather the iface or tooltip variants. Added those to bpy.app.translations, and used pgettext_iface.

(Did not add those when I created that module, because I did not thought we would actually need them in usual UI code, but turned out I was wrong).

Also made some optimizations in those py gettext funcs, when i18n is disabled at build time, no need to do pyobject -> cstring -> pyobject conversions!.
release/scripts/startup/bl_ui/properties_data_modifier.py
release/scripts/startup/bl_ui/properties_material.py
release/scripts/startup/bl_ui/properties_particle.py
release/scripts/startup/bl_ui/properties_physics_fluid.py
release/scripts/startup/bl_ui/space_clip.py
release/scripts/startup/bl_ui/space_image.py
release/scripts/startup/bl_ui/space_sequencer.py
release/scripts/startup/bl_ui/space_text.py
release/scripts/startup/bl_ui/space_userpref.py
release/scripts/startup/bl_ui/space_userpref_keymap.py
source/blender/python/intern/bpy_app_translations.c