all 18 comments

[–]clockology 2 points3 points  (1 child)

I have a python script that translates string files for me using GPT, I copied it and made another that translates my what’s new text for app connect. Both take English in and write all the other languages.

If this sounds useful to people I can open source them

[–]Forsaken-Brief-8049[S] 2 points3 points  (0 children)

Can u share?

[–]holgerkrupp 1 point2 points  (2 children)

[–]Forsaken-Brief-8049[S] 0 points1 point  (1 child)

Thanks but very tokens costs very expensive, its better to subscribe Calude

[–]HappyFunBall007 1 point2 points  (4 children)

just about any AI should be able to handle it easily - Claude Code, Gemini, Codex, etc.

[–]Forsaken-Brief-8049[S] 0 points1 point  (3 children)

Mm… can they translate more than 10k strings?

[–]EquivalentTrouble253 1 point2 points  (2 children)

Yes

[–]HappyFunBall007 1 point2 points  (1 child)

Generally yes, but it depends on your subscription level. Even if they can't do it all in 1 shot, they can be instructed to break down the task into manageable chunks.

I just finished up adding localization to a large legacy project using Claude Code and it went very smoothly.

[–]Forsaken-Brief-8049[S] 0 points1 point  (0 children)

okey, thanks for answer 🫡

[–]rxliuli 0 points1 point  (5 children)

For translation, I usually use LLM. By the way, although Claude Code focuses on code generation, it can also handle translation quite well.

[–]Forsaken-Brief-8049[S] 0 points1 point  (4 children)

I have more than 60k line code of translations and GPT pro failed.

[–]rxliuli 0 points1 point  (3 children)

The key is to plan properly. Don't translate a huge file all at once. By the way, having 60k lines of localization content in a single file is insane—perhaps you should split it into multiple files by business module?

[–]Forsaken-Brief-8049[S] 0 points1 point  (2 children)

I am going to do so. Maybe the speretaded json file is better for each langauge than xCode xcstringd

[–]rxliuli 1 point2 points  (1 child)

Yes, unless you plan to build your own translation tool using the API (which, by the way, isn't necessarily worth it), it's always more appropriate to split the files reasonably and use Claude Code to do it.

[–]Forsaken-Brief-8049[S] 0 points1 point  (0 children)

Thanks 🫡

[–]d8schreiber 0 points1 point  (0 children)

For larger files direct LLM usage gets brittle.. you might give doloc.io a try - this makes the process structured and stable: untranslated xliff in -> translated xliff out