Fallback to English in remoting_localize.py

Currently, remoting_localize.py will fail with an exception if the
requested string has not yet been translated to the requested language.
This makes it difficult to introduce new strings to files localized
using the script (such as core.rc.jinja2), as the build will fail until
all translations have landed. To make life easier, this change makes
remoting_localize.py fall back to English if the appropriate translation
is not available, similarly to how localization is handled elsewhere in
Chromoting.

Bug: 679313
Change-Id: I3e02104ba9b84b838dd152c7d7fe8e236addc109
Reviewed-on: https://chromium-review.googlesource.com/c/1444751
Reviewed-by: Jamie Walch <jamiewalch@chromium.org>
Commit-Queue: Erik Jensen <rkjnsn@chromium.org>
Cr-Commit-Position: refs/heads/master@{#627274}
1 file changed