Start cross-language interface documents with field definitions: names, types, units, ranges and meanings of null and missing values. Distinguish protocol identifiers from reader explanations. Unless the interface definition allows it, do not change field identifiers, enumeration values or error codes when translating natural language.

Keep versions and mappings for changes

When parameter meaning, defaults, error handling or structure changes, record the interface version and migration rules. Link localized documents to the same version and mark sections not yet updated. Save earlier definitions, revisions and examples to prevent mixing old and new instructions.

Check examples against the actual interface

Parse requests and responses in the agreed environment. Check fields, values and error branches. Use stable identifiers to link localized error explanations. Check missing parameters, invalid values and unsupported versions. Report translated examples as verified only after performing the corresponding checks.

Check language and text direction together

W3C internationalization guidance discusses language and text direction information for natural language messages. Distinguish readable explanations from program identifiers. Check bidirectional text, code snippets and number presentation. Retain rendering and parsing results. Readable layout does not replace protocol function verification.

See W3C internationalization guidance.