Translations - Историја измена

Victoria la: /* How to not make translators crazy ;) */

2017-12-28T03:00:29Z

How to not make translators crazy ;)

← Старија измена		Верзија на датум 28. децембар 2017. у 05:00
Ред 49:		Ред 49:
	<pre>sprintf( _("First part of the string, %s second part of the string"), $argument )</pre>		<pre>sprintf( _("First part of the string, %s second part of the string"), $argument )</pre>
	(or the equivalent "dojo.string.substitute" in Javascript)		(or the equivalent "dojo.string.substitute" in Javascript)
	* When translators are going to translate your game, the most difficult task for them is to get the context of the string to be translated. The more the string is a short insignificant string, the more difficult is the task for them. As a rule of thumb, try to avoid insignificant short strings.		* When translators are going to translate your game, the most difficult task for them is to get the context of the string to be translated. The more the string is a short insignificant string, the more difficult is the task for them. As a rule of thumb, try to avoid insignificant short strings. You can also leave a comment on what is the context of the string in the translation program (English to English) if you are the developer of the game.
	* The BGA translation policy is to be flexible on grammar... We prefer to write "player gets 1 coin(s)" than write two versions of the same string for plural and singular - it reduces the number of strings to translate.		* The BGA translation policy is to be flexible on grammar... We prefer to write "player gets 1 coin(s)" than write two versions of the same string for plural and singular - it reduces the number of strings to translate.
	* Instead of writing nice strings like "With the effect of ZZZ, player XXX gets a new YYY", which is very difficult to translate, write strings like "ZZZ: XXX gets YYY".		* Instead of writing nice strings like "With the effect of ZZZ, player XXX gets a new YYY", which is very difficult to translate, write strings like "ZZZ: XXX gets YYY".
			* Use present tense instead of past, i.e. "player gets wood" instead of "player got wood"
			* Avoid using gender specific pronouns, i.e. "player returns card to their hand" instead of "player returns card to his hand"

	== On client side (Javascript) ==		== On client side (Javascript) ==

Victoria la: /* On client side (Javascript) */

2016-08-03T01:53:48Z

On client side (Javascript)

← Старија измена		Верзија на датум 3. август 2016. у 03:53
Ред 63:		Ред 63:

	// Get a string in player's language with parameter:		// Get a string in player's language with parameter:
	var translated = dojo.string.substitute( "You can pick ${p} cards and discard ${d}", {		var translated = dojo.string.substitute( _("You can pick ${p} cards and discard ${d}"), {
	p: 2,		p: 2,
	d: 4		d: 4

Jinnh у 22:43, 23. јун 2014.

2014-06-23T22:43:56Z

← Старија измена		Верзија на датум 24. јун 2014. у 00:43
Ред 115:		Ред 115:
	</pre>		</pre>

	~~<note>~~Pay attention when using 'i18n' argument when translating argument for client : do NOT use same argument for both translation AND key code for client side action (like using 'card_name' to move it on player board as described in the example). It's pretty obvious in the example, but it can be very tricky when translation is made at the end of the development (which is often the case). Use explicit argument name like 'card_name_translated' by example.~~</note>~~		Pay attention when using 'i18n' argument when translating argument for client : do NOT use same argument for both translation AND key code for client side action (like using 'card_name' to move it on player board as described in the example). It's pretty obvious in the example, but it can be very tricky when translation is made at the end of the development (which is often the case). Use explicit argument name like 'card_name_translated' by example.

	'''self::_( "my string to translate" ):'''		'''self::_( "my string to translate" ):'''

Jinnh у 22:43, 23. јун 2014.

2014-06-23T22:43:35Z

← Старија измена		Верзија на датум 24. јун 2014. у 00:43
Ред 114:		Ред 114:
	) );		) );
	</pre>		</pre>

			<note>Pay attention when using 'i18n' argument when translating argument for client : do NOT use same argument for both translation AND key code for client side action (like using 'card_name' to move it on player board as described in the example). It's pretty obvious in the example, but it can be very tricky when translation is made at the end of the development (which is often the case). Use explicit argument name like 'card_name_translated' by example.</note>

	'''self::_( "my string to translate" ):'''		'''self::_( "my string to translate" ):'''

Tilalilalou: /* On server side (PHP) */

2013-05-21T21:36:02Z

On server side (PHP)

← Старија измена		Верзија на датум 21. мај 2013. у 23:36
Ред 124:		Ред 124:
	<pre>		<pre>
	// This will display a translatable red message to the player that just do some wrong action:		// This will display a translatable red message to the player that just do some wrong action:
	throw new ~~feException~~( self::_('You must choose 3 cards')~~, true~~);		throw new BgaUserException( self::_('You must choose 3 cards') );

	// ... notice the use of ~~"true" parameter~~ that ~~signal~~ that this exception is "expected". In theory, all exception that are ~~excepted~~ should be translated.		// ... notice the use of BgaUserException that signals that this exception is "expected". In theory, all exception that are expected should be translated.
	</pre>		</pre>

Ред 139:		Ред 139:
	<pre>		<pre>
	// In material.inc.php, $this->energies[n]['nametr'] has been created with the self::_() method. This we can do this:		// In material.inc.php, $this->energies[n]['nametr'] has been created with the self::_() method. This we can do this:
	throw new ~~feException~~( self::_("To execute this action you need more: ").' '.$this->energies[$resource_id]['nametr']~~, true~~ );		throw new BgaUserException( self::_("To execute this action you need more: ").' '.$this->energies[$resource_id]['nametr'] );
	</pre>		</pre>

Een: /* On client side (Javascript) */

2013-05-10T19:54:03Z

On client side (Javascript)

← Старија измена		Верзија на датум 10. мај 2013. у 21:54
Ред 69:		Ред 69:
	</pre>		</pre>

	~~Note~~: ~~what is also possible~~ to ~~do is~~		'''WARNING:''' in Javascript strings to translate, you should never use '\n', '\t' or such, as it will break the translation bundle and result in all the Javascript translation to fail. In any case, the strings will result in HTML code, and such character codes won't have any impact on the HTML rendering. You should use HTML markup instead.

	== On server side (PHP) ==		== On server side (PHP) ==

Sourisdudesert: /* How to not make translators crazy ;) */

2013-03-06T14:56:14Z

How to not make translators crazy ;)

← Старија измена		Верзија на датум 6. март 2013. у 16:56
Ред 51:		Ред 51:
	* When translators are going to translate your game, the most difficult task for them is to get the context of the string to be translated. The more the string is a short insignificant string, the more difficult is the task for them. As a rule of thumb, try to avoid insignificant short strings.		* When translators are going to translate your game, the most difficult task for them is to get the context of the string to be translated. The more the string is a short insignificant string, the more difficult is the task for them. As a rule of thumb, try to avoid insignificant short strings.
	* The BGA translation policy is to be flexible on grammar... We prefer to write "player gets 1 coin(s)" than write two versions of the same string for plural and singular - it reduces the number of strings to translate.		* The BGA translation policy is to be flexible on grammar... We prefer to write "player gets 1 coin(s)" than write two versions of the same string for plural and singular - it reduces the number of strings to translate.
			* Instead of writing nice strings like "With the effect of ZZZ, player XXX gets a new YYY", which is very difficult to translate, write strings like "ZZZ: XXX gets YYY".

	== On client side (Javascript) ==		== On client side (Javascript) ==

Sourisdudesert: /* How to not make translators crazy ;) */

2013-01-30T14:11:52Z

How to not make translators crazy ;)

← Старија измена		Верзија на датум 30. јануар 2013. у 16:11
Ред 50:		Ред 50:
	(or the equivalent "dojo.string.substitute" in Javascript)		(or the equivalent "dojo.string.substitute" in Javascript)
	* When translators are going to translate your game, the most difficult task for them is to get the context of the string to be translated. The more the string is a short insignificant string, the more difficult is the task for them. As a rule of thumb, try to avoid insignificant short strings.		* When translators are going to translate your game, the most difficult task for them is to get the context of the string to be translated. The more the string is a short insignificant string, the more difficult is the task for them. As a rule of thumb, try to avoid insignificant short strings.
			* The BGA translation policy is to be flexible on grammar... We prefer to write "player gets 1 coin(s)" than write two versions of the same string for plural and singular - it reduces the number of strings to translate.

	== On client side (Javascript) ==		== On client side (Javascript) ==

Sourisdudesert: /* How to not make translators crazy ;) */

2013-01-30T14:09:03Z

How to not make translators crazy ;)

← Старија измена		Верзија на датум 30. јануар 2013. у 16:09
Ред 49:		Ред 49:
	<pre>sprintf( _("First part of the string, %s second part of the string"), $argument )</pre>		<pre>sprintf( _("First part of the string, %s second part of the string"), $argument )</pre>
	(or the equivalent "dojo.string.substitute" in Javascript)		(or the equivalent "dojo.string.substitute" in Javascript)
	* When translators are going to translate your game, the most difficult task for them is to get the context of the string to be translated. The more the string is a short insignificant string, the more difficult is the task for them. As a rule of thumb, try to avoid insignificant short ~~string~~.		* When translators are going to translate your game, the most difficult task for them is to get the context of the string to be translated. The more the string is a short insignificant string, the more difficult is the task for them. As a rule of thumb, try to avoid insignificant short strings.

	== On client side (Javascript) ==		== On client side (Javascript) ==

Sourisdudesert: /* WARNING: how to make sure your strings will be translated */

2013-01-30T14:08:44Z

WARNING: how to make sure your strings will be translated

← Старија измена		Верзија на датум 30. јануар 2013. у 16:08
Ред 38:		Ред 38:
	$not_translated = self::_( $my_string ); // The original string is not bordered by a translator marker => no translation		$not_translated = self::_( $my_string ); // The original string is not bordered by a translator marker => no translation
	$not_translated = self::_( sprintf( "my string with a %s argument", $argument ) ); // Same thing		$not_translated = self::_( sprintf( "my string with a %s argument", $argument ) ); // Same thing
			</pre>

			== How to not make translators crazy ;) ==

	</pre>		* When you need the same string twice, try to reuse exactly the same string (with the same case) to minimize the number of strings.
			* Do not mark as translatable a game element that does not have to be translated (ex: if the name of a monster on a card is "Zzzzz", maybe there's no need to translate it).
			* Words does not come in the same order in each language. Thus, when you have to translate a string with an argument, do not write something like:
			<pre>_("First part of the string, ").$argument.' '._("second part of the string")</pre>
			Write instead:
			<pre>sprintf( _("First part of the string, %s second part of the string"), $argument )</pre>
			(or the equivalent "dojo.string.substitute" in Javascript)
			* When translators are going to translate your game, the most difficult task for them is to get the context of the string to be translated. The more the string is a short insignificant string, the more difficult is the task for them. As a rule of thumb, try to avoid insignificant short string.

	== On client side (Javascript) ==		== On client side (Javascript) ==