Translations - ประวัติรุ่นแก้ไข

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?

←รุ่นแก้ไขก่อนหน้า		รุ่นแก้ไขเมื่อ 21:18, 6 เมษายน 2562
บรรทัดที่ 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)

Een: Rules for original English strings

2019-03-15T15:29:00Z

Rules for original English strings

@@ บรรทัดที่ 14: / บรรทัดที่ 14: @@
 Every text that can be visible by the player when the game is running normally. This includes tooltips, texts on cards, error messages, ...
-This does NOT include error messages that are not supposed to happened (unexpected errors).
+This does NOT include error messages that are not supposed to happen (unexpected errors).
 == Focus on translating notifications ==

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

2017-12-28T03:00:29Z

How to not make translators crazy ;)

←รุ่นแก้ไขก่อนหน้า		รุ่นแก้ไขเมื่อ 05:00, 28 ธันวาคม 2560
บรรทัดที่ 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)

←รุ่นแก้ไขก่อนหน้า		รุ่นแก้ไขเมื่อ 03:53, 3 สิงหาคม 2559
บรรทัดที่ 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 มิถุนายน 2557

2014-06-23T22:43:56Z

←รุ่นแก้ไขก่อนหน้า		รุ่นแก้ไขเมื่อ 00:43, 24 มิถุนายน 2557
บรรทัดที่ 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 มิถุนายน 2557

2014-06-23T22:43:35Z

←รุ่นแก้ไขก่อนหน้า		รุ่นแก้ไขเมื่อ 00:43, 24 มิถุนายน 2557
บรรทัดที่ 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)

←รุ่นแก้ไขก่อนหน้า		รุ่นแก้ไขเมื่อ 23:36, 21 พฤษภาคม 2556
บรรทัดที่ 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)

←รุ่นแก้ไขก่อนหน้า		รุ่นแก้ไขเมื่อ 21:54, 10 พฤษภาคม 2556
บรรทัดที่ 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 ;)

←รุ่นแก้ไขก่อนหน้า		รุ่นแก้ไขเมื่อ 16:56, 6 มีนาคม 2556
บรรทัดที่ 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 ;)

←รุ่นแก้ไขก่อนหน้า		รุ่นแก้ไขเมื่อ 16:11, 30 มกราคม 2556
บรรทัดที่ 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) ==