1184838 - Translation of NPS Survey for Firefox Hello

Status: RESOLVED FIXED

(Mozilla Localizations :: Other, defect)

Description

[Fabio Rios [:frios]]

Hello NPS survey
No character limits
On release in 42
Locales: all available locales for Firefox Hello: https://l10n.mozilla-community.org/~flod/webstatus/?product=loop-client-l10n

Requesting the translation of this survey that will appear at the end of a Firefox Hello call: http://www.surveygizmo.com/s3/2227372/Firefox-Hello-Product-Survey

Hoping to import translations into surveygizmo, but I need to investigate proper template. More info to follow...

Text for translation:

1. How likely are you to recommend Firefox Hello to a friend or colleague? (Scale: 0 is not very likely to recommend and 10 is extremely likely to recommend)

2. What could we do to improve Firefox Hello for you?

3. How can we improve Firefox Hello to make you more likely to recommend us?

4. Was there anything in particular that made Firefox Hello such a positive experience for you?

5. Please rate the quality of your call. 1 - Very Poor, 5 - Excellent

Thank You!

Thank you for taking the time to complete our survey. Your response is very important to us and will help make Firefox Hello better for our users.

Comment 1

[Francesco Lodolo [:flod]]

I found a page explaining the process, which seems quite complicated and will require a bit of testing/scripting.
http://help.surveygizmo.com/help/article/link/export-fields-for-translation

Can you try exporting the current survey and attaching the resulting file here?

Comment 2

[Francesco Lodolo [:flod]]

Temporarily taking so I don't lose track of it.

Comment 3

[Fabio Rios [:frios]]

Thanks Flod,

I'm getting some help here since I haven't worked this tool before. I'll come back once I have more info.

Comment 4

[Fabio Rios [:frios]]

Flod, just an update on this. Gareth is out this week and he is managing the surveygizmo account. I'll ask him to export the file when he returns.

I did go through the doc and it looks like it can get complicated depending on how we present our questions. Fortunately, there's only a few and with a little retouching we may be able to simplify it.

One thing we can't avoid is that we need one .csv file per language.

As you mentioned already we will need a bit of testing.

Comment 5

[Francesco Lodolo [:flod]]

It would be important to figure out the number of locales we want to involve, and if the time to create the automation is worth it. 

I personally think it is anyway, unless we find huge obstacles, because we have requests for surveys from time and time, and we could reuse these tools in the future.

Comment 6

[Romain Testard [:RT]]

Just for context, this survey is accessed from the Hello desktop client on Firefox at the end of a call and we'll change the survey contents once in a while (Fabio can correct me but it feels like the frequency of changes would be at worst 6 weeks to follow releases of new features on the desktop side) so automation may be valuable.
Regarding timelines, the prompt to enter a survey at the end of the Hello call is implemented in FF42 (now you can test this using the latest Nightly) and this will be riding the trains. I feel like we need this translated worst case when FF42 hits beta (September 22nd) and ideally all Firefox supported locales should be supported on the survey. In reality translating to all Firefox locales may not be practical and I'll follow your recommendations about how we can address the widest number of users with the smallest number of locales.

Comment 7

[Fabio Rios [:frios]]

(In reply to Romain Testard [:RT] from comment #6)
> we'll change the survey contents once in a
> while (Fabio can correct me but it feels like the frequency of changes would
> be at worst 6 weeks to follow releases of new features on the desktop side)
> so automation may be valuable.
We will need another survey that runs in conjunction with this survey so that NPS doesn't run 24/7/365. Will set that up in a separate bug. I don't see us modifying this specific survey, though.

> Regarding timelines, I feel like we need this translated worst case when FF42 hits beta (September 22nd) 
Thanks, that's helpful. Flod let us know if there's any concern there.

> In reality translating to all Firefox locales may not be practical
My understanding was that this delivery cannot be controlled, as in not prompting users in some locales. It is an all or nothing and if that's the case we've got to shoot for as many locales as we can get otherwise users will get a message in English.

Flod, once we have a solid understanding of how this process will work (auto or non), you can help us decide what's realistic in this timeline.

Comment 8

[Francesco Lodolo [:flod]]

(In reply to Fabio Rios [:frios] from comment #7)
> > Regarding timelines, I feel like we need this translated worst case when FF42 hits beta (September 22nd) 
> Thanks, that's helpful. Flod let us know if there's any concern there.

As long as we manage to have everything in place and tested together with the rest of material for fx42, I don't see any problem. We'll expose it to all locales, and get as many as we can. The survey seems also pretty short.

If we're stuck on the automation, we can still cover the top 10/15 locales or so with a spreadsheet and bugs.

I think surveygizmo chooses the language based on the accept_languages header sent by the browser
http://help.surveygizmo.com/help/article/link/default-language

> The default language is really only relevant in multiple-language surveys. Then, 
> when the survey is shared, the language of the respondent's browser will be 
> automatically detected and, if a translated version matching that language is 
> detected, it will display the translated survey in that language. If no 
> translated version exists, the default language you specify will display.

So, for example: if we don't get Fulah, but we have French, a browser set to Fulah should still get the French version, not English.

Comment 9

[Fabio Rios [:frios]]

A bit of a slowdown this week, but Gareth and I will be giving this a try next week.

Comment 10

[Fabio Rios [:frios]]

Flod, 

Gareth and I gave this a try and got it to work. Here's what we suggest:

- Use the below sheet to house all translations. 
- Each language's translation can exist in a separate tab. 
- Once complete, we will export each tab and upload directly to surveygizmo.

Do you think this will work for l10n team?

https://docs.google.com/a/mozilla.com/spreadsheets/d/14Bv8NUsjf49p_lpqXpmRPSaVkFYYyATeKJWSENbk1Fs/edit?usp=sharing

Comment 11

[Francesco Lodolo [:flod]]

(In reply to Fabio Rios [:frios] from comment #10)
> Do you think this will work for l10n team?

Not really, we stay as far as possible for Google Docs to store localizations because:
* You don't have a clear history (unlike a proper version control system).
* You don't have clear accountability (who changed what, at what point).
* You can't go back in history only for the part you're interested in (one locale).
* Status can't be tracked in the existing dashboards.

We tried in the past, and we ended up with people changing the wrong locale (like Japanese overwriting Italian), wrong translations and nobody who knew how they ended up there. 

Not an experience I'd like to repeat, especially if we're talking about many locales.

We can use Google Docs if we really have to, but it should be the last resort.

Comment 12

[Fabio Rios [:frios]]

Thanks. I'll take your word for it.

OPTION 2

Each person manages their own Google Doc and then provides the link when ready. We can keep track of the URLs in one place. Anywhere you think is good.

So instead of duplicating the tab, each person duplicates the entire Google Sheet. I can lock it down so that no edits can be made to the main sheet.

Unfortunately we need this in spreadsheet form to upload to surveygizmo.

Comment 13

[Francesco Lodolo [:flod]]

If we have to use Google Docs, I guess we can go with one doc with multiple sheets, we can also pre-create them for the locales we want.

But I'd really like to see us scaling this process, especially if we need it for the future.

Let's say you have a spreadsheet with 15 sheets, one for each locale. What are you going to load in surveygizmo? Does it accept this file directly?

Comment 14

[Fabio Rios [:frios]]

I'm happy to prepopulate the tabs. We will take the sheet and export it to as xls file. Then import to surveygizmo.

OK, so I'll create the tabs for each language. Should we start with 20 then add more?

I have no idea how to kick off scaling this process. We will need it again in the future. I'd look for your help on this.

Comment 15

[Francesco Lodolo [:flod]]

(In reply to Fabio Rios [:frios] from comment #14)
> I'm happy to prepopulate the tabs. We will take the sheet and export it to
> as xls file. Then import to surveygizmo.

When do we need to start with this? Because I feel like we're rushing things if it's needed for Firefox 42 (that was my understanding), and I'd like to figure out if there are way out of Google Docs, if there's enough time.

So, returning to the platform: you export every single sheet as xls, and then import them (one by one) in SurveyGizmo? No mass import for all locales?

Comment 16

[Fabio Rios [:frios]]

No mass import. Unfortunately it's one at a time.

We do need for 42. That gives us a couple of weeks so we need to start soon. But yo have a better insight into timing.

Comment 17

[Francesco Lodolo [:flod]]

(In reply to Fabio Rios [:frios] from comment #16)
> We do need for 42. That gives us a couple of weeks so we need to start soon.
> But yo have a better insight into timing.

Firefox 42 hits beta on Sep 22 and release on Nov 3, what am I missing?

Comment 18

[Fabio Rios [:frios]]

Ideally we could land strings at start 42 Beta.

Assuming we start next week...4 weeks for translation + 1 week for us to import.

Am I looking at this right?

Comment 19

[Francesco Lodolo [:flod]]

(In reply to Fabio Rios [:frios] from comment #18)
> Ideally we could land strings at start 42 Beta.
> 
> Assuming we start next week...4 weeks for translation + 1 week for us to
> import.
> 
> Am I looking at this right?

Thanks, clearer now. We should try to put the request out sometime next week. Let's see if I can think of something before that, otherwise we'll go with Google Docs.

Comment 20

[Francesco Lodolo [:flod]]

Attachment: it.xls

Fabio, can you try importing this file for Italian?

The file is generated from a standard .lang file with a script. If it works, we might be able to work on this with our standard tools, and give you a set of .xls files, one for each locale.

Comment 21

[Fabio Rios [:frios]]

Flod,

The file worked!

One file per locale is exactly what we need. We'll take as many locales as possible. 

Let me know if there's anything else I can provide.

Thanks.

Comment 22

[Francesco Lodolo [:flod]]

(In reply to Fabio Rios [:frios] from comment #21)
> The file worked!
Great, it means we can use our standard tools (including a dashboard for tracking), and you'll get all files (one per locale) in one folder.

> Let me know if there's anything else I can provide.
I should double check if all of our locales are supported by SurveyGizmo.

Are the current strings already final?

Comment 23

[Fabio Rios [:frios]]

Yes, see strings in this doc: https://docs.google.com/spreadsheets/d/14Bv8NUsjf49p_lpqXpmRPSaVkFYYyATeKJWSENbk1Fs/edit#gid=0

Comment 24

[Francesco Lodolo [:flod]]

(In reply to Fabio Rios [:frios] from comment #23)
> Yes, see strings in this doc:
> https://docs.google.com/spreadsheets/d/
> 14Bv8NUsjf49p_lpqXpmRPSaVkFYYyATeKJWSENbk1Fs/edit#gid=0

OK, they're the same I used for the test, so we're set. I will double check the supported locales, set up the files this week and put the deadline for Sep 14. Does it sound right?

Comment 25

[Romain Testard [:RT]]

Sounds good to me, this is a week before 42 hits beta.

Comment 26

[Fabio Rios [:frios]]

Thanks Flod and Romain. All good here.

Comment 27

[Francesco Lodolo [:flod]]

Dashboard for tracking
https://l10n.mozilla-community.org/~pascalc/langchecker/?locale=all&website=2&file=survey_hello_fx42.lang

Files will be available in 
https://svn.mozilla.org/projects/l10n-misc/trunk/surveys/surveygizmo/survey_hello_fx42/

You can check out the entire folder from the terminal with SVN (don't remember if SVN is available out of stock on OS X, or need to install the command line developer tools). 
svn co http://svn.mozilla.org/projects/l10n-misc/trunk/surveys/surveygizmo/survey_hello_fx42/

Eventually I can attach a zip of the folder before deadline.

Comment 28

[Francesco Lodolo [:flod]]

Attachment: xls.zip

Zip of locales currently completed.

If you prefer, they're accessible from there
http://svn.mozilla.org/projects/l10n-misc/trunk/surveys/surveygizmo/survey_hello_fx42/

Comment 29

[Fabio Rios [:frios]]

Thanks Flod. We are going to unpack and get started.

Comment 30

[Francesco Lodolo [:flod]]

Attachment: Small update for Serbian (sr)

I noticed an updated version for Serbian.

My understanding is that this is going to be used also in fx42 release. Should I upload more files if they're localized in the following weeks?

Comment 31

[Fabio Rios [:frios]]

Yes, that's right -- 42 release. 

Can you create a batch of the new files and send over when ready? Gareth and I got the others done pretty quickly, so anytime before Oct 30 is fine.

Thanks Flod.

Comment 32

[Francesco Lodolo [:flod]]

Attachment: surveys_20150930.zip

4 new locales: ca, eo, fy-NL, pt-BR.

I will keep an eye out to check if we'll have more before release.

Comment 33

[Fabio Rios [:frios]]

Thank you!

Comment 34

[Francesco Lodolo [:flod]]

Attachment: surveys_20151015.zip

2 more locales: az, cy.

Comment 35

[Francesco Lodolo [:flod]]

Attachment: surveys20151023.zip

2 more locales: fa, kk

Comment 36

[Francesco Lodolo [:flod]]

Attachment: surveys_20151031.zip

One more: Turkish

Comment 37

[Fabio Rios [:frios]]

Added. Thank you.

Comment 38

[Francesco Lodolo [:flod]]

I suppose we're good to close here. In case we have more surveys of this kind in the future, we can leverage the tools created for this one.

Comment 39

[Fabio Rios [:frios]]

Thanks again Flod