You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 4, 2023. It is now read-only.
Update bergamot-translator wasm module (aka engine) in the web extension and apply the pertinent changes to take advantage of the latest implementations and features:
Review the entire worker and make sure we are using correct config/options and switching things on/off properly (fixed via Update bergamot translator to v0.4.1 #111)
Updating the priority of some of the tasks owing to the priority related discussions in the last plenary meeting (10 Feb, 2022). Basically, QE feature takes more precedence than downloading engine artifacts from gcp instead of github release.
Technically, the bergamot translator module is updated whenever a new feature is added or there is an API change or there is a performance improvement in the engine. Additionally, this task might be repeated for each Milestone because each Milestone integrates new features.
Closing this one as the module is already update for all the tasks of Milestone W3.
I will create new one for other Milestones.
I am removing QE specific tasks and tracking them under the meta issue #26
Update bergamot-translator wasm module (aka engine) in the web extension and apply the pertinent changes to take advantage of the latest implementations and features:
Phase 1:
Phase 2:
The text was updated successfully, but these errors were encountered: