Localize

An app's translations, harvested from its own Swift, shipped as a Granite agent package. A call names the languages; the package reads every localizable string out of the app's code, writes the source language, has the host's model translate what is new or changed into each language in checked batches, and adds the languages to the Xcode project.

It is one of the Rao Craft Agents: independent packages that, tagged in prompts along the life of a project, build an app of Loom's quality. Loom ships 28 languages; localize keeps an app's in step with its code, a call at a time.

How an app finds it

LocalizeAgent is a GraniteAgentPackage, and it carries a record in its binary:

@used @section("__DATA_CONST,__granite")
let localizeRecord: GraniteRoster.Record = { GraniteRoster.record(LocalizeAgent.self) }

In Craft, install it from the Agent Store or with craft agents add https://github.com/Rao-Craft-Agents/LocalizeAgent.git, then say $localize in a request:

$localize the recipe app into French, German, Japanese and Arabic

The model writes the call ({"languages": ["fr", "de", "ja", "ar"]}); the call shows on Craft's agent map as localize-1, and the tables and project file it names are built with the turn.

What a call takes and answers

The answer is a LocalizeResult: every file written (path, paths, absolute; a file that came out the same is not written), the app's languages, how many strings were found, added and translated, the languages that still wait, and a sentence for anything left out.

{"languages": ["fr", "de", "ja", "ar"]}
{"languages": ["loom"]}
{}
{"languages": ["es", "pt-BR"], "format": "catalog"}
{"languages": ["fr"], "refresh": true}
{"languages": ["it"], "helper": true}
{"languages": ["ko"], "scan": ["Components", "Shared/Views"]}

The strings

A literal is a key where SwiftUI or Foundation looks it up at run time: the first argument of Text, Label, Button, Toggle, Section, TextField, Picker, Menu, Link, ContentUnavailableView and the other views that take a LocalizedStringKey; .navigationTitle, .help, .alert, .confirmationDialog, .accessibilityLabel; String(localized:), LocalizedStringResource, LocalizedStringKey, NSLocalizedString, "KEY".localized(); a ternary of literals in those places; and a literal given to a property or parameter the app declares as a LocalizedStringKey, or returned by a computed one. An interpolation becomes the specifier the runtime asks for: an Int is %lld, an Int32 %d, a Double %lf, a specifier: its own, anything else %@; a % beside one is doubled. A key with several specifiers reads numbered in the source language (Cooked by %1$@ in %2$lld minutes), so a language can reorder them. The call's comment: is kept above its entry.

Not a key: Text(verbatim:), a literal built into a String, a string with no letters ("•", "\(name)"), another table's or a package's string, and a preview's sample text. .build, DerivedData, packages and tests are not read unless scan names them.

How the files are made

Without a model the source language is still written, and the answer names the languages that wait.

Testing

swift test                       # the record, the schema, the harvest (matched against the compiler's own), the tables, the checks, whole calls
LOCALIZE_BUILD=1 swift test      # a recipe app localized into four languages, built for macOS and the iOS Simulator, and run

MIT licensed.