Closed Bug 1450571 Opened 7 years ago Closed 7 years ago

Remove translation code

Categories

(Firefox :: Translations, enhancement)

enhancement
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: ntim, Unassigned)

References

(Blocks 1 open bug)

Details

Attachments

(2 files)

I believe the translation code is now abandoned and does not work. I could be wrong however... There are add-ons which can provide this functionality.
(In reply to Tim Nguyen :ntim from comment #0) > I believe the translation code is now abandoned and does not work. I could > be wrong however... It's covered by automated tests, what makes you believe it doesn't work?
Please let me know more about this bug in detail. Thanks
Flags: needinfo?(ntim.bugs)
Flags: needinfo?(felipc)
(In reply to Tim Nguyen :ntim from comment #0) > I believe the translation code is now abandoned and does not work. I could > be wrong however... > > There are add-ons which can provide this functionality. The page language detection (French) works fine, but this is what I get when I hit the translate button.
Flags: needinfo?(ntim.bugs) → needinfo?(florian)
I also tried with yandex as provider, and while language detection works, clicking translate also gives me an error.
Attachment #8964203 - Attachment description: Screenshot of not working translation feature → Screenshot of broken translation feature (bing)
Where can I check for translation code? please guide me
Flags: needinfo?(ntim.bugs)
(In reply to Manish Kumar from comment #5) > Where can I check for translation code? please guide me We're not sure whether we want to remove it yet :) Once we'll have made a clear decision, I'll let you know. The code is in browser/components/translation.
Flags: needinfo?(ntim.bugs)
(In reply to Tim Nguyen :ntim from comment #4) > Created attachment 8964204 [details] > Screenshot of broken translation feature (Yandex) > > I also tried with yandex as provider, and while language detection works, > clicking translate also gives me an error. FWIW, the language detector is done client-side, so it will always work. The translation is done server-side and requires a valid API key from either google or yandex, which we currently don't have.
Flags: needinfo?(felipc)
Tim, you are confirming that at least language detection and showing the translation bar works fine. To try the translation feature, you need to provide an API key for a translation service, like Felipe said in comment 7. Last I heard (that was in Q1), our BD team is still working on getting such an API key that we could distribute to users.
Flags: needinfo?(florian)
Ok, I guess the lack of activity in the past months mislead me :(
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: