Closed brcavallaro closed 2 years ago
Thanks for opening this ticket @brcavallaro !
👋 @fluiddot, you probably have some insights on the translations side of things, can you check out this ticket? Thanks!
👋 @fluiddot, you probably have some insights on the translations side of things, can you check out this ticket? Thanks!
Sure, I'll take a look as soon as possible.
I've done a quick investigation, and the issue is related to the locale identifier used for loading the localizations in WordPress-iOS before passing them to Gutenberg (reference). For some reason, when using PT-BR language the locale identifier retrieved is PT
instead of PT-BR
. We have way less translations for PT
language than PT-BR
, so it makes sense that we see more strings untranslated.
WordPress for iOS GlotPress project:
We should investigate further how to retrieve the proper locale identifier for this case.
Thanks for investigating @fluiddot!
Aha, sounds like we shouldn't be opting for the region-less locale if the one for the region (Brazil in this case) is in a better translation coverage, right?
Aha, sounds like we shouldn't be opting for the region-less locale if the one for the region (Brazil in this case) is in a better translation coverage, right?
Exactly, we should retrieve PT-BR
localizations in this case. As outlined in this comment, I found it unexpected that this line returns PT
even when setting the device's language to PT-BR
. As far as I checked, we don't have a logic that opts for the region-less version when retrieving the localizations file, so I'm wondering if we're taking the wrong identifier for this purpose 🤔 .
Expected behavior
While using the WordPress app in iOS devices configured with PT-BR language, textual content should be translated accordingly.
Actual behavior
Some textual content remains in English when using WordPress app in PT-BR language (iOS device, iPhone XS).
Block removed
toastSteps to reproduce the behavior
Tested on iPhone XS, iOS 14.8.1, WPiOS 19.4.0.2