Languages & RTL

Foodomaa ships with language files for 29 locales, including English, Arabic, Bengali, German, Spanish, French, Hindi, Indonesian, Portuguese, Turkish and Urdu. Translation is a starting point; a native review and an RTL layout test are still required.

What is included

• Language directories under resources/lang for the customer, vendor, rider and admin surfaces.
• Notification templates in several locales.
• Date, currency and number formatting through the application locale.
• The ability to add a locale and translate the strings.

Coverage varies by file. A locale may have notifications but incomplete checkout strings. Audit the actual screens before promising a fully translated product.

Translation workflow

1. Choose the launch locale and set it as the default for the storefront and apps.
2. Export the language files and translate in a spreadsheet or translation tool.
3. Keep placeholders such as :name, :order and HTML tags unchanged.
4. Review menu, checkout, payment, refund and support strings first.
5. Have a native speaker review the customer journey, not only isolated strings.
6. Test the complete order flow in the target language.

RTL checklist

• Set dir="rtl" on the HTML element for Arabic, Hebrew, Persian or Urdu.
• Mirror navigation, icons with direction, progress steps and carousels.
• Do not mirror numbers, phone numbers, prices or map controls.
• Check form labels, validation messages and error placement.
• Test tables, invoices and emails; many RTL bugs appear outside the storefront.
• Use a font with good Arabic glyph coverage and line height.
• Test long Arabic strings on a small phone; translation can be 20–30% longer.

Content that is not in the language files

Menu names, vendor descriptions, banners, legal pages, emails and support scripts are content, not interface strings. They need their own translation process. A storefront that is in Arabic but has English legal pages is not a localised product.