1805089 - Microsoft Store description shows English for Korean page

Status: NEW

(Firefox :: Installer, defect, P3)

Description

[Kagami Rosylight [:saschanaz] (they/them)]

Open https://apps.microsoft.com/store/detail/mozilla-firefox/9NZVDKPMR9RD?hl=ko-kr&gl=kr (hl= and gl= make sure it shows Korean version of the description if exists)

Expected: It should show Korean description
Actual: It shows English description

This one shows Korean one in contrast, so there's something wrong in the Firefox store page. https://apps.microsoft.com/store/detail/1001tvs-screen-mirror-file-transfer/9NF33JPHSQ14?hl=ko-kr&gl=kr

Comment 1

[[e-mail] (:bhearsum)]

It looks to me like the we don't have translated text for the Store page -- at least, not that we've uploaded. I checked some other locales (Italian, Japanese, French) and they were translated. Still some others (Telugu, Romanian) were not.

Ryan, Flod, Geoff -- I'm adding you all here to look for some insights into the expectations here, localization process, etc. It's not clear to me where these get translated (I don't see them in Pontoon?), so it's not clear if we're truly missing translations here, or if perhaps there's a breakdown in the process.

Comment 2

[Ryan VanderMeulen [:RyanVM]]

The Store falls back on en-US when there isn't a translation available for a given locale. Happy to update the listing if we have one.

Comment 3

[Francesco Lodolo [:flod]]

I think Romain would be in a position to answer this, as I have no real visibility.

We don't localize Store material as part of product. If needed, they can go through a different process (vendors)
https://mozilla-hub.atlassian.net/wiki/spaces/FIREFOX/pages/11047236/Request+a+translation+vendor

Comment 4

[Geoff Brown [:gbrown]]

Automation just copies the previous release submission, with no special behavior for locales.

Comment 5

[[e-mail] (:bhearsum)]

It sounds like this is a request for translation in that case.

Edit: erm, I meant to try to find a different component for this, or way to track it, before submitting this comment

Comment 6

[[e-mail] (:bhearsum)]

Does this belong in Mozilla Localization: Korean?

Comment 7

[Francesco Lodolo [:flod]]

(In reply to [e-mail] (:bhearsum) from comment #6)

Does this belong in Mozilla Localization: Korean?

No. Please check the comment I've provided, this doesn't go through community, assuming we want to localize it (which isn't my call, it's a product decision).

Comment 8

[[e-mail] (:bhearsum)]

(In reply to Francesco Lodolo [:flod] from comment #7)

(In reply to [e-mail] (:bhearsum) from comment #6)

Does this belong in Mozilla Localization: Korean?

No. Please check the comment I've provided, this doesn't go through community, assuming we want to localize it (which isn't my call, it's a product decision).

I realize that part, sorry - I'm just not sure who usually shepherds along this sort of thing, and how we track it.

Comment 9

[Francesco Lodolo [:flod]]

(In reply to [e-mail] (:bhearsum) from comment #8)

I realize that part, sorry - I'm just not sure who usually shepherds along this sort of thing, and how we track it.

Vendor requests (which include store content) are tracked via Jira. If Romain decided this needs to be translated, the full process is described in the doc.

As for this bug, do we have something for MSIX? If not, that sounds like something we would want? Otherwise, it might just be a case for Firefox::General.

Comment 10

[Romain Testard [:RT]]

For context when we launched on the store we only covered top Firefox locales for translation of the store page. The text was copied from the localized download pages for czech, dutch, finnish, german, greek, hungarian, indonesian, italian, japanese, polish, brazilian portuguese, portugese, russian, spanish and everything elese received the english strings.
This is not great but at time of launch we were unsure what to expect in terms of adoption and had to avoid creation of dependencies. We now have data on store page visits and should be able to prioritize localisation needs based on page visit volumes.
Let's keep the bug opened, I need to spend some time analysing the partner center data against supported locales to set a priority.