Reference
Translation contexts
A glossary term does not have one translation. The same English word behaves differently in a sentence, in a heading, on a filter chip and on a button — so ETHGlossary records each of those separately. These are the slots translators fill in and reviewers vote on.
Every example below is the same term — externally owned account (EOA) — in English, in Spanish, and in Russian. All three are real translations: Russian renders it внешний аккаунт, where внешний is the Russian word for “external” and аккаунт is “account” borrowed and spelled phonetically.
Because Cyrillic is not Latin script, the entry also records a romanization — vneshniy akkaunt (EOA) — which spells the Russian in Latin letters as a pronunciation aid. That is a separate field from the slots below, and it is not the English transliterated.
There is no slot for code. Code is not translated at all — a term inside backticks or a fenced block is left exactly as written, and comments are the exception, translated as ordinary prose. Where a term has to stay in Latin script even in running text, that is recorded once on the term itself, not per language.
Prose
prose
Running text -- sentences, paragraphs, documentation.
The default form, used inside a sentence. It follows the target language's normal rules for an ordinary noun: lowercase unless the language capitalizes common nouns, inflected as the grammar requires. If you only read one slot, read this one -- most other forms are derived from it.
enexternally owned accountescuenta de propiedad externaruвнешнего аккаунтаHeading
heading
Section titles and page headings.
The same term as it appears in a title. Many languages capitalize the first word of a heading where they would not capitalize it mid-sentence, and some drop articles that prose would keep. This slot exists so a heading does not inherit sentence-case from prose and read as a typo.
enExternally Owned Account (EOA)esCuenta de Propiedad Externa (EOA)ruВнешний аккаунт (EOA)Tag
tag
Category chips, filter pills, metadata labels.
The compact form used where space is tight and the word stands alone with no surrounding grammar -- a filter chip, a topic tag, a table column header. Often identical to prose, but a long term may collapse to its acronym here, as this one does in all three languages.
enEOAesEOAruEOAUI
ui
Buttons, menu items, and other interface controls.
The term as it appears in an interactive control, where space is short and the label has to stay scannable. It often diverges from prose: here every language drops to a shorter form than the full phrase, and Russian sheds the acronym entirely. Render what the control does in your language rather than translating the phrase word for word.
enExternal account (EOA)esCuenta externa (EOA)ruВнешний аккаунтPlurals
plurals
CLDR plural forms, where the language marks them.
Plural forms follow the Unicode CLDR categories -- one, two, few, many, other -- and languages use different numbers of them. Spanish marks two here where Russian marks five, which is why this cannot be a single field. Several languages do not mark plurals grammatically at all, so the slot does not exist for them and no feedback is collected on it.
enexternally owned accountses2 forms: cuenta de propiedad externa, cuentas de propiedad externaru5 forms: внешний аккаунт (EOA), внешних аккаунта (EOA), внешних аккаунтов (EOA)
Why the slot count varies
Five contexts — prose, heading, tag, UI and code — are filled in for every term in every language. Plurals are the exception. 6 of the 24 supported languages do not mark plurals grammatically at all: Indonesian, Japanese, Korean, Vietnamese, Chinese (Simplified), Chinese (Traditional). For those, the plural slot does not exist and no feedback is collected on it.
Among the languages that do mark plurals, coverage still varies term by term. “Reviewed every context” therefore means every context that is actually populated for that specific term in that specific language — never a fixed count.