Filing this on behalf of the mobile team to get tracking on what we ship l10n-wise in GeckoView. GeckoView, by inspecting the beta
aar, ships a few localized resources, both
chrome:// and Fluent.
Open questions from our project-request template:
Description of target audience:
Where the source content (will) lives:
Reference materials (e.g., style guide):
Project's roadmap (URL preferred):
Project's target release date:
David, snorp, who's our partner on your side here?
I'd also like to share my speculations, and see if they're correct:
We're just shipping what used to be used for Fennec? l10n-central, multi-locale logic, changesets, covered files?
If so, we're probably not maintaining that configuration with the intent of doing the right thing for GeckoView on nightly. We just maintain it to do the right thing for Fennec on ESR 68 (which uses the config on mozilla-central).
We also talked about dropping the files in
mobile/ from the l10n process completely, which might have bad impact on what we'd need for GeckoView?