Lingoes Text Capture Extension

Support Lingoes to capturing text and translate it in your browser, Use this extension you need to install Lingoes Translator from lingoes.net

Total ratings

3.13 (Rating count: 16)

Review summary

These summaries are automatically generated weekly using AI based on recent user reviews. Firefox Browser Add-ons does not verify user reviews, so some user reviews may be inaccurate, spammy, or outdated.

Pros

Good selection of dictionaries
Ability to add multiple dictionaries

Cons

Translation dialog appears after any selection, even an image
Translation dialog works sporadically
Original dictionary files have been tampered with

Most mentioned

Doesn't work
Doesn't work on Firefox
Translation dialog appearing after any selection

See reviews for Lingoes Text Capture Extension on Firefox Browser Add-ons

Upgrade to see all 17 reviews

User reviews

Recent rating average: 3.60

All time rating average: 3.13

Upgrade to see all 17 reviews

Rating filters

Date	Author	Comment
2024-07-19	Firefox user 16069213	tốt
2022-12-25	GanJingWorld	Gan Jing World is a clean, curated universe and a dynamic, overlapping network of integrated platforms and services. ==> https://www.ganjing.com
2022-02-16	Zxy	设置里“划选取词”和“双击取词”都能起作用。
2021-11-03	Zoltan	to make lingoes work on firefox make sure you run lingoes as an administrator, also use translate selected text, and double clicking option in the configuration.
2021-01-14	Firefox user 13505469
2020-08-22	vonhutrong	It doesn't work.
2020-05-25	hiphopboy8x	not working
2020-02-29	ismail
2019-03-22	simon
2018-11-09	Frédéric Jeanbart	I like Lingoes since it has a good selection of dictionaries. Howerver, this Firefox module only works if Lingoes itself is configured to have the translation appear whenever you select some text (selection mode - the cursor mode translation doesn't work whatever Lingoes configuration). And it does so with important flaws... After exposing these, this comment ends up with some recommendations... Flaws (4): 1) The translation dialog appears after ANY selection, even an image (which, obviously, it can't translate). Thus if you select something just for the sake of copying or highlighting, the translate dialog will always appear and try to fetch a translation. 2) It works very sporadically ! Either Google Translate or Microsoft's, I always end-up clicking numerous times on the little arrow in the dialog's title bar so as to get a successful hit for fetching the translation (about 4 to 6 times in average before it finds it, otherwise it shows an error stating that it couldn't find the information). EXACTLY like in Lingoes btw, of course. 3) It seems like the "official" or original dictionary files have been tempered with. For example, having the "Concise English Dictionary" to display entries for arbitrary numbers like 14, with a definition stating "the cardinal number that is the sum of thirteen and one - being one more than thirteen", is simply ridiculous as it does not fit in any so-called "Concise" dictionary... 4) Though it's not bound in the configuration menu, Typing Ctrl-C over a selection will open up the translator. If the selection is only one word, it will show the definitions from all active dictionaries, something which always work since it uses the local dictionaries... BUT hey man, usually when we type Ctrl-C, it's for copying something, not for translating the selection! This key combination binding, by default and which cannot be changed, is simply... no comment lmao Recommendations (3): 1) In Lingoes (this plugin uses Lingoes configurations), there should be an option to fetch a translation over a selection only when right-clicking+Ctrl for instance, it should be configurable like the combinations we can set for the cursor mode. An option allowing to only open the translator after some key combination, or from the contextual menu - or both. 2) Right-clicking should provide an option in the contextual menu either to use local dictionaries for some word under the cursor, either to fetch a translation from the web for the active selection (if there's such a selection) on the Web page - or on whatever other local application currently recognized (like Notepad) for that matter. That way, since selecting something does NOT necessarily mean that we want a translation, we'd still have the choice and the control. 3) For the above-mentioned to be relevant, fetching from Google translate or Microsoft's should be revisited by the coder : 1 out of 6 tries (rarely after the 1st shot, frequently after 6, sometimes not at all after xx tries), is far from being usable - I'm not even talking about efficiency here -: it's more like a gambling button than anything else. More over, why not give the option to select SYSTRANS or others since they are available (and works similarly to Google's or Microsoft's, no more nor less hit probability when fetching) ?

Upgrade to see all 17 reviews