Re-factor the L10n-implementations to use lowercase language-codes internally

This is consistent with the implementation used in the (now removed) webL10n-library, and by only using lowercase language-codes internally in the `L10n`-implementations we should avoid future issues e.g. when users manually set the `locale`-option (in the default viewer).
This commit is contained in:
Jonas Jenwald 2023-11-13 13:55:01 +01:00
parent 44cde3ccca
commit 1f9533bae9
6 changed files with 27 additions and 21 deletions

View file

@ -48,7 +48,7 @@ class GenericExternalServices extends DefaultExternalServices {
}
static async createL10n() {
return new GenericL10n(AppOptions.get("locale") || "en-US");
return new GenericL10n(AppOptions.get("locale"));
}
static createScripting({ sandboxBundleSrc }) {