lingva-translate
lingva-translate copied to clipboard
thedaviddelta
Show pronunciation text, verified status and 'definition of word' and 'translations of word' for available strings
Thank you so much for develop this front-end web app :1st_place_medal: :heart:
1. Show pronunciation text.
Why it is important? I saw lingva offer option for play audio about translated word but it still difficult to recognize then user need to go to gtranslate site.
Read book
2. Show verified status for available words and sentences**
Why it is important? It help to trust the specific translation bit more and less possibility to incorrect.
3. Add definition of word and translations of word components
Why it is important? it helps to gather more details about the word and if it other language word than to most popular english then more useful for reader and get meaning of it in depth.
3.1. Option to search appeared words in translation of word component
If you able to implement it successfully then let to re-search each words appeared in translation of book component result. as you know, it's simple enhancement, put words to search box when tap.
4. Show other available words for the translation
Gtranslate has a option to view other available words for the translation. If that also possible to take then we have complete front-end, but i dont know if that easy possible and may be tricky
Why it is important? - There're many translations are not verified and incorrect for many languages (some times verified translation also not perfect) then that feature helps check other available translations for it
Hello and thanks for your interest in the project.
All those GTranslate functionalities are cool and I used to use some of them, specially the latin transcription of external alphabets, because I'm studying mandarin. The problem is that Lingva is currently using the mobile version of GTranslate for scrapping, because it's infinitely easier to extract information from it, doesn't use minified and constantly modifying CSS class names, and loads a lot faster.
Maybe the adding of every GTranslate functionality is a cool plan for the future if I find it viable to scrape the main page, but I'd require to nearly rewrite the whole project and at this moment I don't have the time for doing that. Anyway I'm letting the issue open because it's a cool enhancement wanted for the future, but I'd ask you to join both posts into this one for a better feature request following.
Regards, David.
@TheDavidDelta I updated the post as you said. Today first time knew it has mobile version like that, usually i only have seen main site loads as mobile friendly mode on phone. so far i only expect (1) and (2) features and rest are to make this project complete front-end alternative and comfortable for users.
https://github.com/crow-translate/crow-translate
Thanks for sharing this alternative! But the problem with QOnlineTranslator (crow's library) is that it uses the GTranslate's public API instead of scraping, so it's not a privacy-concerning solution.
Thanks for sharing this alternative! But the problem with QOnlineTranslator (crow's library) is that it uses the GTranslate's public API instead of scraping, so it's not a privacy-concerning solution.
Sorry, i didn't noticed it.
I thought to have lingva on whoogle; recently maintainer added it and display directly on UI https://github.com/benbusby/whoogle-search/pull/360 @TheDavidDelta I considered to let you know for avoid happen conflict with future developments. If there any breaking changes then you may able to PR to whoogle for enhance or let maintainer know about it before everyone notice and start to report. But actually that's not your responsibility at all or doesn't necessary to care however it's opensource and relative project.
I thought to have lingva on whoogle; recently maintainer added it and display directly on UI benbusby/whoogle-search#360 @TheDavidDelta I considered to let you know for avoid happen conflict with future developments. If there any breaking changes then you may able to PR to whoogle for enhance or let maintainer know about it before everyone notice and start to report. But actually that's not your responsibility at all or doesn't necessary to care however it's opensource and relative project.
Wow this is amazing! Thanks for letting me know. It's an amazing project and I'm proud Lingva is there! And as I've seen in the implementation there shouldn't be any way of breaking it unless I change the URL format.
I would LOVE to see the pronunciation text included. I am learning Mandarin too and I've been looking for this exact project for a while now and yours is perfect. Unfortunately, It is not of much use to me without the pinyin/pronunciation text feature. 😢 I greatly appreciate your hard work! 👍
I didn't know about this very nice online app until a short time and a native nice specific app using lingva api for Ubuntu Touch smartphones here , but, am I mistaken or the synthetic voice of online lingva translate is only female? If so, having the choice of a neutral male voice would be appreciated. Thanks for your nice work.
@gbdomubpkm Oh, amazing, thank you for sharing this! I'm always super glad that people creates more FOSS with Lingva!
And about the voice, it's just the same one as in GTranslate, we scrape it from there. I just described the process in #103.
Regards, David.
Hey, we found a way to scrape Definitions, it's pretty much a black-box of code though. https://codeberg.org/SimpleWeb/SimplyTranslate-Engines/src/commit/941880810d453a6f9a78c59144ecfd5196ac167e/simplytranslate_engines/googletranslate.py#L260 Feel free to check it out, we've got the original code from a gist somewhere, I can't find it right now but I think this might be useful for this project either way.
I'm always super glad that people creates more FOSS with Lingva!
@thedaviddelta add it to readme. also, whoogle
@metalune1 Thank you so much for this!! I've been working these last weeks in this and successfully scraped all the information! I extracted the whole scraping proccess to an external NPM package, and implemented part of the information in main Lingva. More info in #113.
This solves much of the requested in this issue, but not everything (the definitions and extra translations haven't been implemented in the UI for the moment). I'll just let this open in order to have record, but now we know there's a viable solution for all of this!