Warning: This page has not been updated in over over a year and may be outdated or deprecated.
development:architecture:localization
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
development:architecture:localization [2024/01/10 13:55] – [Translate Function] demiankatz | development:architecture:localization [2024/01/10 13:56] (current) – [Translate Function] demiankatz | ||
---|---|---|---|
Line 14: | Line 14: | ||
* Many of the translated strings in the language files are simply chunks of English text. However, more recent additions are represented as shorter abstract keys (i.e. " | * Many of the translated strings in the language files are simply chunks of English text. However, more recent additions are represented as shorter abstract keys (i.e. " | ||
* Starting with VuFind® 2.4, a convenient [[https:// | * Starting with VuFind® 2.4, a convenient [[https:// | ||
- | * The translate function can accept an array of values to insert into the translation string in order to include variables inside the translation (e.g. numbers). Starting with VuFind® 10.0, an additional argument can be added to the translate function to override the simple search-and-replace value insertion mechanism with the more complex ICU MessageFormatter syntax. See [[https:// | + | * The translate function can accept an array of values to insert into the translation string in order to include variables inside the translation (e.g. numbers). Placeholders for values are generally surrounded by double-percent-signs (e.g. < |
===== Formatting Language Files ===== | ===== Formatting Language Files ===== |
development/architecture/localization.txt · Last modified: 2024/01/10 13:56 by demiankatz