Closed Bug 1473992 Opened Last year Closed Last year
[Survey] Quarterly Survey (Q3): addons
Hello Corneliu, As communicated through email, the bug is for billing purpose. *Project*: Q3 survey: addons.mozilla.org *Survey Source*: https://drive.google.com/drive/folders/1C3tV2TPzvnKra_YxQxTOR0rOaK7tr257 *Languages: P1: de, fr (partially localized); es, ru, zh-CN (new) P2: ja, pl, pt-BR, zh-TW (new) *Deadline*: P1 by next Friday (July 13) EOD if not sooner. P2 can be delivered a little later if you need more time. *Delivery*: I shared the whole folder with you: https://drive.google.com/drive/folders/1C3tV2TPzvnKra_YxQxTOR0rOaK7tr257. When you are ready to deliver, drop them in the Delivery folder. Name the file to include locale code. *INSTRUCTION*: ** Do NOT touch column A, modify or change orders. These are string IDs and go by defined sequence. ** Leave HTML kind of tags as they are and stylistic tagging can be moved around to make it work for the target language. ** Word(s) preceded with ":" should not be translated *Product Reference material*: ** Basic terminology**: https://transvision.mozfr.org/ - Choose mozilla.org as the Repository; select Target Locale, set Search In "Strings and Entities" as default. Mozilla.org site should contain the key terms used in this survey without going to the details of the product itself. ** Product terminology** references on Pontoon (localization tool for the communities): https://pontoon.mozilla.org/projects/. Select any of the product, then you can select the locales if you need to do more research on how the terms are used. Here are some examples: *** AMO (addons backend and mostly for developers): https://pontoon.mozilla.org/ja/amo/ *** AMO frontend (addons frontend for regular users): https://pontoon.mozilla.org/pl/amo-frontend/ *** AMO Linter (error reporting tool for developers): *Style guides**: https://github.com/mozilla-l10n/styleguides/tree/master/docs
Other tasks: Screenshots - https://drive.google.com/drive/folders/1epZUkaPN8j9dYkLmvnougKTT8d8s-0i- - Take localized screenshots (Peiying) - Post screenshots processing (Jennifer)
@Jennifer, I have completed with taking screenshots: https://drive.google.com/drive/folders/1epZUkaPN8j9dYkLmvnougKTT8d8s-0i-
@Jennifer, The files are dropped in this folder: https://drive.google.com/drive/folders/1YUmqpQD9cUsCRLf8BahvTzmvjD3BJ3Ix. Please give individual reviewer access to the file corresponding to the language s/he reviews. As discussed yestereday, you will coordinate de, fr, zh-CN and zh-TW, I will coordinate the rest. Let me know the best way you'd like to gather feedback before I send out request. A general rule, we try to avoid copy and paste by non-speakers to implement changes. In this round of delivery, there are some minor corrections in German and French in the files you provided. If you want those changes reverted, the agency can do that.
@Jennifer, Could you provide this text with the links embedded in the paragraph, not separately like this? This way, once the localized text is back, you don't have to piece them together. I don't want to second guess what the markups should be.
Flags: needinfo?(pmo) → needinfo?(jdavidson)
If browser locale is not set in target language, the manual way to change the language is https://qsurvey.mozilla.com/s3/addons-mozilla-org-survey/?sglocale=xx (xx being the locale code). This allows tester to check against English source side by side. Surveygizmo only allows locale code in lower case, such as pt-br, zh-tw. For Simplified Chinese, it should be zh.
@Jennifer, here is the update: - To make it easier to find, I move them to the "Edited-tested" folder. - The agency has completed its reviews and they can be found in the new folder. pt-BR has no change, other languages are highlighted in yellow. - All "edited" files are updated with the footer disclaimer, except for German. Let me know when the "de" edited file is uploaded. - I am not clear how the footer disclaimer is placed when you compile the survey. Double check on the indentation/alignment for each line. zh-CN and zh-TW are not consistent with the other languages. It is best implemented at code level instead of playing it in a spreadsheet. For that, verify all the languages when you drop the footer in the source files.
This request is complete.
Status: NEW → RESOLVED
Closed: Last year
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.