|Syntactic Confectionery Delight
De-googleizing translation scriptsby Aldebaran (Curate)
|on Nov 05, 2022 at 03:12 UTC
Aldebaran has asked for the wisdom of the Perl Monks concerning the following question:
I have to divide my life into things that I can change and those I can't, and I wasn't prepared for how quickly I would need to look for google alternatives when they alleged I was a computer and locked me out of my account. I had to realize how dished out to them I truly am. I did not choose for this to be the year I would have to talk about Google, and would be embarrassed for others to know how much this feels like a divorce or jilted lover saga. Google and I: we had some good times, but we've grown apart. Having to switch from my familiar android just takes my breathe away, but I'll come out the other side. So, I'll go with apple until they have some outrageous untenability, and so it goes with the corporate goliaths: pick your poison and exposure.
I rely on google heavily in translation scripts and tried to work up a reasonably-sized SSCCE for it. This script worked better before it worked worse, but it should suffice as a starting point:
What I typically do is use perl to wrap the trans call from the soimort translate shell on github. I'm not wild about this dependency anymore, and the resulting calling code is hideous, but it has been reliable in at least this form:
I'd like to get away both from this trans package and google, so I'm wondering what else is out there. I think this answer has changed over the last year or so with the balkanization of the internet. For example, in the following snippet, I think the bing one succeeds and the yandex has failed (from my perspective), and this, as I say, over the course of the last year:
So let me ask the question like this, given that I want to get away from the trans package and google, what options do I have for machine translations with perl?
Thanks for your comment,