Translations - Гісторыя версій

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

2020-10-25T11:11:12Z

On server side (PHP)

← Папярэдн. версія		Версія ад 11:11, 25 кастрычніка 2020
Радок 154:		Радок 154:
	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.		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.

	WARNING: you should NEVER use concatenation with clienttranslate, as it would result in a different string to translate at runtime than the one retrieved statically in the translation system, and so translation would not be applied. If you need to compose a string, use substitution and the i18n parameter (but you also have to pay attention not to compose sentences in a way that is dependent upon the English language specific syntax, or it may be impossible to translate correctly in another language: sometimes, you need multiple full sentences rather than relying on substitution).		'''WARNING:''' you should NEVER use concatenation with clienttranslate, as it would result in a different string to translate at runtime than the one retrieved statically in the translation system, and so translation would not be applied. If you need to compose a string, use substitution and the i18n parameter (but you also have to pay attention not to compose sentences in a way that is dependent upon the English language specific syntax, or it may be impossible to translate correctly in another language: sometimes, you need multiple full sentences rather than relying on substitution).

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

Een: /* On server side (PHP) */ warning on concatenation

2020-10-25T11:10:38Z

On server side (PHP): warning on concatenation

← Папярэдн. версія		Версія ад 11:10, 25 кастрычніка 2020
Радок 135:		Радок 135:
	<pre>		<pre>
	notif="foo"; self::notifyAllPlayers( 'log', clienttraslate(notif)); // BAD		notif="foo"; self::notifyAllPlayers( 'log', clienttraslate(notif)); // BAD
	notif=~~clienttraslate~~("foo"); self::notifyAllPlayers( 'log', notif); // GOOD		notif=clienttranslate("foo"); self::notifyAllPlayers( 'log', notif); // GOOD
	</pre>		</pre>

Радок 153:		Радок 153:

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

			WARNING: you should NEVER use concatenation with clienttranslate, as it would result in a different string to translate at runtime than the one retrieved statically in the translation system, and so translation would not be applied. If you need to compose a string, use substitution and the i18n parameter (but you also have to pay attention not to compose sentences in a way that is dependent upon the English language specific syntax, or it may be impossible to translate correctly in another language: sometimes, you need multiple full sentences rather than relying on substitution).

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

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

2020-10-18T18:15:31Z

On client side (Javascript)

← Папярэдн. версія		Версія ад 18:15, 18 кастрычніка 2020
Радок 99:		Радок 99:

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

			'''ANOTHER WARNING:''' you cannot use this function _() in the javascript object constructor, but you can achieve the same if you use it the setup method

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

Victoria La: /* On server side (PHP) */

2020-09-26T01:59:38Z

On server side (PHP)

← Папярэдн. версія		Версія ад 01:59, 26 верасня 2020
Радок 128:		Радок 128:
	// A game log string with no argument:		// A game log string with no argument:
	self::notifyAllPlayers( 'pickLibraryCards', clienttranslate("Everyone draw cards from his library"), array() );		self::notifyAllPlayers( 'pickLibraryCards', clienttranslate("Everyone draw cards from his library"), array() );
			</pre>

			As a consequence there is no point passing variables to this function, i.e.
			<pre>
			notif="foo"; self::notifyAllPlayers( 'log', clienttraslate(notif)); // BAD
			notif=clienttraslate("foo"); self::notifyAllPlayers( 'log', notif); // GOOD
	</pre>		</pre>

Радок 148:		Радок 154:
	'''self::_( "my string to translate" ):'''		'''self::_( "my string to translate" ):'''

	This function returns a string translated in the language of CURRENT user (~~ie:~~ player who send the request to the server) (be careful, this is NOT the active player).		This function returns a string translated in the language of CURRENT user (i.e. player who send the request to the server) (be careful, this is NOT the active player).

	Most of the time, you don't need to translate strings on server side, except on the following 3 situations:		Most of the time, you don't need to translate strings on server side, except on the following 3 situations:
Радок 154:		Радок 160:

	<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 did some wrong action:
	throw new BgaUserException( self::_('You must choose 3 cards') );		throw new BgaUserException( self::_('You must choose 3 cards') );

Радок 169:		Радок 175:

	<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. Now we can do this:
	throw new BgaUserException( self::_("To execute this action you need more: ").' '.$this->energies[$resource_id]['nametr'] );		throw new BgaUserException( self::_("To execute this action you need more: ").' '.$this->energies[$resource_id]['nametr'] );
	</pre>		</pre>

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

2020-09-26T01:49:49Z

How to not make translators crazy ;)

← Папярэдн. версія		Версія ад 01:49, 26 верасня 2020
Радок 80:		Радок 80:
	* 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"		* 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"		* Avoid using gender specific pronouns, i.e. instead of "player returns card to his hand" use "player returns card to their hand" or just avoid using it, i.e. "player picks up the card"

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

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

2020-06-20T12:44:06Z

How to not make translators crazy ;)

← Папярэдн. версія		Версія ад 12:44, 20 чэрвеня 2020
Радок 72:		Радок 72:
	* 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).		* 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:		* 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>		<pre>self::_("First part of the string, ").$argument.' '.self::_("second part of the string")</pre>
	Write instead:		Write instead:
	<pre>sprintf( _("First part of the string, %s second part of the string"), $argument )</pre>		<pre>sprintf( self::_("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. 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.		* 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.

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

2020-06-20T12:43:12Z

WARNING: how to make sure your strings will be translated

← Папярэдн. версія		Версія ад 12:43, 20 чэрвеня 2020
Радок 59:		Радок 59:
	var mystring_translated = _("my string"); // JS		var mystring_translated = _("my string"); // JS
	$mystring_translated = self::_("my string"); // PHP		$mystring_translated = self::_("my string"); // PHP
	$mystring_translated = sprintf( _("my string with an %s argument"), $argument ); // PHP		$mystring_translated = sprintf( self::_("my string with an %s argument"), $argument ); // PHP

	// Examples: the following strings WILL NOT be translated:		// Examples: the following strings WILL NOT be translated:

Cpasbanal: /* On server side (PHP) */ minor typo on transate -> translate

2020-05-10T13:56:39Z

On server side (PHP): minor typo on transate -> translate

← Папярэдн. версія		Версія ад 13:56, 10 мая 2020
Радок 136:		Радок 136:

	self::notifyAllPlayers( 'winPoints', clienttranslate('${card_name}: ${player_name} gains ${points} point(s)'), array(		self::notifyAllPlayers( 'winPoints', clienttranslate('${card_name}: ${player_name} gains ${points} point(s)'), array(
	'i18n' => array( 'card_name' ), // <===== We specify here that "card_name" argument must be ~~transate~~		'i18n' => array( 'card_name' ), // <===== We specify here that "card_name" argument must be translated
	'player_id' => $player_id,		'player_id' => $player_id,
	'player_name' => self::getActivePlayerName(),		'player_name' => self::getActivePlayerName(),

Tutchek: Added navigation

2020-04-15T21:05:38Z

Added navigation

← Папярэдн. версія		Версія ад 21:05, 15 красавіка 2020
Радок 1:		Радок 1:
			{{Studio_Framework_Navigation}}


	Using BGA Studio, the game you create is ready to be translated to each language by the BGA community. To make this possible, you only need to specify which string must be translated and how to combine them.		Using BGA Studio, the game you create is ready to be translated to each language by the BGA community. To make this possible, you only need to specify which string must be translated and how to combine them.

Een: /* What rules should I follow for the original English strings? */

2019-04-06T19:18:45Z

What rules should I follow for the original English strings?

← Папярэдн. версія		Версія ад 19:18, 6 красавіка 2019
Радок 36:		Радок 36:
	** We can tolerate a dot or no dot (but it should be consistent inside the game) for:		** We can tolerate a dot or no dot (but it should be consistent inside the game) for:
	*** isolated tooltip / isolated small sentence		*** isolated tooltip / isolated small sentence
	*** game log		*** game log (no dot is usually preferable)
	*** error messages (except if more than one sentence in the error message => final dot mandatory in this case)		*** error messages (except if more than one sentence in the error message => final dot mandatory in this case)