Skip to main content

On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Thank you for your patience! :)

I've fixed the issue with TranslateAI, OpenL Translate, Lingvanex Translate and Gemini. I have a few more things I need to sort out, but hopefully the beta will drop tonight.
Thank you for all the debugging, it has been very helpful!

Text Translator2 seems broken. I can't even get it working with Postman. Besides it doesn't expect JSON but rather

"application/x-www-form-urlencoded"

and I am not entirely sure what it is, but even doing a POST with that format on Postman returned the same error message.

If you'd like to use Gemini or a similar LLM that is not purposed for translation, you could prompt it simply as;

```

{

    "contents": [

      {

        "parts": [

          {

            "text": "Translate this text to Swedish and only return the translated text: %text%"

          }

        ]

      }

    ]

}

```

The above format is not possible in 0.4.9 but will be in the beta release.
I tried it a little bit and it did not seem to break at all like the local LLM models I tried.

I'm curious to how you got Cloud Translation API to work. Definitely not straightforward with that one..

Thank you for the info. I would for sure be interested in adding Azure if they have an automatic limit or if it is easy for general person to set up. Problem is that they refuse to confirm my identity. Tried all my debit cards and it just won't work, so I can't even test it..

(1 edit)

Hi,

Thanks for the new update—it's super neat! :)

Gemini is now up and running perfectly for me.

I even got Text Translator2 to work! Turns out, you don't need to put the value in a JSON array. Just use this for the Body:  source_language=en&target_language=hu&text=%text%, and it worked :)

All the accessible APIs from rapidapi.com are working now. I've tested quite a few, and they've all been successful, so I'm guessing the rest should work too, assuming they're available. (A couple aren't, unfortunately.) This means we can now use not only APIs from the Translation category but also AI APIs from the Artificial Intelligence/Machine Learning category for translations.

I also tested the Azure AI Translator, and it worked without a hitch. It has an automatic limit of 2 million characters per hour, and once you hit that, it'll stop working. You can find more details here: Service limits for Azure AI Translator Service. I found it pretty straightforward to set up, and I'm just an average person :) You need to register, which requires a credit card, then go to 'Create a resource', search for 'Translator', and hit 'create'. Fill in your details like name, region, and select the F0 free tier. Hit 'create' again, and you're all set.

Here's how to configure it:

Azure AI Translator:

URL: 

https://api.cognitive.microsofttranslator.com/translate?api-version=3.0&to=your_language_code

Headers:

{

    "Content-Type": "application/json",

    "Ocp-Apim-Subscription-Key": "YOUR_API_KEY",

    "Ocp-Apim-Subscription-Region": "YOUR_REGION"

}

Body:

[

    {

        "Text": "%text%"

    }

]

Text Output Path:

.translations[0].text

Now, the Cloud Translation API is a bit different; it doesn't have an automatic limit. This could be a bit risky if you're not paying attention, because if you go over the 500,000 character/month limit, you'll automatically start paying. But don't worry, you can set up a Budget Alert. You could, for example, set a $1 limit and then get email notifications when you've used 50%, 90%, 100%, and even 150% of that amount. Setting this one up was pretty simple too. If I remember correctly, you just need to enable this: Cloud Translation API (which also requires a credit card), create an API key, and you're good to go.

And here's how to use it:

URL:

https://translation.googleapis.com/language/translate/v2?key=YOUR_API_KEY

Headers:

{

    "Content-Type": "application/json"

}

Body:

{

    "q": "%text%",

    "source": "en",

    "target": "hu"

}

Text Output Path:

data.translations[0].translatedText

Seriously, thanks again for all your hard work. This is a massive help! :)

Legend! Sorry, I've been away on holiday and got caught up with other things before that. I'll respond to this in another thread soon, I'm trying to reorganize the Itch.io forum because.. well.. it's just a terrible forum format. Locking and unsticking this thread.