3 ms·
This has been established practise in Zope, Plone et al for many years. http://developer.plone.org/i18n/internationalisation.html#marking-translatable-strings-
by thruflo 13y ago
This has been established practise in Zope, Plone et al for many years.
http://developer.plone.org/i18n/internationalisation.html#marking-translatable-strings-in-python http://developer.plone.org/i18n/internationalisation.html#ma...
- dalke 13y agoIt's standard Python practice since Martin von Löwis's work in support for internationalization, which he presented at the IPC6 Python conference in 1997. Quoting from http://www.python.org/workshops/1997-10/proceedings/loewis.html http://www.python.org/workshops/1997-10/proceedings/loewis.h... : > Here are several ways of producing the message catalogs. This is the one suggested by the GNU gettext documentation. First, all translatable message strings in the source code must be marked. In order to disturb readability as little as possible, the wrapper function around each string should be called _ (underscore). This use of the underscore usually does not interfere with its meaning in the interactive mode. A gettextized module would then begin with import intl _=intl.gettext