Quote:
Originally Posted by aldazo
Hello again.
1. Just to be clear, does this mean it could be possible to bring the offline translator as an overlay using the koreader UI? or I am confusing things again? 
2. When you say "open ... on top of" using the PROCESS_TEXT intent, you mean opening it as an activity not necessarily as an overlay, correct?
3. You mean the "translate button" would manage a list of 3rd party translators to choose from the same way the "dictionary button" can bring on colordict, goldendict, fora, etc. Right?
In that case one should not use the dictionaries.lua to bring up translators because a dictionary pops up when you select one word, and the main function of a translator is to translate phrases or sentences.
It would be better to create a translators.lua that acts as a dictionary.lua but only when you select more than one word and hold the last word for about a second. I cannot imagine how much work would be needed but would be interesting.  |
1. Nope
2. Nope
3. Yes. That's exactly what needs to be implemented. Basically a copy of
https://github.com/koreader/koreader/pull/5108/files. The example I gave on the previous post is to show that the platform code is there and works without modifications, but the frontend code to manage third party translators needs to be implemented.