This directory contains translations for the message strings shown in the recovery installer UI.
The message translation process works as follows:
If you make a code change that requires message changes, adjust the English strings in the cros_recovery.grd file.
To trigger translation of updated messages, take the the current version of cros_recovery.grd and update the copy in Google's internal code repository
Wait until the actual translation process finishes (It can take a few weeks though!)
Build all_xtbs target in the Google's internal code repository:
# Make a g4 client if you haven't already. $ cd google3/googleclient/chrome/transconsole_resources $ blaze build all_xtbs
Find out where the blaze dumps the resulting cros_recovery_LANG.xtb
files. It will be visible by the blaze command log and possibly here: google3/blaze-genfiles/googleclient/chrome/transconsole_resources/strings/cros
Copy the resulting cros_recovery_LANG.xtb
files which contain the translated strings into your Chromium OS local branch. Make sure you get the versions that use the correct fingerprinting algorithm to generate message IDs.
If you are adding any new languages, update the cros_recovery.grd
file and update the permissions of new files to 640 using chmod
.
Create a code review that updates the corresponding files in this directory. Do a sanity check to verify that your review only contains string changes (i.e. no unexpected message ID changes).
(Optional, but recommended) Check updated images. Run ./make_images
inside of the sdk and look at the various images under screens/
.
(Optional, but recommended) Build a recovery image with your translation update change present and install the recovery image on a device to verify the translated strings show up as intended.
Have your code change reviewed and submit it as usual.