This bug is to localize Firefox for Android copy for the Google Play Store. The copy reflects the changes made to the new Firefox for Android product page that goes live on October 29:https://www-demo1.allizom.org/en-US/firefox/android/ Two parts 1. Localize headline and copy for top 10 feature screenshots (see attached en_US example) 2. Localize the Google Play store listing itself Timing: - Nov 10: Current Firefox for Android GP locales - Nov 25: All 41 GP locales Project owner: Arcadio Lainez Length of project (in number of source strings or words): 532 words Description of target audience: Android users on the Firefox for Android Google Play store listing Where the source project will live: https://docs.google.com/a/mozilla.com/document/d/1O287e1iM9uDhMAwigj4i8Ss_Q-btJWKe00hyaNswAcM/edit Target locales for first iteration: zh-TW, cs-CZ, nl-NL, fr-FR, de-DE, it-IT, ja-JP, ko-KR, pl-PL, pt-BR, pt-PT, ru-RU, es-ES, en-US Rate of adding new locales per quarter: TBD Resources available for L10n drivers and localizers (can include personnel): Not sure Identify project's life-cycle:NA Project's release schedule (URL preferred): NA Project's target release date: November 10, 2014 (for locales shown above; Nov 25 for all locales in Google Play Store options)

Cleaning up CC list and CCing more l10n-drivers. (In reply to alainez from comment #0) > - Nov 10: Current Firefox for Android GP locales Why updating the text for November 10? This is not a small text to localize, localizers are already flooded with requests for FxDecade (and we're short on l10n-drivers in the first days of November). I strongly suggest to move the deadline for all locales after November 25, and even with that timeframe we won't get all localizations in. Not even sure how to manage 55 localizations of a Google Doc to be honest.

Let's(In reply to Francesco Lodolo [:flod] from comment #1) > Not even sure how to manage 55 localizations of a Google Doc to be honest. We shouldn't use a Google doc, let's use a .lang file and generate .txt outputs for marketing to copy/paste. That said, I agree that we (l10n-drivers and localizers) already have plenty of work for November 10 and adding new stuff everyday with this deadline is not a good idea.

Arcadio, I will take this bug and we will do what we can to get you locales, but given the context (a new project or a copy change per day, all of them for end of next week, with ) we will just do our best to get you localized content but can't promise you will get the volume or locale set you want for this deadline. The bug is in the Marketing/Copy component in Bugzilla, I looked at Bugzilla component/products and it seems that there is none for Google Play. Maybe it would be a good idea to get the Bugzilla guys add Firefox Android/Google Play component since updating our google play listing copy is a recurring task.

Thanks you guys. Understand the timing isn't great. I was hoping to get the Google Play store listing copy (the long description) done in the 14 languages we have on GP now. After Nov 10 we could catch up with everything else. Understand the time though. Filed the bug after speaking with Jeff and choffman over email. Agree on having a GP component. However, I don't anticipate changes to happen that frequently to the store listing and screenshots. The main parts that change with each release is the "What's New" section. Thanks, Everyone.

There are various links in the copy that are integrated in the google doc: Read about Firefox permissions: mzl.la/Permissions Learn more about what’s up at Mozilla: blog.mozilla.org Like Firefox on Facebook: mzl.la/FXFacebook Follow Firefox on Twitter: mzl.la/FXTwitter and Also links like: "Curious about add-ons? Check them out on AMO:" where AMO is a link. How is Google Play determining what words are links? Does it recognize mzl.la links automatically? Is there a specific format that Google Play is expecting like HTML or Markdown? I need these information to know if we should have replacement variables in the strings and what output we should generate. Thanks

As a side note, I think the AMO link should lead to https://addons.mozilla.org/android/ and not to https://addons.mozilla.org/firefox/, that's also why I would prefer these links not to be hardcoded in the copy, so as that we can change them without pinging localizers

I see in a past bug that there may be text length constraints for Google Play https://bugzilla.mozilla.org/show_bug.cgi?id=949420#c2 Arcadio, are there such constraints for this text? Thanks

(In reply to Pascal Chevrel:pascalc from comment #7) > I see in a past bug that there may be text length constraints for Google Play > https://bugzilla.mozilla.org/show_bug.cgi?id=949420#c2 > > Arcadio, are there such constraints for this text? Thanks Hey Pascal - the Full Description has a 4000 character limit. We are currently at 3407 character or less. The one place where we have a 500 character limit is in the "What's new" section which is not part of this request.

(In reply to Pascal Chevrel:pascalc from comment #6) > As a side note, I think the AMO link should lead to > https://addons.mozilla.org/android/ and not to > https://addons.mozilla.org/firefox/, that's also why I would prefer these > links not to be hardcoded in the copy, so as that we can change them without > pinging localizers Agreed. Thank you for catching that.

(In reply to alainez from comment #8) > (In reply to Pascal Chevrel:pascalc from comment #7) > > I see in a past bug that there may be text length constraints for Google Play > > https://bugzilla.mozilla.org/show_bug.cgi?id=949420#c2 > > > > Arcadio, are there such constraints for this text? Thanks > > Hey Pascal - the Full Description has a 4000 character limit. We are > currently at 3407 character or less. > Translations are usually 10 to 30% longer to the source text, which means that many locales will be well above 4000 characters (3407 * 1.3 = 4429), so that's a constraint that needs to be taken into account in this project, communicated to localizers and we will probably need to work on tooling to check copy length in an automated way.

(In reply to Pascal Chevrel:pascalc from comment #6) > As a side note, I think the AMO link should lead to > https://addons.mozilla.org/android/ and not to > https://addons.mozilla.org/firefox/, that's also why I would prefer these > links not to be hardcoded in the copy, so as that we can change them without > pinging localizers Good idea. Let's do that. GP is reading HTML links but I would like the ability to change those without pinging the localizers.

For future reference, this is the only resource about formatting possibilities of the app description I found, so that's the basis I will use for the output: http://stackoverflow.com/questions/11071127/google-play-app-description-formatting

OK, translation of this page is launched and back to a normal l10n process which means that you have a dashboard to follow the progress there: https://l10n.mozilla-community.org/~pascalc/langchecker/?locale=all&website=12&file=description_page.lang We also now have a small web app that outputs the description page in rendered html, source html and json (for future collaboration with the scripts release drivers are working on so as to automate updates to Google Play), it is here: https://l10n.mozilla-community.org/~pascalc/google_play_description/ Our German localizer who is very fast and efficient already translated it so you have a live example: General view for QA and copy-pasting of TOP 10 features strings: https://l10n.mozilla-community.org/~pascalc/google_play_description/?locale=de HTML output for copy-pasting into Google Play interface, this should result in a similar output in Google Play as what we have in the general view. It uses the html tags mentionned un the Stackoverflow article I referenced: https://l10n.mozilla-community.org/~pascalc/google_play_description/?locale=de&output=html Json output for tools wanting to get this data remotely: https://l10n.mozilla-community.org/~pascalc/google_play_description/?locale=de&output=json

Cheers, Pascal!!

Arcadio, does the 4000 character limit include both the copy describing Firefox and the top 10 features that describe the screenshots? Also, it would be good to test if html tags are counted in the total number of characters allowed, could you test and tell me? Thanks

Arcadio, you mentionned 41 Google Play locales, do you have this list? Our Frisian localizer raised the point that his locale is probably not among them, I need to assign the task only to the locales that we have in common with Google Play (currently it is assigned to all our Android locales). thanks

(In reply to Pascal Chevrel:pascalc from comment #15) > Arcadio, does the 4000 character limit include both the copy describing > Firefox and the top 10 features that describe the screenshots? Also, it > would be good to test if html tags are counted in the total number of > characters allowed, could you test and tell me? Thanks 4,000 is only for the description. The top 10 features are not counted in the word count because those will be part of the screenshots we're creating

(In reply to Pascal Chevrel:pascalc from comment #16) > Arcadio, you mentionned 41 Google Play locales, do you have this list? Our > Frisian localizer raised the point that his locale is probably not among > them, I need to assign the task only to the locales that we have in common > with Google Play (currently it is assigned to all our Android locales). > thanks These are the 14 locales we currently support on GP: zh-TW, cs-CZ, nl-NL, fr-FR, de-DE, it-IT, ja-JP, ko-KR, pl-PL, pt-BR, pt-PT, ru-RU, es-ES, en-US Here is the list of GP locales we don't currently support: Afrikaans – af Amharic – am Arabic – ar Belarusian – be Bulgarian – bg Catalan – ca Chinese (Simplified) – zh-CN Croatian – hr Danish – da-DK English (United Kingdom) – en-GB Estonian – et Filipino – fil Finnish – fi-FI French (Canada) – fr-CA Greek – el-GR Hebrew – iw-IL Hindi – hi-IN Hungarian – hu-HU Indonesian – id Latvian – lv Lithuanian – lt Malay – ms Norwegian – no-NO Persian – fa Romanian – ro Romansh – rm Serbian – sr Slovak – sk Slovenian – sl Spanish (Latin America) – es-419 Spanish (United States) – es-US Swahili – sw Swedish – sv-SE Thai – th Turkish – tr-TR Ukrainian – uk Vietnamese – vi Zulu – zu

(In reply to alainez from comment #18) > (In reply to Pascal Chevrel:pascalc from comment #16) > > Arcadio, you mentionned 41 Google Play locales, do you have this list? Our > > Frisian localizer raised the point that his locale is probably not among > > them, I need to assign the task only to the locales that we have in common > > with Google Play (currently it is assigned to all our Android locales). > > thanks > > These are the 14 locales we currently support on GP: zh-TW, cs-CZ, nl-NL, > fr-FR, de-DE, it-IT, ja-JP, ko-KR, pl-PL, pt-BR, pt-PT, ru-RU, es-ES, en-US > > Here is the list of GP locales we don't currently support: > Afrikaans – af > Amharic – am Do you mean that the list Google PLay supports is the addition of these 2 lists? Where did you get the list? Is that documented somewhere? Thanks

Got it from the Google Play Console where all the store listing assets are managed. These are the available locales that I can add to our listing.

Arcadio, a few update on the webapp: - Home page now shows the list of locales fully translated in the first column: https://l10n.mozilla-community.org/~pascalc/google_play_description/ - QA view shows untranslated strings in orange, ex: https://l10n.mozilla-community.org/~pascalc/google_play_description/?locale=fr - If you hover a translated string in QA page, you can see the original English string - The total count of letters is displayed on the QA page for the description, it doesn't count the html markup - The raw html page allows clicking on the html, it will make the text selectabla for copy/pasting (click on text, ctrl+A, ctrl+C and you have the text ready for pasting with CTRL+V in Google Play). We have a few locales translated already. I will work on Monday on making our making sure our locales match what locales are supported on Google Play.

One more question: can we have HTML in these strings? Example: in Italian we display foreign words in Italic, so "<em>mobile</em>". Would that work?

(In reply to Francesco Lodolo [:flod] from comment #22) > One more question: can we have HTML in these strings? > > Example: in Italian we display foreign words in Italic, so > "<em>mobile</em>". Would that work? You can use <i>

(In reply to Pascal Chevrel:pascalc from comment #23) > You can use <i> OK, thanks.

Given that we had to add a string in bug 1093554, the Play dashboard app only lists as translated the locales that translated it in the last 30mn (2 locales so far): https://l10n.mozilla-community.org/~pascalc/google_play_description/ Use this dashboard to check which locales have the full description translated minus the short description: https://l10n.mozilla-community.org/~pascalc/langchecker/?locale=all&website=12&file=description_page.lang All locales with only have 1 string untranslated are good to go.

Thanks, Pascal! To clarify in this link: https://l10n.mozilla-community.org/~pascalc/langchecker/?locale=all&website=12&file=description_page.lang All the locales that show "1" are good to go? Meaning they are only missing the short description? If yes, how about "it" and "ja". They seemed complete a few days ago but they don't show the "1" in the link. Can you let me know about those two?

I translated the tagline to ja one hour ago in r134449, so the file is completely translated.

(In reply to alainez from comment #26) > If yes, how about "it" and "ja". They seemed complete a few days ago but > they don't show the "1" in the link. Can you let me know about those two? They're fast ;-) Both locales were already updated (the other one is mine).

So that's even better. Means it's totally translated! Impressive!! Thanks again...

Hello... I'm flowing the text into the design layout. Japanese doesn't look right to me. Can someone let me know if OK or give a hint on how to copy/paste from text editor to Photoshop? Thanks! arcadio

Kohei, do you think you can help (or do you know someone who could)?

(In reply to alainez from comment #30) > Created attachment 8519520 [details] > Japan_Sync_Final.png It looks good to me :) I have Photoshop so can help if you have some other variations. Just send me your PSD file! (M+ fonts are preferred for Japanese rendering; it's perfectly matched with Open Sans: http://mplus-fonts.sourceforge.jp/mplus-outline-fonts/index-en.html)

I just opened the attachment 8513225 [details] and found 13 image files rendered in Fira Sans. Anyways I'm happy to help!

Thanks, Kohei. If the attachment I sent with the Japanese translation looks good to you, I can quickly go through the rest of the screenshots and send them to you for a final review. I was worried these characters were not properly formatted: 好 | コ | ー But if you think they look good, I'll just keep going. arcadio

Um, yes, some characters may not be properly formatted depends your fonts, and it's very difficult to decide where to break lines (invisible separators between word groups) like this: > パスワード、/ブックマーク、/開いている/タブなどを/どこへでも/持ち出せます。 > 好きな/Web コンテンツで/ホームパネルを/カスタマイズ。 The attached ZIP contains my shots. Hope this helps :)

Kohei, Thanks so much for sending the strings with the screenshots. By reviewing your screenshots, I realized I had made a mistake in the QuickShare screen. I have attached them here with localized screenshots of each feature. I matched your string breaks so hopefully this reads well now. Thanks for help! arcadio

(In reply to alainez from comment #37) > Created attachment 8519734 [details] > Japanese_GP Screenshots.pdf LGTM :)

There is another string missing in this bug, the title. We also need that string to update the copy via the google play API. Currently the English title is "Firefox Browser for Android", Arcadio can you confirm that this is what I should give for translation to localizers? FYI, we already have the title "Firefox for Android" on mozilla.org and could just reuse that.

I'll add that right now the title is quite a messy mix: I checked the other day because a Danish localizer pinged me, we go from "Firefox", to "Firefox Web Browser", to "Firefox Official Browser", and probably some more variations. Having a single string, update through API seems a very sane option.

We have been updating our google play copy in 2015 for both the release and beta channels via Google Play API and joint automation between l10n-drivers and release-drivers. Marking fixed.