Closed pdehaan closed 9 years ago
It looks like what's happening is that the go server is looking for a normalized path where the lang and locale are lower case (e.g. zh_tw). The problem is that the PO files appear to have mixed case for locale (zh_TW, sr_Latn). We should probably normalize the path names to use lower case.
@nchapman is that possible? cc @pdehaan
Found in https://find.dev.mozaws.net/status/ (commit d99f37c)
Steps to reproduce:
Actual results:
Figure 1: Those don't look Chinese or Taiwanese. They look like my fallback locale of Portuguese. Note that my
Accept-Language
header is:... and it looks like zh_CN and zh_TW should both be valid locales, per the FindMyDevice-l10n repo.
And for the record, here's my JSON response for the /1/l10n/client.json file:
Expected results:
I should have gotten my preferred Chinese/Taiwanese strings instead of (my ultimately third choice) Portuguese. This may be some weird conversion of lowercase_UPPERCASE or dashes-vs_hyphens when conducting the special l10n dance.