translationstring
translationstring copied to clipboard
Pylons
A library used for internationalization (i18n) duties related to translation.
The docstring for translationstring is missing a corresponding term in the Glossary. See: https://github.com/Pylons/translationstring/blob/master/translationstring/__init__.py#L50
`translate()` should support `context` keyword analogically to how it supports `domain` keyword. Till then one can workaround this by wrapping string to translate in extra `TranslationString` like so: `translate(TranslationString(tstring, context='some_ctx'))`
Pluralizer ignores by default the domain of TranslationString that is passed in, whereas Translator doesn't. This is rather silly, since if a TranslationString is passed in to Pluralizer instead of...
I programmatically build up TranslationStrings based on what the content of the message should be. (A common pattern when building up for example an error message based on several conditions...
I've noticed that if I interpolate translated strings into translated strings - it doesn't work. This happens something like this: ``` warning = _("Missing correct answers") object_id = "fnord" _("${warning}...
- When a translation string is coerced to its native string type (i.e. the built-in string or unicode type), the default translation (or msgid if not applicable) is returned with...
translate() has context=None in the method signature but it is not used. If it is passed to translator(), then translator would not need to do get_current_request() (not green thread safe)...
hi pylons team, i much prefer python's `string.format()` string templating rules than the templating provided by `translationstring.TranslationString.interpolate()`, and have monkey-patched translationstring to use that instead for my projects. i'd like...
seems it is not possible to use $ just before interpolation value, something like: $${val}
