L20n/Features/Globals namespace: Difference between revisions
Jump to navigation
Jump to search
(Created page with "== goal == variables that will be defined by the system should be available without collisions with user or developer defined values. == example == We decided to keep "globals...") |
No edit summary |
||
| (2 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
[[Category:L20n Features|{{SUBPAGENAME}}]][[Category:L20n]] | |||
== goal == | == goal == | ||
| Line 17: | Line 19: | ||
* screenWidth | * screenWidth | ||
* languageCode | * languageCode | ||
* | * time | ||
The <code>time</code> global may allow the localizer to adjust the message to the time of the day (which often depends on it in case of greetings). | |||
== status == | == status == | ||
accepted for inclusion | accepted for inclusion | ||
Latest revision as of 20:05, 7 August 2012
goal
variables that will be defined by the system should be available without collisions with user or developer defined values.
example
We decided to keep "globals" in a separate namespace. Current proposal is to mark them with "@" sign as a prefix.
<title[@os] {
*win: "Settings",
lin: "Preferences",
mac: "Settings"
}>
Other examples of global values might be:
- os
- screenWidth
- languageCode
- time
The time global may allow the localizer to adjust the message to the time of the day (which often depends on it in case of greetings).
status
accepted for inclusion