There are a number of languages that are supported by our translation service, but are not being offered as translation opportunities because they are not in our client-side list of supported languages. We have data showing the most common languages that are being missed, and we should consider adding some of them.
Assignee: nobody → florian
Status: NEW → ASSIGNED
Iteration: --- → 35.3
Points: --- → 2
So if I understood correctly, the languages we want to add are: - Dutch and Norwegian (useful for Polish users) - Azerbaijani and Bulgarian (useful for Turkish users) - Czech, traditional Chinese, Polish (useful for Vietnamese users) Felipe, I think you wrote somewhere that these languages are all supported by Bing. Where's the list of languages supported by Bing? I have doubts about Azerbaijani being supported, as it's not offered on http://www.bing.com/translator/ We are expending the experiment to Spain and Argentina. Do we know if some source languages relevant to these locales are missing in our current lists? Joanne, can we just go ahead here, or do we need to request permission to add these languages to our experiment? Or do we need to notify Bing about this change?
So it appears that 2 different things are happening here: 1) we're expanding the language pairs in our current test locales - no permission necessary from Bing 2) we're adding Spain & Argentina to the test - this requires an ok from Bing. Can someone prepare a short summary of the test results and why we need to expand into more locales (for external consumption), so I can send that on to the Bing folks?
Thanks Joanne. 1) is happening here. 2) is happening too, but in a different bug (bug 1072741).
The patch adds Dutch Norwegian Bulgarian Czech and Polish to the list of supported source languages. I skipped Azerbaijani because Bing doesn't support it, and traditional Chinese because our code would have a hard time differentiating it from simplified Chinese. Then I made the 2 lists match (which adds Turkish and Vietnamese in the list of source languages), because that makes Felipe happy ;-).
Attachment #8499674 - Flags: review?(felipc)
Attachment #8499674 - Flags: review?(felipc) → review+
Felipe and I discussed this bug on IRC last week, clearing the needinfo flag as I'm not actually waiting for anything from him here.
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 35
We tested the new languages added in the list of source languages, and all looks fine from QA point of view (played with the translation and checked that the data is stored in FHR). Testing was done on Windows 7 64-bit, Windows 8.1 64-bit Surface Pro 2, Mac OS X 10.9.5 and Ubuntu 14.04 32-bit using latest Nightly (buildID: 20141010030201). Closing this as verified fixed since it was verified on the target milestone.
Comment on attachment 8499674 [details] [diff] [review] Patch Approval Request Comment [Feature/regressing bug #]: Increases the list of languages that we offer translation to/from [User impact if declined]: The languages added are the ones that are the most common misses, according to the FHR data we have from the running experiment [Describe test coverage new/current, TBPL]: Landed in m-c, tested locally [Risks and why]: Limited to the translation experiment [String/UUID change made/needed]: None
Attachment #8499674 - Flags: approval-mozilla-aurora?
Comment on attachment 8499674 [details] [diff] [review] Patch Aurora+ Felipe, as discussed, please handle the landing of this patch yourself before the uplift of 34 to beta on Monday.
Attachment #8499674 - Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
(In reply to Bogdan Maris, QA [:bogdan_maris] from comment #8) > We tested the new languages added in the list of source languages, and all > looks fine from QA point of view (played with the translation and checked > that the data is stored in FHR). > Testing was done on Windows 7 64-bit, Windows 8.1 64-bit Surface Pro 2, Mac > OS X 10.9.5 and Ubuntu 14.04 32-bit using latest Nightly (buildID: > 20141010030201). > > Closing this as verified fixed since it was verified on the target milestone. We extended the testing on the same platforms using Firefox 34 beta 1 and latest Aurora 34. Marking as verified on firefox 34 as well.
You need to log in before you can comment on or make changes to this bug.