Sequencing Example

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.

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 the first prep kit has already been sent.

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.

The Dashboard looks like:

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