Languages

Quickmunch is translation-ready, with right-to-left built in. What ships, and how translating works in WordPress.

Settings → General → Site Language

What ships

Part	What it is
English interface	Every label, button and message in the theme and both plugins.
Eight ready translations	Arabic, Bengali, Dutch, French, Hindi, Russian, Spanish and Urdu, for the theme and both plugins, as `.po` and `.mo` files in each `languages` folder. Arabic is complete; a string added after another translation was made reads in English until that `.po` is updated.
Three translation templates	`quickmunch.pot` in the theme, `sigma-core.pot` and `sigma-restaurant.pot` in the plugins — every string, ready to translate.
Right-to-left stylesheets	Loaded automatically whenever the site language reads right to left.
An Arabic typeface	Noto Sans Arabic, bundled — nothing is fetched from a font service. See Credits & licences.

Choosing the site's language

Pick it under Settings → General → Site Language. WordPress then downloads its own translation for that language, and WooCommerce's with it, automatically. Quickmunch's own strings need a translation file of their own — the next section.

Offer only what you can support. Switching the language translates the product, but your own content — menus, page wording, restaurant descriptions — stays in whatever it was written in. A half-translated site reads worse than a single-language one.

Offering more than one language

Theme Options → General → Languages lists every language whose translation files are in the theme's languages folder — the eight shipped ones appear by themselves. Tick the ones you offer under Enabled languages and pick the Default language a first-time visitor gets; English is always on.

The enabled languages are offered in three places: the switcher on the storefront header (turned off under Theme Options → Header), the same switcher on the top bar of the restaurant dashboard, and a Language field on every account's Account details, which keeps the choice on any device the person signs in from. A visitor's pick is remembered for the browser; a signed-in account's pick wins over it.

Translating Quickmunch

Use a translation plugin such as Loco Translate from the WordPress plugin directory, or a desktop editor such as Poedit. Either starts from the .pot templates and produces a .po file you edit and a .mo file WordPress reads.

Template	Covers	Save the translation as
`quickmunch.pot`	The storefront, header, footer and pages.	`wp-content/languages/themes/quickmunch-{locale}.mo`
`sigma-core.pot`	The page-builder sections and widgets.	`wp-content/languages/plugins/sigma-core-{locale}.mo`
`sigma-restaurant.pot`	Every dashboard, the POS, kiosks, TV screens and emails.	`wp-content/languages/plugins/sigma-restaurant-{locale}.mo`

{locale} is the language's WordPress code — es_ES, fr_FR, ar and so on. The file name has to match exactly, or WordPress never finds it.

Placeholders must survive. Anything like %s, %d or %1$s is replaced at runtime and has to remain in the translation, spelled exactly.
Keep your files up to date. A new release can add strings. Re-sync your translation against the new .pot and the new ones appear, untranslated, to fill in.

Keep translations out of the theme's own folder. Anything saved inside quickmunch/languages or a plugin's languages folder is replaced when you update. The wp-content/languages locations above are never touched — see Updating to a new version.

Right-to-left is a real layout, not a mirror

With a right-to-left site language, WordPress loads the theme's right-to-left stylesheets and the whole interface turns: sidebars, tables, forms and printed menus. It is a separate stylesheet rather than a transformation, which is why it looks correct rather than reversed.

What is translated and what is not

Translated	Not translated
Every label, button and message in Quickmunch, once you add its translation.	Menu dishes and descriptions.
WordPress and WooCommerce's own screens and emails, automatically.	Restaurant names and descriptions.
Quickmunch's built-in email wording, through the same files.	Your pages and blog posts.

A site in several languages at once — with a language switcher and each page written per language — needs a multilingual plugin. Every string in Quickmunch is translation-ready, so such a plugin can translate them alongside your content.

When it doesn't work

Some text stays in English

Either it is your own content, which the product does not translate, or that string has no translation yet. If none of Quickmunch is translated, the .mo file is in the wrong place or named wrongly — check it against the table above.

The layout does not turn right to left

The site language is not a right-to-left one. Check Settings → General → Site Language.

A translation disappeared after an update

It was saved inside the theme's or a plugin's own folder. Save it again in wp-content/languages, where updates cannot reach it.

A placeholder prints literally

A translated string lost or changed it. Compare that string against the .pot.

Related Pages · Branding · Header, Navigation and Footer · Updating to a new version