Closed Bug 738780 Opened 12 years ago Closed 12 years ago

[NativeUI Beta] Localize Google Play Market description

Categories

(Mozilla Localizations :: Other, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jfu, Assigned: Milos)

References

()

Details

Hi Milos,

For the upcoming Native UI Beta launch, we revamped the description on the Google Play (Android Market) page. 

We would like to request for localizations in these languages:
be
ca
cs
da
de
es-AR
es-ES
et
eu
fl
fr
fy-NL
ga-IE
gd
gl
he
hu
id
it
ja
ja-JP-mac
ko
lt
nb-NO
pa-IN
pl
pt-BR
pt-PT
ro
ru
sk
sl
sq
th
tr
zh-CN
zh-TW


Copy to be localized:

Help refine and polish the newest features almost ready for prime time.

With Firefox Beta, you get to test the latest performance, customization and security enhancements before they make it to our next version. Have an impact by helping to put the finishing touches on features and functionality.

Visit https://bitly.com/FXinput to report issues or share your suggestions so we can make Firefox for Android more awesome.

Firefox Beta is compatible with a wide range of devices. Find out if yours is supported at http://mozilla.com/mobile/platforms/.

ABOUT MOZILLA
Mozilla is a proudly non-profit organization dedicated to keeping the power of the Web in people's hands. We're a global community of users, contributors and developers working to innovate on your behalf. When you use Firefox, you become a part of that community, helping us build a brighter future for the Web. Learn more at mozilla.org.
-------

Aimed deadline: April 19 (Beta is expected to release on April 20) 

Thank you!
Hi Milos - we would like to get as many languages localized before the Beta launch as possible. Thanks!
At this point, it's hard to ask our l10n community on this, as we're short of a product to localize. Not that we're short on plans on that, but we're still hoping for one that survives half a week.

We'll need to be a tad non-planned and last-minute if we don't want to end up in a situation where the engagement pages don't match the locales we ship in again.
I'm unclear on what the request is in the description.

is it to localize the the copy there plus the linked pages including

http://www.mozilla.org/en-US/mobile/platforms/ 
and 
http://m.input.mozilla.com/en-US/feedback#intro
No, the request is to just localize the description copy
Pascal, Milos, can we prepare something to have this task on the webdashboard following the locale list that we're finding to be ship-ready on the product side? Maybe put this in a .lang file?

Once we get ready on the product side, we should align forces to get the market material exposed and tracked swiftly, so that we get the best out of the situation we're in.
(In reply to Jaclyn Fu from comment #4)
> No, the request is to just localize the description copy

Has the content on the link pages already been translated somewhere.  Seems like we don't want to link to english content from localized content, right?
(In reply to Axel Hecht [:Pike] from comment #5)
> Pascal, Milos, can we prepare something to have this task on the
> webdashboard following the locale list that we're finding to be ship-ready
> on the product side? Maybe put this in a .lang file?

Pascal should be able to create a new `project` in the webdashboard, and we can file bugs for each locale and assign those to a project. That way we could track it easily and will know at all times where are we with translations.
sure, no problem, we can do that today.
Updated list of locales that Firefox Beta will be available in (someone correct me if there's an even more up-to-date update):

Russian
German
French

We will need the description copy localized in these languages. We are making a copy tweak, and will provide final copy in the next couple of days 

Aimed deadline: May 8 

Thanks
Updated copy for localization in ru, de, fr:
-------

Help refine and polish the newest features almost ready for prime time.

With Firefox Beta, you get to test the latest performance, customization and security enhancements before they make it to our next version. Have an impact by helping to put the finishing touches on features and functionality.

Visit https://bitly.com/FXinput to report issues or share your suggestions so we can make Firefox for Android more awesome. Find a bug? Report it at http://mzl.la/fxbug. 

See our list of supported devices and minimum system requirements: http://mozilla.com/mobile/platforms/. 

Firefox Beta is currently available in English, Russian, German, and French, with additional language support coming soon.
Should we check in translations in nativeui-beta-kickoff.txt file in projects/l10n-misc/trunk/androidmarket (e.g. http://viewvc.svn.mozilla.org/vc/projects/l10n-misc/trunk/androidmarket/ru/nativeui-beta-kickoff.txt)?
Jaclyn, you got me confused here. Hardcoding the language list sounds like a step backwards. I understand that I've sent this one out, but it's already outdated (we're adding Punjabi).

Also, is the lack of ABOUT MOZILLA on purpose?

Regarding our locale coverage, I don't think folks can select the language they get in the market. So enumerating them without making them accessible might not be helpful? Instead we could point them to all-beta.html? Maybe if the copy had some text along the lines of "If your download is not in the language you expect, please check "LINK_TO_BETA.html" for our currently available list. We're growing our coverage on a weekly basis." or so?
I'm not familiar with our approach when it comes to supported locales - can you explain how hardcoding the language list is a step backwards? 

The About Mozilla portion is already localized, so I didn't include it in the request. 

If a user with an unsupported language lands on our Google Play Store page, and the description is in English, they might still hit the download button anyway. If we actually tell them what languages are supported beforehand, then they'll know the version they are downloading is not in their default language (unlikely people will come back to our Google Play page after they download and it's not in the language they expect) 

all-beta.html is desktop only, languages for mobile is not reflected. would there be another place to point them to if we went with this approach?
My main problem with the list of hard-coded localizations is that it's
- new content to localize every week, and that
- we don't know the list of locales we ship that week before hand.

I must continue to take new localizations every day, as they come in. Our engagement material can't hold us back.

Re the copy, we need to have one copy to send out to localizers, mixing stuff that's current with stuff that might have been there doesn't allow us to act quickly.

Re downloading the less-than-preferred language: I don't know what will happen when the device language becomes available on the market. It might just switch to the newly-available locale, but we'd have to loop in the market specialists.

If the market users are used to getting their market description in English but the app localized, then clarifying the current list of languages in the English copy makes sense to me, but what's the benefit of that in the localized texts?

The original plan for the single-locale builds was to have two ways to install, the OS-locale or English from the market, and an explicit choice of locale independent and beyond the market on our website, updating through the mozilla update service instead of the market updates (like nightlies/aurora does now). So I think we should have an all-beta.html and all.html and similar for mobile like we have for desktop. Not sure if those bugs are filed, though.
(In reply to Axel Hecht [:Pike] from comment #14)
> My main problem with the list of hard-coded localizations is that it's
> - new content to localize every week, and that
> - we don't know the list of locales we ship that week before hand.

It would be the same content to localize in the new supported language (for the already localized descriptions we would just have to insert the language name into the list). This first Beta is going to be a change for a lot of our users because the list of supported languages has decreased so much. We should give them a heads up that what once was supported is not anymore. 
 
> 
> I must continue to take new localizations every day, as they come in. Our
> engagement material can't hold us back.

Engagement material is not holding anyone back. I just want to the description copy to be localized in the languages the product is going to be available in. 
> 
> Re the copy, we need to have one copy to send out to localizers, mixing
> stuff that's current with stuff that might have been there doesn't allow us
> to act quickly.

What do you mean by "mixing stuff that's current with stuff that might have been there"? 
> 
> Re downloading the less-than-preferred language: I don't know what will
> happen when the device language becomes available on the market. It might
> just switch to the newly-available locale, but we'd have to loop in the
> market specialists.

Not sure on this either. But in the What's New Tab we can also include a note about the new language that's added
> 
> If the market users are used to getting their market description in English
> but the app localized, then clarifying the current list of languages in the
> English copy makes sense to me, but what's the benefit of that in the
> localized texts?

Good point. We can take out the list of languages for the localized versions and keep the list in English only. 

> 
> The original plan for the single-locale builds was to have two ways to
> install, the OS-locale or English from the market, and an explicit choice of
> locale independent and beyond the market on our website, updating through
> the mozilla update service instead of the market updates (like
> nightlies/aurora does now). So I think we should have an all-beta.html and
> all.html and similar for mobile like we have for desktop. Not sure if those
> bugs are filed, though.

Not sure, but I can poke around 


So - are we OK with localizing the copy minus the list of languages at the end (list of languages for en only)?
(In reply to Jaclyn Fu from comment #15)
> (In reply to Axel Hecht [:Pike] from comment #14)
> > My main problem with the list of hard-coded localizations is that it's
> > - new content to localize every week, and that
> > - we don't know the list of locales we ship that week before hand.
> 
> It would be the same content to localize in the new supported language (for
> the already localized descriptions we would just have to insert the language
> name into the list).

That "just" is the problem, we need the right names in N languages every week. I expect to get some 60 languages building, can't say how many of those are close to shipping until we get there. I'll do my very best to make this not scale ;-)

> This first Beta is going to be a change for a lot of
> our users because the list of supported languages has decreased so much. We
> should give them a heads up that what once was supported is not anymore. 

I'm with you here, though I'd choose a different wording. The locales we ship on 10.0.x are still supported, they're just not making the first beta.

> > I must continue to take new localizations every day, as they come in. Our
> > engagement material can't hold us back.
> 
> Engagement material is not holding anyone back. I just want to the
> description copy to be localized in the languages the product is going to be
> available in. 

We don't know that list until very late in each weekly cycle. The flow of how we can add localizations to a product progressing as aggressively as mobile does right now doesn't offer a lot of knowledge on what we're shipping.

> > Re the copy, we need to have one copy to send out to localizers, mixing
> > stuff that's current with stuff that might have been there doesn't allow us
> > to act quickly.
> 
> What do you mean by "mixing stuff that's current with stuff that might have
> been there"? 

We're exposing the copy in one file to our localizers. If there are chunks that you expect to get from previous versions, you need to keep them in the copy. Otherwise they'll get removed in both the copy we offer and the localized content.

> > Re downloading the less-than-preferred language: I don't know what will
> > happen when the device language becomes available on the market. It might
> > just switch to the newly-available locale, but we'd have to loop in the
> > market specialists.
> 
> Not sure on this either. But in the What's New Tab we can also include a
> note about the new language that's added

That's another string in the market, right? Sounds like a good idea, we shouldn't rely on that tab to be localized, though?

> > If the market users are used to getting their market description in English
> > but the app localized, then clarifying the current list of languages in the
> > English copy makes sense to me, but what's the benefit of that in the
> > localized texts?
> 
> Good point. We can take out the list of languages for the localized versions
> and keep the list in English only. 
> 
> > 
> > The original plan for the single-locale builds was to have two ways to
> > install, the OS-locale or English from the market, and an explicit choice of
> > locale independent and beyond the market on our website, updating through
> > the mozilla update service instead of the market updates (like
> > nightlies/aurora does now). So I think we should have an all-beta.html and
> > all.html and similar for mobile like we have for desktop. Not sure if those
> > bugs are filed, though.
> 
> Not sure, but I can poke around 
> 
> 
> So - are we OK with localizing the copy minus the list of languages at the
> end (list of languages for en only)?

Yeah, sounds good, thanks.
Ok awesome.

So we will need localized versions of the copy for Punjabi, German, French, Russian:

--------

Help refine and polish the newest features almost ready for prime time.

With Firefox Beta, you get to test the latest performance, customization and security enhancements before they make it to our next version. Have an impact by helping to put the finishing touches on features and functionality.

Visit https://bitly.com/FXinput to report issues or share your suggestions so we can make Firefox for Android more awesome. Find a bug? Report it at http://mzl.la/fxbug. 

See our list of supported devices and minimum system requirements: http://mozilla.com/mobile/platforms/. 

-----

For Punjabi we will also need this copy localized:

ABOUT MOZILLA
Mozilla is a proudly non-profit organization dedicated to keeping the power of the Web in people's hands. We're a global community of users, contributors and developers working to innovate on your behalf. When you use Firefox, you become a part of that community, helping us build a brighter future for the Web. Learn more at mozilla.org.

-----

Completion date: May 8

Thanks
Depends on: 751088
Depends on: 751089
Depends on: 751090
Depends on: 751091
Depends on: 751092
Depends on: 751093
cc'ing Tetsuya, who has flagged that Japanese will be signing off soon.

Milos can we get a ja localization of this copy as well?

thanks
Sure thing. I've added Japanese in revision r104952. Let's file a bug once they're definitely in, though. Is that all right?
Hi L10N team, Axel and I had a chat this morning to clarify how to best accomplish this. 

Takeaways:
-I should provide the content I want to be localized in one complete chunk
-Let L10N team drive what locales should be filed because they know which have landed for sure

-------
CONTENT: 

Help refine and polish the newest features almost ready for prime time.

With Firefox Beta, you get to test the latest performance, customization and security enhancements before they make it to our next version. Have an impact by helping to put the finishing touches on features and functionality.

Visit https://bitly.com/FXinput to report issues or share your suggestions so we can make Firefox for Android more awesome. Find a bug? Report it at http://mzl.la/fxbug. 

See our list of supported devices and latest minimum system requirements at http://mozilla.com/mobile/platforms/. 

ABOUT MOZILLA
Mozilla is a proudly non-profit organization dedicated to keeping the power of the Web in people's hands. We're a global community of users, contributors and developers working to innovate on your behalf. When you use Firefox, you become a part of that community, helping us build a brighter future for the Web. Learn more at mozilla.org.

-----

Thanks!
Depends on: 751794
https://bitly.com/FXinput -> http://mzl.la/FXinput
http://mozilla.com/mobile/platforms/ -> http://www.mozilla.org/mobile/platforms/
Learn more at mozilla.org -> Learn more at http://www.mozilla.org/ (for auto link)
OS: Mac OS X → All
Hardware: x86 → All
uploaded to Google Play
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
The Japanese description is not live on the store. Can you take a look?
https://play.google.com/store/apps/details?id=org.mozilla.firefox_beta&hl=ja
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Hi Kohei - the first beta was english only which is why we didn't upload the localized versions yet. now that b2 supports multi locales i'm in the process of re-uploading the localized copy 

thanks for flagging
Hi Kohei - the first beta was english only which is why we didn't upload the localized versions yet. now that b2 supports multi locales i'm in the process of re-uploading the localized copy 

thanks for flagging

*Japanese should be live now :)
Verified :)
Status: REOPENED → RESOLVED
Closed: 12 years ago12 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.