Site settings
Multilingual sites
Kufi works with Polylang, WPML, TranslatePress and Weglot. Polylang and WPML keep a separate page per language; TranslatePress and Weglot translate one page as it's shown. Right-to-left languages such as Arabic are supported.
Without a multilingual plugin, your site is in one language, set under Settings → General → Site Language. Right-to-left languages such as Arabic or Hebrew work out of the box.
Which plugin to choose
| Polylang, WPML | TranslatePress, Weglot | |
|---|---|---|
| How it translates | A separate page per language | Translates the text of one page as it's shown |
| Layout per language | Each language has its own layout, so it can differ | One layout for all languages |
| Where you translate | In the builder, on the translated page (WPML can also use its Translation Editor) | In the plugin's own visual translation editor |
| Components and popups | One per language | One, with translated text |
Choose Polylang or WPML if languages need different images, sections or lengths. Choose TranslatePress or Weglot to keep one design and translate only the words.
Polylang and WPML
- Build the page in your main language and publish it.
- Create the translation with the plugin (the + icon next to the page).
- Open the translation with Edit with Kufi. In Settings → Translations, use Copy layout from to start from the original, then translate the texts in place.
With WPML's Translation Editor, Kufi sends every text of the page to WPML as separate strings. When the translator saves, Kufi rebuilds the translated page with the same layout and publishes it.
Header and footer texts: Polylang under Languages → Translations, WPML under String Translation.
Keep translations in sync
When you publish changes to a page that has translations, Kufi offers to carry them over to the other languages:
- Added, moved and removed elements, styles, images and other settings follow on each translation.
- Translated texts and links stay as they are. Elements that only a translation has keep their place.
- Texts that are new or changed in the original are highlighted on each translation in the builder, with the new original text next to them, so translators can find what to update.
- A translation that is a draft, or has unpublished changes in the builder, gets the update as a draft, so what visitors see doesn't change until you publish it.
This works on every site, free or Pro. With a Pro key, Translate automatically in the same dialog also translates the new and changed texts, and Translate page in the builder translates a whole page. See Automatic translation.
TranslatePress and Weglot
Build the page once. In the builder's Settings tab, Translate this page opens TranslatePress's editor; with Weglot, use the link to the Weglot dashboard. The builder itself always shows your main language.
The language menu
Add a Language menu item in the header builder or the footer builder. With Polylang and WPML it uses Kufi's menu; with TranslatePress and Weglot it shows the plugin's own switcher.
Right-to-left languages
Pages in Arabic, Hebrew, Persian and Urdu are mirrored automatically: text, columns, menus, sliders and spacing follow the reading direction. Arabic text uses Readex Pro, which is built for Arabic.
Good to know
- Polylang has been tested with Kufi in real use. WPML, TranslatePress and Weglot follow their documented interfaces; if something doesn't translate as expected, tell us.
- With Weglot, Kufi allows Weglot's own servers in the Content Security Policy automatically.
More in Site settings
Still need help?
Tell us what you are trying to do and what you see. We read every message.