Closed
Bug 973271
Opened 11 years ago
Closed 6 years ago
Automatic Translation
Categories
(Tracking Graveyard :: Firefox Operations, defect)
Tracking
(Not tracked)
RESOLVED
INACTIVE
People
(Reporter: MarcoM, Unassigned)
References
Details
(Whiteboard: [tracking] [translation])
No description provided.
Reporter | ||
Updated•11 years ago
|
Whiteboard: [epic] → [epic] [translation]
Reporter | ||
Updated•11 years ago
|
No longer blocks: fxdesktopbacklog
Whiteboard: [epic] [translation] → [tracking] [translation]
Comment 1•9 years ago
|
||
Hi,
I haven't heard of this for quite a long time, so are there any updates about implementing this feature and when can we expect it?
Comment 2•9 years ago
|
||
It was decided at the last meeting that the development of this feature was not plausible given the current Mozilla priorities for the required resources. As such, it has been (probably permanently) shelved. There has been some talk on using the Mozilla Intellego brand that we developed for a related project, but concerns about disambiguation have not been resolved.
Unfortunately, Intellego has reached a dead-end, at least for the foreseeable future.
Comment 3•7 years ago
|
||
What's the status for this feature? We still have plenty of code and strings around, and the prefs are already broken in the panel.
Is there any plan to remove the code from tree?
Comment 4•6 years ago
|
||
No activity for a while, closing.
Feel free to reopen if you disagree.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INACTIVE
Updated•6 years ago
|
Product: Tracking → Tracking Graveyard
The machine learning team is working with some EU partners (Edinburgh University, Sheffield University, Tartu University, and Charles University) to create an on-device translation engine, see [https://browser.mt].
However, as a first step we are creating a server based engine that's using the current code, see [https://youtu.be/ptmLzVeU0dk?vq=hd2160]. So for us it'd be extremely useful if this code stays around for a bit longer as we're currently using it to get our head around our future work.
You need to log in
before you can comment on or make changes to this bug.
Description
•