Black Friday
Skip to documentation content

Multilingual Sites

Translate interface strings and hotel content separately

Translation files, multilingual Page/menu configuration and supported hotel-entity translations solve different problems. Installing a .mo file does not translate room descriptions or create another language's menu automatically.

Translation files, multilingual Page/menu configuration and supported hotel-entity translations solve different problems. Installing a .mo file does not translate room descriptions or create another language’s menu automatically.

Interface catalogs

Free uses text domain kimorapro-hotel-booking, Pro uses hotel-booking-pro, and Aurelia uses aurelia. Each package owns its strings and language assets. The reviewed repositories include French, German, Italian and Vietnamese assets; check exact locale filenames and current build results rather than assuming every regional locale or string is covered.

Keep translation-source edits separate from generated MO/JavaScript outputs and rebuild through the owning package’s workflow. Do not rename another package’s domain or load Pro translations as a substitute for Free strings.

The current review found Free’s POT source extraction stale, although its MO/JSON build check passed against the existing catalogs. Pro’s POT/build checks passed. This is not proof that every new Free source string is translated; source/catalog synchronization needs its owning follow-up before a completeness claim.

Hotel content

Use the supported translation controls for room/amenity fields and available Pro services/policies. The registered entity contract determines editable fields and fallback; it is not permission to translate IDs, machine dates, quantities, currencies or financial amounts.

Sparse translations can fall back to canonical content. Verify the public room/detail/booking surface in each language instead of assuming every related entity has a complete translation. A provider’s translated Page relationship is separate from these domain records.

New bookings capture the applicable language and policy/financial snapshots through the owner workflow. Later editing a current policy translation does not rewrite saved acknowledgements, cancellation terms or issued documents. A translated checkbox is not consent evidence for an imported/OTA record.

Inspect a synthetic booking and its new email/document output in the selected language. Use a mail sink, and keep delivery testing separate from content generation. Do not repair a translation problem by editing old financial/policy rows.

For Aurelia labels/action URLs, use its supported Customizer and provider controls; Core does not translate all theme marketing copy automatically. See menus and booking locale history.

Was this article helpful?

Your feedback helps us improve the documentation.