mirror of
https://github.com/hrydgard/ppsspp.git
synced 2026-10-15 15:30:29 +02:00
Henrik RydgårdandClaude Opus 5
c9ff8f55fe
Plenty of strings are legitimately identical in the target language - "Vsync", "Status", "Ad Hoc multiplayer" - but the only test we had for "is this translated" is "does it differ from English", so those got sent to the AI again on every single run of finish-language-with-ai, costing tokens and giving it another chance to translate something that shouldn't be. They now get a "# same as English" comment and are skipped. finish-language-with-ai writes it when the AI hands the English string back unchanged (which the validation added earlier was throwing away as an error), and import-single writes it when a language's line matches the en_US one. Deleting the comment puts the key back in play. Also stop comparing values with their comments still attached while working out what's untranslated, which was leaking "# AI translated" into the context block of the prompt. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0164UKoXpz9r155TRfQsoc3H
62 lines
1.9 KiB
Markdown
62 lines
1.9 KiB
Markdown
# Language ini file processor tool
|
|
|
|
To install Rust and cargo, [go here](https://www.rust-lang.org/learn/get-started).
|
|
|
|
To run, with rust installed, change to this Tools/langtool directory, then:
|
|
|
|
```bash
|
|
cargo run
|
|
```
|
|
|
|
(Or just move the binary out of target/ and run it directly).
|
|
|
|
To see command line usage, type:
|
|
|
|
```bash
|
|
cargo run -- --help
|
|
```
|
|
|
|
## Validating
|
|
|
|
```bash
|
|
cargo run -- validate
|
|
```
|
|
|
|
Checks every translated string in every language file against the English one it came from:
|
|
placeholders (`%1`, `%d`, ...) must survive translation, no line breaks or stray quotes, nothing
|
|
empty. Exits with a non-zero code if it finds anything, so it can be used as a check in a script.
|
|
|
|
The same checks run on anything the AI produces, before it gets written to a file.
|
|
|
|
## AI translation
|
|
|
|
Some commands (`add-new-key-ai`, `add-new-key-value-ai`, `finish-language-with-ai`) use an LLM to
|
|
generate translations. Two providers are supported, pick one by setting its API key in the
|
|
environment:
|
|
|
|
* Claude (Anthropic): `ANTHROPIC_API_KEY`
|
|
* OpenAI: `OPENAI_API_KEY`
|
|
|
|
If both are set, Claude is used unless you say otherwise with `--provider openai`. To pick a
|
|
specific model, use `--model`, for example:
|
|
|
|
```bash
|
|
cargo run -- --model claude-sonnet-5 finish-language-with-ai sv_SE
|
|
cargo run -- --model gpt-4o finish-language-with-ai sv_SE
|
|
```
|
|
|
|
The provider is inferred from the model name, so `--provider` is only needed to disambiguate.
|
|
|
|
Strings that are deliberately the same as the English one (terms like "Vsync") are marked with a
|
|
`# same as English` comment. `finish-language-with-ai` skips those instead of paying to have them
|
|
"translated" again on every run, and writes the comment itself when the AI hands the English string
|
|
back unchanged. Delete the comment if you disagree with it and it'll be picked up again next time.
|
|
|
|
To autoformat the code, use:
|
|
|
|
```bash
|
|
cargo fmt
|
|
```
|
|
|
|
or set up your IDE to do that (it's already pre-set-up for VS Code, if you open the langtool folder directly).
|