Multilingual Data and Localization
Actualog lets teams maintain shared product information for several languages without creating a separate product for every translation. Names, descriptions and other supported text fields can have localized values, while the product's identity, relationships and structured technical values remain shared.
This article explains the platform model. For personal language selection and editor controls, use Languages. For the role of English in shared terminology, use Source Language.
Interface language and business content
Two kinds of text have different owners and update paths:
| Text | Examples | How it is maintained |
|---|---|---|
| Application interface | Buttons, validation messages and menu labels | Versioned English resources and managed satellite translations |
| Business content | Product descriptions, category names and translated dictionary labels | Localized field values maintained with the relevant records |
Changing the interface language does not translate a product description. Editing a French product name does not rename application buttons. This distinction also explains why a translated interface can display an English business value: the interface translation exists, while the requested content translation may be missing.
Your data-language selection determines the languages available in multilingual editors. It is a working preference, not a request to duplicate the underlying records or automatically generate all missing translations.
One record, several text values
Supported localized fields keep canonical English text and a stable term identifier. Translated values are associated with that identifier and a language code in the term store. The current implementation uses Azure Table Storage for those language terms; relational records retain the business identity and canonical fields.
This separates language coverage from the core relational structure. Adding another translation to a supported field does not require adding another product or another language column to every entity table.
When preparing a page, application services request the needed terms in batches and compose the localized result. English reads use the canonical English value. Other languages use the stored translation where one is available; the normal display fallback is English.
Fallback is field-sensitive. Some optional text deliberately remains empty when no translation is available. An empty description therefore does not always mean that storage or translation has failed. Conversely, an English label in a localized page is not evidence that a translation has been completed.
A product example
Consider one product whose reviewed English name is “LED power supply”, with a French name “Alimentation LED” and a numeric output-voltage value of 24 V.
| Viewing context | Name | Technical value |
|---|---|---|
| English | LED power supply | 24 V |
| French, with a stored name translation | Alimentation LED | 24 V |
| Another language, with no stored name translation | English fallback where the field uses it | 24 V |
These are language views of the same record. Translating the name does not create a different product, change the voltage or convert the unit. The example illustrates the data model; it does not describe a particular product already stored in Actualog.
Technical meaning stays structured
An Attribute definition determines whether a value is numeric, text, a controlled selection or another supported type. A category template supplies the applicable Attribute rules. See Attribute and Category Attributes Template.
For numeric information, distinguish the physical quantity, selected unit and stored value from the wording used to present them. Translating “length” does not convert millimetres into inches. Review unit compatibility and precision through the Attribute and template rules, rather than embedding a different measurement in a translated description.
Controlled values also have identities beyond their displayed names. A translated label should describe the same selected reference value. Integrations should preserve documented identifiers and codes instead of treating a localized label as an immutable key. Standards references, manufacturer part numbers and technical symbols require particular care: they often need preservation rather than linguistic rewriting.
Assisted translation and review
Translation actions use configured services where available. The result can accelerate drafting, but service availability and a successful response do not establish technical accuracy or approval. Use Auto-Translation Button for the editor workflow.
Review translated engineering terms, decimal notation, units, tolerances, standards and safety statements before relying on the text. Keep brand names and identifiers intact. If English source wording changes materially, review affected translations for meaning; do not assume an existing translation remains aligned merely because it is still present.
Human review is a publishing practice. This article does not imply that every translation field has an enforced approval workflow. Apply the permissions and governance controls of the record you are editing.
Search, delivery and operational checks
Search uses maintained projections that include language-specific text. A saved translation and a refreshed search index are separate states. The selected search languages, indexed fields and refresh progress can affect discovery; finding the record by identifier is a useful first check when a newly translated phrase is absent from results.
API and export clients should use each documented contract's language selection and field semantics. Do not assume that every endpoint returns every translation or that the browser's interface language controls an integration response.
For an IT review, verify a representative multilingual record end to end: save the English baseline and a translation, reload both language views, check a missing-language fallback, confirm structured values remain correct, and inspect the intended export or search result. This tests the delivered experience as well as the existence of translated text.