An email has been sent to chrome-localization@ asking for the next steps. It looks like sending new translation requests to the Translation Console requires specific privileges.
They're already translated. :-)
For instance, see
http://shortn/_2knwz0Cyl7 (inside Google: this is a shortened link to TC for 'Failed to copy to clipboard'). They're translated into Kannada, Marathi, Tamil, Malayalam, and many other languages (which is not supported by Chrome-Android).
My understanding is that messages have been translated into 'yet-to-support' languages for a few years in anticipation of 'upcoming' support, but that 'upcoming' support has been delayed for a long while unfortunately.
Anyway, it seems that there's an issue with getting translated strings back to Chrome's tree.
Google Internal link for Unable to complete previous operation due to low memory : http://shortn/_XvtFYYfifs
> Anyway, it seems that there's an issue with getting translated strings back to Chrome's tree.
govind@: String transfer script (from TC to Chromium tree) is likely to drop 9 locales in question for messages in ui/android/java/strings/android_ui_strings.grd .
digit@ : I think you need to update the following files in Chromium tree to get strings back from TC for 9 additional languages.
android_chrome_strings.grd
android_content_strings.grd
android_ui_strings.grd
android_webapk_strings.grd
android_webview_strings.grd
These files will be copied to the corresponding location in Google's internal repos and
everything may just work. See
http://www.chromium.org/developers/design-documents/ui-localization
BTW, https://chromium-review.googlesource.com/c/chromium/src/+/1196378#message-30b20be1d1e4e5f177db61a94e8834021b4e54dc explains why you encountered an issue with only 3 strings. That's because you're only adding android_ui_strings while not adding others listed the above.
If you had added them as well, you'd have found a lot more messages missing.
digit@ : did you update grd files to list more languages ? see comment 13.
While writing my comments here and in a chat session with you, I may have shuffled the order of things to do. The CL recorded in comment 15 may have to be preceded by listing more languages in grd files in comment 13.
Please take a look at the candidate CL [1] I just uploaded. Cherry-picking or submitting should be enough to get the import process to work correctly for @govind.
Once this is completed and we get the right .xtb file content, we should be able to fix the build rules related to omitted locales (which are currently broken, but see http://crbug.com/897056 for more details.
[1] https://chromium-review.googlesource.com/c/chromium/src/+/1297364
First CL submitted, now it's up to govind@ to run the import process to update the .xtb files.
Once this is done, please re-assign the bug to me so I can adjust the build system appropriately. And let me know of any issues.
Comment 1 by digit@google.com
, Sep 4