L20n/Features/Entities vs Variables - Revision history

Jbeatty at 20:04, 7 August 2012

2012-08-07T20:04:38Z

← Older revision		Revision as of 20:04, 7 August 2012
Line 1:		Line 1:
	[[Category:L20n Features\|Entities vs Variables]]		[[Category:L20n Features\|Entities vs Variables]][[Category:L20n]]

	== goal ==		== goal ==

StasM at 16:48, 18 June 2012

2012-06-18T16:48:38Z

← Older revision		Revision as of 16:48, 18 June 2012
Line 1:		Line 1:
	[[Category:L20n Features\|~~{{SUBPAGENAME}}~~]]		[[Category:L20n Features\|Entities vs Variables]]

	== goal ==		== goal ==

StasM at 16:47, 18 June 2012

2012-06-18T16:47:38Z

← Older revision		Revision as of 16:47, 18 June 2012
Line 1:		Line 1:
	[[Category:L20n Features]]		[[Category:L20n Features\|{{SUBPAGENAME}}]]

	== goal ==		== goal ==

StasM at 16:43, 18 June 2012

2012-06-18T16:43:18Z

← Older revision		Revision as of 16:43, 18 June 2012
Line 1:		Line 1:
			[[Category:L20n Features]]

	== goal ==		== goal ==
	we need to be able to recognize variables from a developer from entities located in resources		we need to be able to recognize variables from a developer from entities located in resources

StasM at 12:14, 19 April 2012

2012-04-19T12:14:21Z

← Older revision		Revision as of 12:14, 19 April 2012
Line 6:		Line 6:
	We decided to separate the expression syntax used to call to other entities from the syntax used to reference developer provided variables.		We decided to separate the expression syntax used to call to other entities from the syntax used to reference developer provided variables.

	~~Developer provided variables (either from the context or a call)~~ are referenced by a name, no changes here. But in order to reference ~~another entity,~~ a prefix ":" has to be used. It looks like this:		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:

	<pre>		<pre>
Line 17:		Line 17:
	>		>

	<about "About {{ :brandName.nominative }}">		<about "About {{ brandName.nominative }}">
	<update[:brandName:_gender.win] {		<update[brandName.._gender.win] {
	male: "{{ :brandName }} has been updated. The update took {{ updateTime }} seconds."		male: "{{ brandName }} has been updated. The update took {{ $updateTime }} seconds."
	female: "{{ :brandName:accesskey.mac }}"		female: "{{ brandName..accesskey.mac }}"
	}>		}>
	</pre>		</pre>

	The rationale here is that we expect localizers to reference developer provided variables much more often, while referencing other entities (except for a brandName like cases) will be rather an exception.

	~~For computed calls, the syntax will look like this:~~
	~~<pre>~~
	/*
	~~For variables:~~
	~~var1 - "accesskey"~~
	~~var2 - "entity2"~~
	~~var3 - "win"~~
	*/

	~~<entity1 "value"~~
	~~accesskey: "c">~~

	~~<entity2 "value">~~

	~~<entity3 {~~
	~~win: "test",~~
	~~lin: "test2"~~
	}>
	/*
	~~This will compute to "Hello c and value and test"~~
	*/
	~~<title "Hello {{ :entity1:[var1] }} and {{ :[var2] }} and {{ :entity3[var3] }}">~~
	~~</pre>~~

	== status ==		== status ==

StasM at 14:36, 5 March 2012

2012-03-05T14:36:28Z

← Older revision		Revision as of 14:36, 5 March 2012
Line 52:		Line 52:
	== status ==		== status ==
	* open		* open
	* stas, gandalf - ok		* stas - ok
	* pike - ?		* gandalf - ok
			* pike - ok

StasM: Created page with "== 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..."

2012-03-01T14:02:43Z

Created page with "== 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..."

New page

== 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.

Developer provided variables (either from the context or a call) are referenced by a name, no changes here. But in order to reference another entity, a prefix ":" has to be used. It looks like this:

<pre>
<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 }}"
}>
</pre>

The rationale here is that we expect localizers to reference developer provided variables much more often, while referencing other entities (except for a brandName like cases) will be rather an exception.

For computed calls, the syntax will look like this:
<pre>
/*
For variables:
var1 - "accesskey"
var2 - "entity2"
var3 - "win"
*/

<entity1 "value"
accesskey: "c">

<entity2 "value">

<entity3 {
win: "test",
lin: "test2"
}>
/*
This will compute to "Hello c and value and test"
*/
<title "Hello {{ :entity1:[var1] }} and {{ :[var2] }} and {{ :entity3[var3] }}">
</pre>

== status ==
* open
* stas, gandalf - ok
* pike - ?