The slash character '/' seems to prevent any translation.

[gbdomubpkm]

Wanting to include an https link in a translation (wish it could be included), I thought that was the one blocking the translation. But in fact it is only the slash character / which blocks the translation. You can test by putting a slash at any place in a sentence.

A workaround is to substitute the slash character by another to allow translation, for example the backslash \ 🙂

This bug doen't exist on the online app https://lingva.ml/

[aparatext]

Weird. The URI should have been encoded. I'm working on a new app and have some upcoming work deadlines, so I might not be able to fix it in the coming weeks. Sorry for this inconvenience.

[aparatext]

https://lingva.ml/api/v1/auto/ru/https%3A%2F%2Fgoogle.com%2F doesn't seem to work. The URI is encoded, but the server doesn't seem to respond correctly.

[aparatext]

This seems to be tied to thedaviddelta/lingva-translate/issues/68. I'm afraid this could be an upstream issue.

[thedaviddelta]

Hello guys!

I'm sorry to inform you that indeed this bug happens because of Lingva's API. But, unfortunately, as mentioned in that issue, it's not caused by Lingva itself but because of a problem on the framework level.

It has already been reported several times to the maintainers, as you can see there, but it has been constantly ignored.
I'm sorry I cannot do more about this, you can follow the evolution on the linked issues.

Thanks for creating this software using Lingva's API!

Regards, David.

[gbdomubpkm]

@thedaviddelta
On Volla phone with morph browser:

[aparatext]

This Lingva bug seems to only affect the Rest API. I didn't quite get how, but it doesn't impact the front-end.

[thedaviddelta]

@walking-octopus Yes exactly, that's just was I was going to say.
@gbdomubpkm As I described yesterday, this is a bug related to Lingva's API, not to Lingva itself. Indeed, this bug happened on both in the past, but a Vercel member was able to solve it. The problem is that the bug was still present on API routes, and has been ignored since then.

I recommend you both to check the issues I linked, and the issues linked inside them, if you want to get a deeper understanding of the topic.
For the moment, I just can say that. It's not in my hand.

Regards, David.

[gbdomubpkm]

OK... thanks for the clarification @thedaviddelta !
Maybe there is an hope that the problem could be solved for translate-ut too as in Lingva even if it isn't solved in the API.. 😉

[gbdomubpkm]

Is a total or workaround solution possible at this point?

[thedaviddelta]

The 3rd opened issue is still being completely ignored... vercel/next.js#36719