Difference between revisions of "Sequencing Example"
(→Conclusion) |
|||
| (13 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| + | == Prep Kit 1 == |
||
Suppose you have a '''Acme_en_US.properties''' resource file to be translated. A subset of the file: |
Suppose you have a '''Acme_en_US.properties''' resource file to be translated. A subset of the file: |
||
| Line 4: | Line 5: | ||
SEAR_NUMERIC_60=numeric |
SEAR_NUMERIC_60=numeric |
||
SEAR_DAILY_61=daily |
SEAR_DAILY_61=daily |
||
| − | SEAR_LICK_62= |
+ | SEAR_LICK_62=book |
SEAR_OPTIONA_63=optionally |
SEAR_OPTIONA_63=optionally |
||
SEAR_MARK_64=mark |
SEAR_MARK_64=mark |
||
| Line 12: | Line 13: | ||
</pre> |
</pre> |
||
| − | + | Since this is the first prep kit, the entire file will be sent to translation. The file will include all the keys and values. When this prep kit is pushed to the repository, the project will be 100% translated for all locales. |
|
| + | == Prep Kit 2 == |
||
If the following lines: |
If the following lines: |
||
SEAR_DAILY_61=daily |
SEAR_DAILY_61=daily |
||
| − | SEAR_LICK_62= |
+ | SEAR_LICK_62=book |
SEAR_OPTIONA_63=optionally |
SEAR_OPTIONA_63=optionally |
||
| Line 26: | Line 28: | ||
SEAR_OPTIONA_63=three fix |
SEAR_OPTIONA_63=three fix |
||
| + | '''Prep kit 2''' will contain this section of the file, (1 file) with 3 keys and 6 words, since prep kit 1 has already been sent, translated, and pushed back to the repository. |
||
| − | 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 |
||
| + | == Prep Kit 3 == |
||
If more keys are changed, |
If more keys are changed, |
||
| Line 39: | Line 37: | ||
SEAR_UNABLE_65=six half |
SEAR_UNABLE_65=six half |
||
| − | Note that key '''<code>SEAR_OPTIONA_63</code>''' has been changed in '''both prep kits'''. Create another prep kit (this one is #3) |
+ | Note that key '''<code>SEAR_OPTIONA_63</code>''' has been changed in '''both prep kits'''. Create another prep kit (this one is #3) with this section of the file. |
| + | == Dashboard View == |
||
| − | #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: |
The Dashboard looks like: |
||
| Line 52: | Line 47: | ||
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. |
||
| + | == Returning Prep Kit 3 == |
||
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): |
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 57: | Line 53: | ||
SEAR_NUMERIC_60=numeric |
SEAR_NUMERIC_60=numeric |
||
SEAR_DAILY_61=daily |
SEAR_DAILY_61=daily |
||
| − | SEAR_LICK_62= |
+ | SEAR_LICK_62=book |
'''SEAR_OPTIONA_63=four changes''' |
'''SEAR_OPTIONA_63=four changes''' |
||
| − | SEAR_MARK_64=five for good |
+ | '''SEAR_MARK_64=five for good''' |
| − | SEAR_UNABLE_65=six half |
+ | '''SEAR_UNABLE_65=six half''' |
SEAR_CASES_66=cases |
SEAR_CASES_66=cases |
||
... |
... |
||
| + | == Returning Prep Kit 2 == |
||
If '''prep kit #2''' is then pushed to the repo, the .properties files look like: |
If '''prep kit #2''' is then pushed to the repo, the .properties files look like: |
||
... |
... |
||
SEAR_NUMERIC_60=numeric |
SEAR_NUMERIC_60=numeric |
||
| − | SEAR_DAILY_61=one change |
+ | '''SEAR_DAILY_61=one change''' |
| − | SEAR_LICK_62=two modification |
+ | '''SEAR_LICK_62=two modification''' |
| − | + | SEAR_OPTIONA_63=four changes |
|
SEAR_MARK_64=five for good |
SEAR_MARK_64=five for good |
||
SEAR_UNABLE_65=six half |
SEAR_UNABLE_65=six half |
||
| Line 76: | Line 73: | ||
... |
... |
||
| + | == Summary == |
||
| − | 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. |
||
| + | |||
| + | 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. |
||
Latest revision as of 19:28, 26 April 2019
Contents
Prep Kit 1
Suppose you have a Acme_en_US.properties resource file to be translated. A subset of the file:
SEAR_NUMERIC_60=numeric SEAR_DAILY_61=daily SEAR_LICK_62=book SEAR_OPTIONA_63=optionally SEAR_MARK_64=mark SEAR_UNABLE_65=unable SEAR_CASES_66=cases SEAR_DEVIATI_67=deviation
Since this is the first prep kit, the entire file will be sent to translation. The file will include all the keys and values. When this prep kit is pushed to the repository, the project will be 100% translated for all locales.
Prep Kit 2
If the following lines:
SEAR_DAILY_61=daily SEAR_LICK_62=book SEAR_OPTIONA_63=optionally
are changed to:
SEAR_DAILY_61=one change SEAR_LICK_62=two modification SEAR_OPTIONA_63=three fix
Prep kit 2 will contain this section of the file, (1 file) with 3 keys and 6 words, since prep kit 1 has already been sent, translated, and pushed back to the repository.
Prep Kit 3
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) with this section of the file.
Dashboard View
The Dashboard looks like:
The project has been 100% translated and two more prep kits are outstanding with changes.
Returning Prep Kit 3
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=book SEAR_OPTIONA_63=four changes SEAR_MARK_64=five for good SEAR_UNABLE_65=six half SEAR_CASES_66=cases ...
Returning Prep Kit 2
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 ...
Summary
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.
