Cherry Picker - Revision history

Olibouban: /* Example 1-sending subset of all files for a locale */

2019-05-08T22:38:17Z

Example 1-sending subset of all files for a locale

← Older revision		Revision as of 22:38, 8 May 2019
Line 35:		Line 35:
	<locale code="fr">		<locale code="fr">
	<files-include>		<files-include>
	<include file="/locales/~~file1_de~~.json"/>		<include file="/locales/file1_fr.json"/>
	<include file="/locales/~~file2_de~~.json"/>		<include file="/locales/file2_fr.json"/>
	<include file="/locales/~~file3_de~~.json"/>		<include file="/locales/file3_fr.json"/>
	<include file="/locales/~~file4_de~~.json"/>		<include file="/locales/file4_fr.json"/>
	<include file="/locales/~~file5_de~~.json"/>		<include file="/locales/file5_fr.json"/>
	<include file="/locales/~~file6_de~~.json"/>		<include file="/locales/file6_fr.json"/>
	<include file="/locales/~~file7_de~~.json"/>		<include file="/locales/file7_fr.json"/>
	<include file="/locales/~~file8_de~~.json"/>		<include file="/locales/file8_fr.json"/>
	<include file="/locales/~~file9_de~~.json"/>		<include file="/locales/file9_fr.json"/>
	</files-include>		</files-include>
	</locale>		</locale>

Llawson: /* Example 2 */

2017-09-14T16:19:33Z

Example 2

← Older revision		Revision as of 16:19, 14 September 2017
Line 54:		Line 54:
	In this example, if the <code>locales</code> directory has 10 files, only 9 are sent for French and German; The other locales in this LRM project are not affected.		In this example, if the <code>locales</code> directory has 10 files, only 9 are sent for French and German; The other locales in this LRM project are not affected.

	== Example 2 ==		== Example 2-preventing files from being prepped for a locale ==
	Now let's say that for Chinese you do not want to send any files. You could write a Cherry Picker like:		Now let's say that for Chinese you do not want to send any files. You could write a Cherry Picker like:
	<pre>		<pre>

Llawson: /* Example 1 */

2017-09-14T16:19:16Z

Example 1

← Older revision		Revision as of 16:19, 14 September 2017
Line 11:		Line 11:
	* The cherry picking is done per locale		* The cherry picking is done per locale

	== Example 1 ==		== Example 1-sending subset of all files for a locale ==
	For instance, let's say that you want to send 9 files out of 10 to translate into French and German and all ten for the remaining locales. You could write a Cherry Picker like:		For instance, let's say that you want to send 9 files out of 10 to translate into French and German and all ten for the remaining locales. You could write a Cherry Picker like:
	<pre>		<pre>
Line 52:		Line 52:
	</pre>		</pre>

	In this example, if the <code>locales</code> directory has 10 files, only 9 are sent for French and German; The other locales in this LRM project are not affected.		In this example, if the <code>locales</code> directory has 10 files, only 9 are sent for French and German; The other locales in this LRM project are not affected.

	== Example 2 ==		== Example 2 ==

Llawson at 16:17, 14 September 2017

2017-09-14T16:17:55Z

← Older revision		Revision as of 16:17, 14 September 2017
Line 1:		Line 1:
			= Cherry Picker =
	The idea behind the cherry picker is that you can ''ignore'' file(s) (not keys) for specific locales or ''include'' files for specific locales.		The idea behind the cherry picker is that you can ''ignore'' file(s) (not keys) for specific locales or ''include'' files for specific locales.

Llawson at 23:03, 13 September 2017

2017-09-13T23:03:05Z

← Older revision		Revision as of 23:03, 13 September 2017
Line 1:		Line 1:
	The idea behind the cherry picker is that you can 'ignore' file(s) (not keys) for specific locales~~. Say you have ten~~ files ~~and you want to send 9 files to translate into French and German but not Japanese and all ten to all~~ locales. ~~You can.~~		The idea behind the cherry picker is that you can ''ignore'' file(s) (not keys) for specific locales or ''include'' files for specific locales.
	'''This feature sometimes lead to misunderstanding so use it with care''' and remember to remove/rename the cherry picker file when done cherry picking!
			'''This feature sometimes lead to misunderstanding so use it with care''' and remember to edit/remove/rename the cherry picker file when done cherry picking!

	==The mechanics:==		==The mechanics:==

	* Create a file under the project configuration directory (<code><HOME>/Lingoport_Data/L10nStreamlining/GroupName/projects/ProjectName/config</code>) named '''<code>config_file_cherry_picker.xml</code>'''. There is a template in '''<code> <HOME>/Lingoport_Data/L10nStreamlining/config </code>'''		* Create a file under the project configuration directory (<code><HOME>/Lingoport_Data/L10nStreamlining/GroupName/projects/ProjectName/config</code>) named '''<code>config_file_cherry_picker.xml</code>'''. There is a template in '''<code> <HOME>/Lingoport_Data/L10nStreamlining/config </code>'''
	* Edit that file to say what file to include for what locale in the next prep kit. If you have a 'fake' file, no files will be sent.		* Edit that file to say what file to include for what locale in the next prep kit. If you have a 'fake' file, no files will be sent for that locale.
			* The locale code must match one of your target locales
			* The cherry picking is done per locale

	== Example 1 ==		== Example 1 ==

Rdaly: /* The mechanics: */

2017-01-26T18:11:20Z

The mechanics:

← Older revision		Revision as of 18:11, 26 January 2017
Line 4:		Line 4:
	==The mechanics:==		==The mechanics:==

	* Create a file under the project configuration directory (<code>~/Lingoport_Data/L10nStreamlining/GroupName/projects/ProjectName/config</code>) named '''<code>config_file_cherry_picker.xml</code>'''. There is a template in '''<code> <HOME>/Lingoport_Data/L10nStreamlining/config </code>'''		* Create a file under the project configuration directory (<code><HOME>/Lingoport_Data/L10nStreamlining/GroupName/projects/ProjectName/config</code>) named '''<code>config_file_cherry_picker.xml</code>'''. There is a template in '''<code> <HOME>/Lingoport_Data/L10nStreamlining/config </code>'''
	* Edit that file to say what file to include for what locale in the next prep kit. If you have a 'fake' file, no files will be sent.		* Edit that file to say what file to include for what locale in the next prep kit. If you have a 'fake' file, no files will be sent.

Rdaly: /* The mechanics: */

2017-01-26T18:10:58Z

The mechanics:

← Older revision		Revision as of 18:10, 26 January 2017
Line 4:		Line 4:
	==The mechanics:==		==The mechanics:==

	* Create a file under the project configuration directory named <code>config_file_cherry_picker.xml</code>.		* Create a file under the project configuration directory (<code>~/Lingoport_Data/L10nStreamlining/GroupName/projects/ProjectName/config</code>) named '''<code>config_file_cherry_picker.xml</code>'''. There is a template in '''<code> <HOME>/Lingoport_Data/L10nStreamlining/config </code>'''
	* Edit that file to say what file to include for what locale in the next prep kit. If you have a 'fake' file, no files will be sent.		* Edit that file to say what file to include for what locale in the next prep kit. If you have a 'fake' file, no files will be sent.

Olibouban at 19:59, 20 June 2016

2016-06-20T19:59:03Z

← Older revision		Revision as of 19:59, 20 June 2016
Line 69:		Line 69:

	In this example, the cherry picker is set for the <code>zh-Hans</code> locale. It states that for that locale, the file to be included is a fake file, <code>fake_zh_Hans.json</code>. Since that file does not exist, no files will be sent for translation. Sending resource bundles for the other locales in the LRM project are not affected.		In this example, the cherry picker is set for the <code>zh-Hans</code> locale. It states that for that locale, the file to be included is a fake file, <code>fake_zh_Hans.json</code>. Since that file does not exist, no files will be sent for translation. Sending resource bundles for the other locales in the LRM project are not affected.

	~~Here is another example:~~

Olibouban at 19:58, 20 June 2016

2016-06-20T19:58:45Z

← Older revision		Revision as of 19:58, 20 June 2016
Line 2:		Line 2:
	'''This feature sometimes lead to misunderstanding so use it with care''' and remember to remove/rename the cherry picker file when done cherry picking!		'''This feature sometimes lead to misunderstanding so use it with care''' and remember to remove/rename the cherry picker file when done cherry picking!

	~~'''~~The mechanics:~~'''~~		==The mechanics:==

	* Create a file under the project configuration directory named <code>config_file_cherry_picker.xml</code>.		* Create a file under the project configuration directory named <code>config_file_cherry_picker.xml</code>.
	* Edit that file to say what file to include for what locale in the next prep kit. If you have a 'fake' file, no files will be sent.		* Edit that file to say what file to include for what locale in the next prep kit. If you have a 'fake' file, no files will be sent.

			== Example 1 ==
	For instance, let's say that you want to send 9 files out of 10 to translate into French and German and all ten for the remaining locales. You could write a Cherry Picker like:		For instance, let's say that you want to send 9 files out of 10 to translate into French and German and all ten for the remaining locales. You could write a Cherry Picker like:
	<pre>		<pre>
Line 49:		Line 50:
	In this example, if the <code>locales</code> directory has 10 files, only 9 are sent for French and German; The other locales in this LRM project are not affected.		In this example, if the <code>locales</code> directory has 10 files, only 9 are sent for French and German; The other locales in this LRM project are not affected.

			== Example 2 ==
	Now let's say that for Chinese you do not want to send any files. You could write a Cherry Picker like:		Now let's say that for Chinese you do not want to send any files. You could write a Cherry Picker like:
	<pre>		<pre>

Olibouban at 19:58, 20 June 2016

2016-06-20T19:58:08Z

← Older revision		Revision as of 19:58, 20 June 2016
Line 2:		Line 2:
	'''This feature sometimes lead to misunderstanding so use it with care''' and remember to remove/rename the cherry picker file when done cherry picking!		'''This feature sometimes lead to misunderstanding so use it with care''' and remember to remove/rename the cherry picker file when done cherry picking!

	The mechanics:		'''The mechanics:'''

	* Create a file under the project configuration directory named <code>config_file_cherry_picker.xml</code>.		* Create a file under the project configuration directory named <code>config_file_cherry_picker.xml</code>.