this post was submitted on 20 Aug 2023
63 points (93.2% liked)

Firefox

17937 readers
39 users here now

A place to discuss the news and latest developments on the open-source browser Firefox

founded 4 years ago
MODERATORS
[email protected]
63
Linguist, an ultimate translation browser extension (vitonsky.net)
submitted 1 year ago by vitonsky to c/[email protected]
4 comments fedilink hide all child comments
 

cross-posted from: https://programming.dev/post/1924228

Hey everyone, check the Linguist

  • you can translate texts offline (with sent no one single byte to a Google and stay private)
  • a lot of features and flexible configuration
  • dictionary + history for learn languages
  • it is are hackable - you can write code to use your own translation service
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 2 points 1 year ago (1 children)

So this uses Bergamot by default, that's really interesting! Is there a reason why you didn't merge it with Mozilla's Firefox Translations extension?

[–] vitonsky 2 points 1 year ago (1 children)

It's good question. If a Mozilla people interesting for it - feel free to email me. As i know, for now a firefox translator is just a wrapper over Bergamot Translator while time a Linguist is a common purpose translation system for all major browsers, that embedded a Bergamot Translator as one of a great translator implementations.

For now Linguist had no reviews by influencers and it did not appears on reviews of a firefox addons blog unlike some other addons like proprietary Mate translate and open source TWP - Translate Web Pages. If we together make Linguist visible for a wide people, maybe Mozilla will pay attention for a Linguist too and we can integrate Linguist into a Firefox with all features it have

[–] [email protected] 3 points 1 year ago* (last edited 1 year ago)

I see, that's true, it could use some more publicity! Still, I think you could get in touch with Mozilla somehow already.
However, thinking more about it, it does make sense that they'd be separate since yours is more like a framework to implement various translation systems, as you said. I could still see some of the features you implemented being contributed to the Firefox Translations extension, for the sake of keeping it in scope, I'm not sure which kind of things they would like though ¯\_ (ツ) _/¯