Closed darhma closed 3 years ago
I'm adding query parameters to the url for selecting the engine. But it gives me an error:
I tried to use twitter's server and added the lang
parameter to see if the UI language will change and it worked just fine:
Arabic:
Spanish:
Note that if I changed the parameter to anything other than libre
, it won't give an error and will translate the text:
Maybe it's a server side problem.
Update: it's now weirdly working just fine. Too quiet to be believed. Don't know what happened:
I tried to enter https://metalune.xyz/?engine=libre as a custom server but it didn't work.
You forgot the subdomain translate
: https://translate.metalune.xyz/?engine=libre
I just tried again with https://translate.metalune.xyz/?engine=libre but it still doesn't work.
I think it's because I didn't add support for parameters. If you inject it in the code though. It will work. I'm now working on it.
Note: If the instance didn't have LibreTranslate turned on. The client won't detect that yet.
I've now added LibreTranslate detection.
I am trying the app again but I don't understand how to select LibreTranslate as the translation engine, even using an instance that supports it like https://simplytranslate.org/ it is still possible to select a different engine or it is a feature that has been deleted?
The support for an engine other than GoogleTranslate has been removed. We'll readded though. There were so many bugs and collisions that we needed to remove it.
Thanks for the answer, I had imagined that the implementation could present some problems and that it had been removed for this. A little sorry about that but you have made an understandable choice, in any case the app seems to work well so keep up your good work. Thanks
From the website https://translate.metalune.xyz/ you can select the translation engine (google/libretranslate) it would be useful to add a similar option in the app as well.