Home Creators Posts Import Register Favorites Logout

Videos

  • translator-openai-batch-api-translation.mp4
  • translator-batch-api-apply-translations.mp4
  • translator-codex-assistant-demo.mp4

Downloads

Content

Hello fellow translators,

Translator++ 8.11.11 is here, and this update brings a major overhaul to batch translation. Whether you are sending regular translation requests or using a provider's Batch API, the redesigned Batch Manager gives you a better place to follow your work, inspect results, and recover translations that need attention.

The OpenAI API Translator has also received a major upgrade, and you can now enable Codex and Claude Code as assistants to help investigate and potentially fix problems during your translation workflow.

Let me show you what is new!

More affordable translation with Batch API

Translating a large game can involve tens of thousands of lines. With a supported Batch API, you submit the work for processing in the background instead of waiting for every request to finish immediately. In return, some providers offer batch processing at half the normal API price. The discount, available models, processing time, and pricing depend on the provider, so check your chosen service before submitting a job.

Combined with Translator++'s translation optimizations, this can make a big difference. You do not always need the most expensive cutting-edge model to get a result you are happy with.

For example, I translated a project of about 59,000 rows using GPT-6 Luna for less than $2. I was quite satisfied with the result! In my experience, a well-configured workflow can produce translations that are comparable to, and sometimes even better than, human translation. Of course, the result and cost will vary depending on the game, language, model, and settings, and reviewing the translation is still important.

The project contains approximately 59,000 rows.

The Luna usage shown here came to $1.48.

Batch API is now easier to use

You can now submit Batch API jobs directly from the supported OpenAI API Translator batch translation workflow. Set up your translation through the familiar OpenAI Chat settings, choose a model, and review the request before submitting it. This brings the available OpenAI API Translator options into the batch workflow, making it easier to use your existing setup for larger jobs.

🎬Easier way to translate using Batch API

We have also expanded provider support. Alongside existing options such as OpenRouter, the LLM Batch API now supports Claude, Mistral, and Grok. Available models and batch features depend on the provider.

Meet the overhauled Batch Manager

The Batch Manager now gives you a clearer view of your translation work in one place. It can display logs from regular batch translation requests as well as jobs submitted through a Batch API. You can inspect the requests and results, check their status, and find translations that need another look.

For Batch API jobs, you can review and filter results before applying them. You can also apply translations from multiple batches at once, or select individual batch items to apply or re-apply when you need more control.

Apply translations from multiple batches together.

Select individual items when you want to apply or re-apply specific results.

🎬Applying translation from Batch API

Recover translations with local models

A good translation can sometimes fail validation because its formatting does not match what the game or project expects. That does not necessarily mean you have to throw the translation away and pay the original provider to translate everything again.

The new local batch recovery workflow can use a cheaper local model to repair failed results. The idea is to keep the translation produced by your chosen provider and ask the recovery model to fix the formatting problems that prevented it from passing validation. Configure the recovery model and run recovery from the Batch Manager; Translator++ handles the repair workflow and lets you review the results.

Review recovered translations and their validation results.

Choose the local model and recovery settings for your workflow.

You can also retry failed translations when that is the better choice. Recovery is a way to salvage useful work, though its results should still be reviewed.

More control over translation validation

Validation helps catch problems before they find their way into your project. Depending on your settings, Translator++ can check things such as line counts, game codes, and other formatting requirements.

You now have more granular control over these checks. Choose which issues should block a translation, which should produce a warning, and which checks to turn off. You can save your preferences for each project.

Choose how validation issues are handled when applying Batch API translations.

Improvements to normal batch translation

Regular batch translation has received major improvements too, including configurable validation to give you more control over the results that enter your project.

Adjust translation checks to suit your project and the level of protection you need.

When using the OpenAI API Translator, a problem in one row no longer means you have to lose every valid translation in the same request. Translator++ first attempts the corrective retries you have configured. If validation still fails, it applies the rows it can safely identify as valid and leaves the existing translations in the failed rows unchanged.

You can inspect the logged request and response in the Batch Manager later, so you have an opportunity to review and salvage useful translations instead of starting over blindly.

Codex and Claude Code as assistants

Sometimes a translation problem needs more investigation than a simple error message can provide. You can now enable Codex CLI or Claude Code in Options → Assistant to help troubleshoot problems and potentially fix them.

For example, Resolve with Assistant can help investigate game injection problems. You can follow the assistant's progress, answer its questions, and stop the task when needed. Tasks can also continue after you close the dialog or restart Translator++.

Enable and configure the CLI assistant you want to use.

🎬Codex Assistant in Translator++

These assistants use their respective CLI setup and sign-in. Review their work and any proposed changes as you would with any tool helping you modify a project.

A better workflow for bigger projects

My goal with this update is to make large translation jobs easier to afford, easier to monitor, and less frustrating to recover when something goes wrong. The new Batch Manager brings the information together, while validation and recovery give you more ways to protect and make use of your results.

If you're interested in translating Tokimeki Memorial 4, yes, this add-on is available for free, so you can translate it into your own language.

Thank you as always for supporting Translator++ and making these improvements possible. I hope you enjoy the update!

Happy translating,

— Dreamsavior

Files

Comments

Emre Arslan

I've been following this app for a long time and I have a question: can I translate games that use game engines like Unity or Renpy into any language I want with this app?

Dreamsavior

Thank you for following this Project.Yes you can.

Emre Arslan

Great, I'll download and try it when I get home. Okay, but how do I translate games using Unity and Renpy? Are there any tutorial videos or anything?