L20n/Features/Entities vs Variables: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
[[Category:L20n Features|Entities vs Variables]] | [[Category:L20n Features|Entities vs Variables]][[Category:L20n]] | ||
== goal == | == goal == | ||
Latest revision as of 20:04, 7 August 2012
goal
we need to be able to recognize variables from a developer from entities located in resources
example
We decided to separate the expression syntax used to call to other entities from the syntax used to reference developer provided variables.
Entities are referenced by a name, no changes here. But in order to reference a developer provided variable (either from the context or a call) a prefix "$" has to be used. It looks like this:
<brandName {
nominative: "Firefox",
genitive: "Firefoksa"
}
_gender: { mac: 'male', win: 'female' }
accesskey: { mac: 'F', win: 'C'}
>
<about "About {{ brandName.nominative }}">
<update[brandName.._gender.win] {
male: "{{ brandName }} has been updated. The update took {{ $updateTime }} seconds."
female: "{{ brandName..accesskey.mac }}"
}>
status
- open
- stas - ok
- gandalf - ok
- pike - ok