Name Translations

Page: [Admin] -> Configure -> Name Translations

AoT ships with the interface itself translated into more than a dozen languages, but the names on your farm — device names, zone names, crop names, dashboard titles, and so on — are things you typed in yourself. Nothing in the software can know in advance what to call them in every language. Name Translations is the settings page where AoT keeps (and lets you correct) the translations it has generated for those names, so that a farm built in Korean can still be read comfortably by someone who set their account to Japanese, or English, or any other supported language.

The names you typed are never changed. What this page manages is a separate translation shown on screen for each one, per language. The stored name stays exactly as you wrote it.

Not the interface language setting~

It is easy to confuse this with Language under General Settings, so it is worth being explicit about the difference.

The two systems never mix. A name you gave a device is not run through the interface's translation catalog, and interface text is never treated as a name to translate.

What this translates~

The dictionary this page manages covers names from across the system:

A few things are deliberately left out and will never appear here:

• Text that identifies a person or credential — user names, API key labels — is never collected.
• Text that the system uses as an identifier rather than a label — a management program's resource role (for example irrigation), user role names, device serial/EUI-style strings — is skipped, because translating it would break the lookup that depends on it matching exactly.
• Long-form text — a management program's stage guidance and notes, note bodies, notice content — is not covered yet. Only short, label-like names are in scope.
• A name that turns out to be too short, made only of numbers/symbols, or that happens to collide with a word already used in the interface's own translation catalog (so that translating it would look like the interface itself changed) is recorded with a status of Excluded rather than translated.

Turning it on~

Name translation has three independent switches, each controlling a different scope:

Turning translation off at any of these levels never changes a stored name. It only stops the translated text from being displayed.

Without an AI engine~

Producing a new translation needs an AI engine (configured under Settings > General Settings, AI Service). If none is configured, this page still works: it can collect the names currently in use, and you can type in your own translation for each one by hand — what you enter is shown on screen exactly the same as an AI-produced one would be. The button at the top of the page reads "Collect names" in this case, instead of "Translate now".

The Name Translations page~

The page lists one row per collected name, for the language selected at the top. Two dropdowns filter the list:

• Language — which language's translations to show. Only languages that already have at least one row appear, plus the language your account currently uses.
• Status — All, Translated, Not translated yet, Excluded, or Failed (see Status values below).

Each row shows the original name, its translation for the selected language, which category it belongs to (see the table above), and its status. The count in the top-right corner (done / total) is a quick read on how much of the current language is filled in.

The main button does one of two things depending on whether an AI engine is available:

• Translate now — scans the database for any name not yet in the dictionary, adds it to the queue, and immediately runs one batch of translation through the AI engine for the selected language. This is the same work a background job also does automatically every 15 minutes; the button exists so you do not have to wait for it.
• Collect names — the same scan and queue step, without the AI batch (shown when no AI engine is configured).

Retranslate all clears every translation for the selected language and marks it for translation again — except rows you have edited by hand, which are left untouched. A confirmation is required before this runs, since it discards existing translations for that language.

Each row also has its own Retranslate button, which resets just that one name and immediately re-runs translation for it. It is hidden for Excluded rows, but stays available for rows you have edited by hand — retranslating a locked row is exactly how you would discard your own correction and let the AI translate it again.

Editing a translation~

The Translation column is an editable field for every row that is not Excluded. Type a correction and move focus away from the field (or press Tab/Enter) to save it.

Saving a value here does two things: it stores your text as the translation shown for that name, and it locks the row — its status becomes Edited, and neither the periodic background job nor "Translate now" nor "Retranslate all" will overwrite it again. Clearing the field back to empty unlocks the row and returns it to Not translated yet.

This is the only way to fix a translation you disagree with. The original name itself is never editable from this page — the box next to it, under Translation, is a display-language override, not the record of what the name actually is.

Status values~

Where translated names show up~

Once a name has a translation for the language you are viewing AoT in, it appears in place of the original wherever that name is shown on screen — dashboard widgets, the map, device lists, and so on. The stored data is never changed; the substitution happens only in what is displayed to you. If you type a name into a form field — renaming a device, for example — you are always shown and always editing the original text, never a translation, so there is no risk of accidentally saving a translated name over the real one.