andrenatal1
Joined 4 years ago
Karma
74
Submissions
14
Member since
Jun 2
Recent submissions
Comment · 4 years ago
French is being trained by the consortium and is part of the scope of the grant, so we should have it at some point in June and we'll ship and update as soon we have it.
Comment · 4 years ago
The point here is that it simpler to have just one NMT engine in WebAssembly shipped bundled in the extension than runs in all platforms for free, instead of having to support and distribute multiple native builds of the engine that would be sideloaded and communicate with the extension via native messaging.
When the project started for example, the engine has incompatible with ARM, which we could just get for free with WebAssembly. The performance penalty of doing that was minimal for the user eyes, and so far we received less than a handful of complains about it.
Bundling the entire engine on Firefox was never an option for many obvious reasons.
Comment · 4 years ago
Yes, we are investigating how to support Firefox for Android.
Comment · 4 years ago
Thanks for using it! Best way currently is to keep using and reporting issues on [1]. You can see how the models are trained on [2] and file issues there too.
[1] https://github.com/mozilla/firefox-translations/issues [2] https://github.com/mozilla/firefox-translations-training
Comment · 4 years ago
Sure, like I mentioned in the article, you can embed the engine and the models in any web page to be run in a browser with proper WebAssembly and SIMD support.
You can have an example on how we did here [1] and test it here (I recommend using Firefox) [2]
That way you don't need a server and everything is processed in the browser, so no need of google translate, or any cloud service to have translations embedded in any website anymore.
[1] https://github.com/mozilla/translate [2] https://mozilla.github.io/translate
Comment · 4 years ago
Yes, like I said above that's something we've been discussing internally and is being considered. In this meantime, please feel free to file an issue in the repo [1] so we could track it:
[1] https://github.com/mozilla/firefox-translations/issues
Comment · 4 years ago
Yes, that's something we've been discussing internally and is being considered. In this meantime, please feel free to file an issue in the repo [1] so we could track it:
Comment · 4 years ago
You can find the engine used here [1], the API built around it here [2] and its WASM port here [3] and the WebAssembly matrix multiplication optimizations are here [4]
[1] https://marian-nmt.github.io/
[2] https://github.com/browsermt/bergamot-translator
[3] https://github.com/browsermt/bergamot-translator/tree/main/w...
[4] https://github.com/mozilla/gecko-dev/tree/master/third_party...
Comment · 4 years ago
Just did it, thanks for the suggestion!
Comment · 4 years ago
> Are there any plans for Mozilla to host this data? (Well, Amazon I guess to match addons.mozilla.org)
I'll bring this internally for discussion.
> I noticed the web page has Polish but not the extension. Is it not considered sufficiently high quality yet? (Looks like that might be the case from a quick test.)
The Polish model finished training after we had the extension reviewed and signed for distribution, so that's why we could already integrate it in the website, which is controlled just by my team, and not in the extension yet, but we'll ship it in the next version which might come next week.
This feature you requested is something that I consider interesting and important, would you mind filing an issue in the repo so we could track it [1]?
We did not find any large quality issues after quantizing the models.
In regards to the neologism in Spanish, that is yes a condition that the consortium is aware and working to remediate it.
Comment · 4 years ago
Thanks to you for giving the extension a try! This is a very interesting feature, and I'd like to consider it. Would you mind filing an issue in the repo so we could track and discuss it here [1]?
Comment · 4 years ago
Yes, the extension is being developed here [1] and the engine[2]/wasm[3] wrapper here.
The models and training pipeline are in the urls your posted and the evaluation of those models are hosted here [4]
[1] https://github.com/mozilla/firefox-translations [2] https://github.com/browsermt/bergamot-translator [3] https://github.com/browsermt/bergamot-translator/tree/main/w... [4] https://github.com/mozilla/firefox-translations-models/tree/...
Comment · 4 years ago
Hi, I am part of the team who developed this and the author of the article. You can ask me anything about it if you have questions.