Add translator suggestions for text correction

When detect mixed content on page, suggest "auto detect" language in popup and auto translate from this language.

And allow to user decide edge of mixed content.

If translator has no support auto detection language then will use one of page languages (as now)

Make "core" as package, to decrease complexity of init project and prevent install from many directories

Maybe we should make repo as project

Prepare release

• Generate locales files for all languages
• Rework product description
• Update screenshots
• Translate product description

Publish in browsers stores

• Firefox
• Chrome
• Edge
• Opera
• Kiwi

Implement option "show translate button once", which will use flag which set after show button and unset after any "selection" event.

When flag is set, then button is not shown.

It may be useful for sites like twitter where after click on oter place, button can appear again. With this option button will not appear until user will select text again.

Think about make this option enable by default

Add option "never translate this site" for cases when enable "translate this lang always", but current site must not be auto translated never

Prevent focus by click on lang panel while focus on textarea in text translator

It useful for continue input after change language.

At least test this

Optionally sync data with firefox/google account

Must be able configure data for sync

Data for sync:

• Preferences
• Dictionary
• History

For cases like site https://online-timer.ru with high frequency untranslatable changes translator work useless.

It not require real translate request and this case must be optimize to economy traffic, requests number and performance.

Concept

Skip translate a language independent chars for simple cases.

Detect language independent chars in text, search in translator cache a translates with original text which match with current request, but with ignore this chars on their positions and while match return translated text from this cache with replacing chars to actual.

Example:

Text in cache: Article number 1, posted in 2021 year.
Current request: Article number 523, posted in 7925 year.

Text pattern: ^Article number (\d+), posted in (\d+) year.

Notes

To do it perform, we may use temporary registry with data signature like this

type HotTextSignature = {
  pattern: RegExp;
  text: string;
  translate: string;
  replacements: Record<string, string>;
}

And keep it short time (few seconds/minutes) after last use.

Switch for translate selected text set as text and translate same text. Add it to favorites give confused result.

Just swap source text and translation result.

Add option "default for this language" which will remove options for this language but will not delete entry if it not empty

See src/layouts/PageTranslator/[email protected]:120

• src/layouts/PageTranslator/[email protected]

Configure test after build to check zip archives

For example use this: https://github.com/mozilla/web-ext

• Rewrite to async storage use
• Migrate data

• Migrate all data for all tabs
  • Page translate
    • Use async storage for PopupPage.tabSet
  • Text translate
• Migrate config

Refactor this

Popup tab text translator have hungry height size and with big text it overflow popup height and show scrollbar.

We must use border-box

Implement text speaking for text translation.

It must be module. For start it may be not configurable by user

While create div, connect shadowRoot at same time and load styles.

It important to prevent twitch translate buton, it looks ugly

Add tests for translators in core directory

It important to catch bugs and prevent deploy with broken modules

Fix it in popup

Optionally inject contentscript in iframes

It useful for tweets and other widgets on page

It may be enable by default

Manifest option "all_frames": true

Add images in readme for each browser extensions store

Like images here:

• https://github.com/mue/mue
• https://github.com/Authenticator-Extension/Authenticator
• https://github.com/floccusaddon/floccus

Sometime, after quick switch languages while translating in TextTranslator text may be lose.

Seems cause in inconsistent switch handling.

Translate manifest files to other popular languages

Improve auto translate section view

Add optional spell check to text translation

Proposal from #36 (comment)

Add option for remember "auto detect" direction for translate page. In this case auto translate will use this direction too.

This should remember for all sites or for each domain?

Often while selection 1-3 words on the page, browser can't detect language.

At this time we just use page language.

I suggest implement option for enable preferent "auto detect" language instead page language if current translator support this feature (usually is that). Otherwise will use page language or last chosen direction depends on current settings.

Add 2-3 screenshots in readme

Add button for choose translator in translate text component

It require implement translator parameter for translate request and getting translator modules in component while init

Change size between sections for options to visually separate segments (obey the principle of proximity)

Add action for build and publish release by commit with some tag like "release"

Add option for disable "show original text" block in select translator

Example: https://www.opennet.ru

On this page text align is center and popup with translate result are inherit this style.

We must set it explicity

Use router for navigate between sections by URL hash

Thank you for creating this promising addon. I'd like to offer several proposals to improve on it.

1. Currently it often fails to automatically translate some webpages. For example, on the following pages(even if "Always translate this language" is ticked):

(1) nasional.tempo.co/read/1491253/pasien-sembuh-covid-19-hari-ini-39-726-orang/full&view=ok
(2) jdih.tabanankab.go.id/berita/159/rapat-koordinasi-satpol-pp-disperindag-dan-dinas-lingkungan-hidup

2. Pls allow translation of webpages of any original language into English.This function is important and indispensible, because in many cases webpages are in mixed languages.

   In many cases the original language of a webpage is not detected or wrongly detected. For example, the original language of the following webpage is detected as English by your addon and can not be translated, but actually it also contains many Indonesian words.

https://www.linkedin.com/search/results/people/?keywords=menteri%20pendidikan&origin=CLUSTER_EXPANSION&sid=6ld

When I use Chrome browser(with in-built Google Translate function), the original language of the above webpage is not detected because it is in mixed languages. However,the webpage can be translated into English with the Context Menu button as shown by the picture below.

(1) The original language of that linkedin page is not detected by Google Translate, because it contains both English and many Indonesian words. So it just shows "Detected Language" instead of any specific language.

(2) But I need to translate the Indonesian words on that page and I can achieve that by using the Context Menu button as shown by the picture below.

3. Original Text on mouseover. This funciton is also indispensible as shown by the picure below.

Could you pls consider these proposals? Thank you and best regards!

Do it

It happens while showing and hidding a block contains buttons for apply changes

Now Linguist uses an third party services to translate texts. It is not private, because users send their texts to a servers like Google, Yandex, Bing, etc.

We need to allow users to use offline translation that will not send their texts to internet and will process it local on user machine. It is technically possible right now with custom translators, we have guide about it, however it is not embedded solution "for geeks only", so most users will not use this way.

Thus, we have to implement embedded module to offline translate text.

Requirements to candidate

• High quality of translation
• High performance
• Support WASM or ready of maintainers to implement it
• Many languages (at least 6)
• Support all translate directions between supported languages
• Not so big size of additional files (like dictionary or AI models)

At this time we collect all tags and only after it start translate.

This way lead to long waiting of translate page.

• Instead we must check visibility while scan tags and instant translate it if it visible and in viewport boundaries.
• Also we can set priority for tags content instead attributes
• Also we can lazy collect DOM nodes, instead collect all while start
• Also we can group nodes with limit by length

Some sites not have lang attribute for html tag, but set it with JS.

We should wait full loading page and after it check lang attrubute again, even if it empty while DOMContentLoaded.

Suggest language direction while translate text from auto directon.

Do it optionally, if translate module support this feature

Add checkbox "auto translate this site for this lang"

It need for cases, when user not wanna enable auto translate this language for all languages

Fix migrations for new IDB scheme to prepare to release

Sometime translates have wrongs which lead to misunderstanding.

We must implement popup with original text, which will show by hover, and maybe only with pressed hotkey.

It should be optionally feature.

Add wrappers for requests, to bound handler and helper.

This is required to ensure correct types. We have too many wrongs due to this mistyping

Purposes

• Type bounding hook and handler of request
• Prevent non unique endpoint names
• Optionally type checking in runtime by setting validator in property

How it should work?

Is it have priority over all other options? Or site specific options have priority on it?

Implement config migrations for changes struct with updates