How do I integrate attranslate with my AI coding agent like Claude or GitHub Copilot?

You need to modify your agent's system prompt to include attranslate commands and use the pipe-based workflow; for example, add instructions in AGENTS.md to invoke attranslate after adding new keys, as shown in the README's prompt examples. Ensure the agent outputs translations in the correct order for piping.

Can attranslate handle real-time translation updates in a live app?

No, attranslate is a CLI tool focused on syncing static translation files; it doesn't support real-time updates or dynamic translation in user interfaces, making it unsuitable for apps needing instant language switching.

attranslate vs i18next: which is better for managing translations?

attranslate is ideal for syncing files with AI agents and preserving manual edits, while i18next is a full-fledged JavaScript library for runtime translation management in apps. Choose attranslate for agent-driven workflows and i18next for client-side integration and frameworks.

What happens if I manually edit a translation file after using attranslate?

attranslate will preserve your manual edits in subsequent runs and never overwrite them, as stated in the 'Preserve Manual Translations' feature; it only translates new or missing strings to maintain corrections.

How does attranslate handle nested JSON structures in translation files?

attranslate supports 'nested-json' format explicitly, allowing it to sync hierarchical data; ensure you specify the correct format in the command to properly parse and translate nested keys without flattening them.

Is attranslate suitable for large-scale projects with many languages?

Yes, its efficient sync minimizes token usage and costs, but the agent workflow might become complex; you'll need to script multiple calls for each language and ensure agents handle terminology consistently across files.

Open-Awesome

attranslate

NOASSERTIONTypeScript

A CLI tool that assists coding agents in translating and syncing JSON/YAML/XML files with minimal token usage.

Visit Website GitHub

358 stars29 forks0 contributors

What is attranslate?

attranslate is a CLI tool that synchronizes translation files (JSON, YAML, XML) by translating only new strings, preserving existing manual translations. It is designed to assist coding agents in managing translations efficiently with minimal token usage, reducing costs and maintaining translation quality.

Target Audience

Developers and coding agents working on multilingual websites or apps who need to manage translation files efficiently, especially those using AI agents for localization tasks.

Value Proposition

It uniquely integrates with coding agents via a pipe-based workflow, allowing seamless translation updates while never overwriting manual corrections, ensuring both automation and human oversight.

Overview

A CLI to assist Coding Agents in doing translations

Use Cases

Best For

Syncing translation files for web or mobile apps with multiple languages
Integrating translation workflows into coding agent pipelines
Reducing API token usage in automated translation processes
Maintaining manual translation corrections in JSON/YAML/XML files
Managing healthcare or technical app translations with specific terminology
Detecting missing translations in CI/CD pipelines

Not Ideal For

Projects requiring real-time, dynamic translation updates in user interfaces
Teams using comprehensive translation management platforms with GUI and team collaboration features
Developers who prefer direct API integration with services like Google Translate without agent intermediaries
Simple apps with static, unchanging translations where manual file editing suffices

Pros & Cons

Pros

Preserves Manual Edits

From the README, attranslate never overwrites manual corrections in subsequent runs, ensuring human oversight is maintained and quality is improved.

Agent Integration Focus

It is designed specifically for coding agents with a pipe-based workflow, prompting agents to translate new strings efficiently, as highlighted in the agent workflow section.

Efficient Token Usage

Only translates missing strings to minimize API calls and reduce costs, which is a core feature mentioned in the efficient sync description.

Multi-Format Support

Supports various formats like JSON, YAML, XML, and more, making it versatile for different project structures, as listed in the usage options.

Cons

Limited Translation Services

The README states that services like openai and google-translate are deprecated, leaving only the 'agent' service, which locks users into coding agent workflows and reduces flexibility.

Complex Agent Workflow

Requires pipe-based integration and specific agent instructions, which can be cumbersome and error-prone for teams not already immersed in coding agent ecosystems.

Non-Zero Exit Codes

Exits with a non-zero code on the first run to detect missing translations, which might complicate CI/CD scripts and require additional handling, as noted in the agent workflow section.

Frequently Asked Questions

Related Projects

i18next

i18next: learn once - translate everywhere

Stars8,637

Forks694

Last commit2 days ago

polyglot

Give your JavaScript the ability to speak many languages.

Stars3,720

Forks205

Last commit11 months ago

Localize-Swift

Swift friendly localization and i18n with in-app language switching

Stars3,122

Forks329

Last commit3 years ago

BartyCrouch

Localization/I18n: Incrementally update/translate your Strings files from .swift, .h, .m(m), .storyboard or .xib files.

Stars1,404

Forks116

Last commit2 years ago

Community-curated · Updated weekly · 100% open source

Found a gem we're missing?

Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.

Submit a project Star on GitHub