> ## Documentation Index
> Fetch the complete documentation index at: https://docs.assetinfinity.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Localization

> Translating the product's own wording, renaming what it calls things, and finding what nobody has translated yet.

Where the product's own text is translated into another language, and where an administrator
renames what the product calls things — a work order into a Job, an asset into Equipment — for
everybody who reads this organisation's copy of it.

## Languages

Every string in the product is written in English and resolved through a catalogue at the moment
it renders, so a second language is a translation of that catalogue rather than a second build.

| Language | State |
| - | - |
| **English** | The source language. Complete by construction — it is what every string is written in. |
| **French** | Fully translated. |
| **Arabic** | Fully translated, and right-to-left: the whole layout mirrors, not just the text. |

Other language codes can appear on the **Languages** tab at 0% complete. Those are reference rows
with no translation behind them yet, and read entirely in English until one is written.

<Note>
  A language's completeness is measured against the strings the product actually ships this
  release. A language sitting at 100% today can drop below it the moment a new screen ships with
  wording nobody has translated — that is what the percentage is for.
</Note>

## What things are called

The tab that leads, because renaming an object is the change most administrators come here to
make, and it is an afternoon's work rather than a project.

Type your own singular and plural for a term — "work order" and "work orders" — and every screen
that names that object follows: navigation, page titles, buttons, and the sentences that explain
them. **Preview** shows the before-and-after for every string the rename reaches before you save
it, because a substitution over two hundred sentences is not something to agree to from two text
boxes and an act of faith.

<Tip>
  Type a term in lower case and the product capitalises it wherever its own wording does. Type a
  capital anywhere but the first letter — *eTicket*, *WO* — and it is used exactly as typed.
</Tip>

A rename applies to the language it is made in. Renaming the English does not rename a screen a
translator has already done in French or Arabic — each language keeps its own word for the object,
and a rename made on one does not reach the others.

<Warning>
  A rename rewrites the product's own wording, never yours. If a sentence reads awkwardly after a
  rename, correct it on **Product strings** below — the correction stays even if the rename
  changes again later.
</Warning>

## Product strings

Every string in the catalogue, in whichever language you are editing, with a box to override it
for this organisation. Filter by module, search keys and wording, or show only what is still
untranslated.

A **right-to-left preview** toggle flips this panel only — not the navigation you came in
through — so you can see how a right-to-left reader experiences the product without having to sign
in as one.

<Note>
  Saving here changes the wording for your organisation only. It never touches the product's own
  catalogue, and it never affects another tenant.
</Note>

## Your fields

The custom fields you have added to the product's own forms — a label, a description, help text,
the grey placeholder text in an empty box, and a dropdown's own choices — translated one string at
a time, in whichever language you are working in. See [form studio](/config/form-studio) for
where those fields are built.

## Your lists

The rows you have configured yourself — your own work order types, priorities, and inspection
prompts — listed by which register they belong to and how many rows are translated.

<Note>
  This tab is a list rather than an editor. Translating your own configured rows is not available
  from this screen yet; it shows what exists so you know what is still English-only.
</Note>

## Who can use this

Everything on this screen sits behind the same configuration permission as the rest of
**Administration** — the two administrator roles and Maintenance Manager, by default. Without it,
the screen refuses outright rather than showing a read-only view. See [roles](/setup/roles).