Difference between revisions of "Sequencing Example"

From Lingoport Wiki
Jump to: navigation, search
Line 12: Line 12:
 
</pre>
 
</pre>
   
The prep kit will be sent to translation with all the keys and values and <code>#Acme_1_5 - FULL-FILE</code> to indicate that this is the first prep kit and it will translate everything. When this prep kit is imported, the project will be 100% translated for all locales.
+
The prep kit will be sent to translation with all the keys and values and <code>#Acme_1_5 - FULL-FILE</code> to indicate that this is the first prep kit and it will translate everything. When this prep kit is pushed to the repository, the project will be 100% translated for all locales.
   
 
If the following lines:
 
If the following lines:
Line 26: Line 26:
 
SEAR_OPTIONA_63=three fix
 
SEAR_OPTIONA_63=three fix
   
The first prep kit has been sent and imported. The second prep kit will have the changes to the 1 file, 3 keys and 6 words. The file sent to be translated will look like:
+
The first prep kit has been sent and pushed to the repo. The second prep kit will have the changes to the 1 file, 3 keys and 6 words. The file sent to be translated will look like:
   
 
#Acme_2_5 - CHANGES-ONLY
 
#Acme_2_5 - CHANGES-ONLY
Line 52: Line 52:
 
The project has been 100% translated and two more prep kits are outstanding with changes.
 
The project has been 100% translated and two more prep kits are outstanding with changes.
   
If '''prep kit #3''' is imported, the imported .properties file subset would look like (but it would be translated to the appropriate language):
+
If '''prep kit #3''' is pushed to the repo, the .properties file subset would look like (but it would be translated to the appropriate language):
   
 
...
 
...
Line 64: Line 64:
 
...
 
...
   
If '''prep kit #2''' is then imported, the imported .properties files look like:
+
If '''prep kit #2''' is then pushed to the repo, the .properties files look like:
   
 
...
 
...
Line 76: Line 76:
 
...
 
...
   
Note that since <code>SEAR_OPTIONA_63</code> was changed for both prep kit #2 and #3, LRM remembered the order and kept the value from prep kit #3, even though the prep kits were imported in the reverse order.
+
Note that since <code>SEAR_OPTIONA_63</code> was changed for both prep kit #2 and #3, LRM remembered the order and kept the value from prep kit #3, even though the prep kits were pushed to the repo in the reverse order.

Revision as of 20:37, 25 April 2019

Suppose you have a Acme_en_US.properties file that is a combination of keys and values from several files. A subset of the file:

SEAR_NUMERIC_60=numeric
SEAR_DAILY_61=daily
SEAR_LICK_62=lick
SEAR_OPTIONA_63=optionally
SEAR_MARK_64=mark
SEAR_UNABLE_65=unable
SEAR_CASES_66=cases
SEAR_DEVIATI_67=deviation

The prep kit will be sent to translation with all the keys and values and #Acme_1_5 - FULL-FILE to indicate that this is the first prep kit and it will translate everything. When this prep kit is pushed to the repository, the project will be 100% translated for all locales.

If the following lines:

SEAR_DAILY_61=daily
SEAR_LICK_62=lick
SEAR_OPTIONA_63=optionally

are changed to:

SEAR_DAILY_61=one change
SEAR_LICK_62=two modification
SEAR_OPTIONA_63=three fix

The first prep kit has been sent and pushed to the repo. The second prep kit will have the changes to the 1 file, 3 keys and 6 words. The file sent to be translated will look like:

#Acme_2_5 - CHANGES-ONLY
SEAR_DAILY_61=one change
SEAR_LICK_62=two modification
SEAR_OPTIONA_63=three fix

If more keys are changed,

SEAR_OPTIONA_63=four changes
SEAR_MARK_64=five for good
SEAR_UNABLE_65=six half

Note that key SEAR_OPTIONA_63 has been changed in both prep kits. Create another prep kit (this one is #3), the prep kit sent will look like:

#Acme_3_5 - CHANGES-ONLY
SEAR_OPTIONA_63=four changes
SEAR_MARK_64=five for good
SEAR_UNABLE_65=six half

The Dashboard looks like:

SmokePrepKit2.png

The project has been 100% translated and two more prep kits are outstanding with changes.

If prep kit #3 is pushed to the repo, the .properties file subset would look like (but it would be translated to the appropriate language):

...
SEAR_NUMERIC_60=numeric
SEAR_DAILY_61=daily
SEAR_LICK_62=lick
SEAR_OPTIONA_63=four changes
SEAR_MARK_64=five for good
SEAR_UNABLE_65=six half
SEAR_CASES_66=cases
...

If prep kit #2 is then pushed to the repo, the .properties files look like:

...
SEAR_NUMERIC_60=numeric
SEAR_DAILY_61=one change
SEAR_LICK_62=two modification
SEAR_OPTIONA_63=four changes
SEAR_MARK_64=five for good
SEAR_UNABLE_65=six half
SEAR_CASES_66=cases
...

Note that since SEAR_OPTIONA_63 was changed for both prep kit #2 and #3, LRM remembered the order and kept the value from prep kit #3, even though the prep kits were pushed to the repo in the reverse order.