| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
(use first default key that resolves to a translation). this might, depending
on the backend implementation save some expensive lookups (like db lookups)
|
|
|
|
|
|
| |
standarize on. Also, in future this place can be used for data/code that's
not literally translations but conceptually belongs to the locale (like
custom pluralization algorithms etc.).
|
|
|
|
|
|
|
|
|
| |
client libraries to the backend: clients now can pass a block to
backend#populate which can contain code to load and register translations.
This makes sense for backends that persist their translations (e.g. to db)
so the repeated loading and passing of translations throughout the server
startup would be wasted resources.
|
|
|
|
| |
because it overwrites existing translations
|
|
|