Localization Guide: Language Support & Setup

Localization in Dyson Sphere Program controls how in-game text, item names, building names, and historical labels appear across language settings. Proper localization ensures players see consistent, readable names and preserves historical naming where appropriate.

What localization covers

• UI text: menus, tooltips, descriptions, and system messages.
• Entity names: items, buildings, ships, and modules as presented in the interface.
• Historical/legacy names: previous or alternate names shown in history notes or legacy references.

Consistency of proper nouns

Proper nouns (item/building names, model names, and version labels) are preserved byte-for-byte as they appear in the localization source. This means:

• The current canonical English names are used exactly as written (for example, "Storage MK.I", "Depot MK.II" where those are the current strings).
• Historical names that reference older nomenclature are retained verbatim in their localized description text.

Historical naming treatment

Some objects include a History note that records previous names. These History notes must reproduce the exact former name string used in the game. Examples:

• Storage MK.I history states it was formerly known as the "Storage MK.N" where N was in Roman numerals.
• Depot MK.II history likewise records that it was formerly known as the "Storage MK.N" where N was in Roman numerals.

When translating or editing history descriptions, do not alter the quoted former-name string; translate only the surrounding explanatory sentence if necessary.

Editing and translating guidelines

• Keep technical and model-like names unchanged unless there is an established localized equivalent. Model suffixes such as "MK.I", "MK.II", "MK.N" must be copied exactly.
• When a History entry quotes a former name, preserve the original quoted format (including quotation marks and Roman numerals) to avoid loss of historical accuracy.
• Translate descriptive text, verbs, and grammar around proper nouns, but do not transliterate or modify item identifiers and model numbers.
• Maintain consistent capitalization and punctuation for names across all localized strings.

Presentation and UX considerations

• Short names should be concise for UI space; if a long historical note is necessary, keep the historical string intact but consider truncation for small tooltips and provide the full text in detailed info panels.
• Avoid inserting language-specific characters into proper nouns (e.g., don't replace "MK.I" with a localized abbreviation).
• Ensure that tooltip widths and text-wrapping handle quoted historical names without breaking readability.

QA checklist for localization reviewers

• Verify that all item and building names match the canonical strings exactly.
• Confirm History notes quote former names verbatim.
• Check that translations do not alter Roman numerals, model suffixes, or other identifiers.
• Validate tooltip layout with long quoted strings to avoid overflow or clipping.

By following these rules, localization preserves both current and historical naming conventions, ensuring clarity and fidelity for players across languages.