For multilingual vision device delivery, list interfaces, operating instructions, API documents, error messages and version records. Define terminology, parameter meanings, units and applicable conditions. Wording may vary across languages, while function scope, limitations and unverified status must remain consistent.

Manage parameter values separately from display formats

Record parameter identifiers, value types, ranges, defaults and units. When converting units, retain conversion rules and required numerical precision. A display format change must not change the actual setting. Check decimal separators, dates, time zones and coordinate definitions. Interface wording alone does not establish meaning.

Maintain error identifiers separately from readable messages

W3C internationalization guidance recommends language-independent error identifiers for APIs and protocols. Stable identifiers can link to localized explanations and handling instructions. When adding errors or changing their meaning, update interface definitions, message text and test records together.

Deliver evidence for the same scope in each language

Check body text, parameters, errors, operating steps and known limitations by function and language. Record actual language resources, software versions and check results. List unfinished languages or functions. Acceptance of one language does not establish acceptance of the whole delivery.

See W3C internationalization guidance.