Contents
Translations and RTL - Plugixa Chat
Plugixa Chat is translation ready. Every word the plugin itself supplies can be translated, including the words the widget and the contact form show to visitors. On a right-to-left site both the admin app and the widget follow the direction of the page.
Two kinds of text
It helps to separate the words you typed from the words the plugin supplies.
| Text | Where it comes from | How it gets into another language |
|---|---|---|
| Channel labels you typed, hover text, the greeting, pre-filled messages, the form’s title, intro, consent text, button text and thank-you message | You, in the builder | You type them in the language you want |
| Channel names such as “Phone call” and “Contact form”, used when you leave a label empty | The plugin | A translation file |
| The form’s field labels (Name, Email, Phone, Message), its default title, button and thank-you message, and its error messages | The plugin | A translation file |
| The widget’s labels for screen readers, such as “Open chat options” | The plugin | A translation file |
| The QR panels’ sentences and the Copy button | The plugin | A translation file |
| The default button text “Chat with us” and “Ask about this product” | The plugin | A translation file |
| Every label in the admin app | The plugin | A translation file |
A useful consequence: a field left empty uses the plugin’s default, and the default is translated. A field you filled in is shown exactly as you typed it, in every language.
Translating the plugin
| Detail | Value |
|---|---|
| Text domain | plugixa-chat |
| Template file | languages/plugixa-chat.pot, inside the plugin’s folder |
| Where translations are read from | wp-content/languages/plugins/, then the plugin’s own languages/ folder |
To translate it yourself:
- Open
languages/plugixa-chat.potin a translation editor such as Poedit, or use a translation plugin such as Loco Translate. - Translate the strings and save a
.poand.mofile named with your locale, for exampleplugixa-chat-fr_FR.mo. - Put the files in
wp-content/languages/plugins/. Files there survive plugin updates and take precedence over files in the plugin’s own folder.
The admin app’s labels come from the same .mo file as everything else. No
separate JavaScript translation files are needed for it.
The Chat button block’s labels in the block editor are the exception: WordPress loads those from a JSON translation file for the block’s script, in the usual WordPress way.
Which language is used
- The admin app follows the language of the person using it, as set in their WordPress profile.
- The widget follows the language of the page being viewed. The plugin’s own words are translated on each page view, so a multilingual plugin that changes the site’s language per page changes the widget’s words with it.
Multilingual sites
The plugin’s own words follow the page’s language by themselves. The words you typed do not, because they are stored once.
The way to have, say, a French greeting on French pages and an English one on English pages is a widget per language:
- Build the widget in one language.
- Duplicate it on the Widgets screen and retype the copy’s text in the other language.
- Give each widget a rule that keeps it to its own pages.
| Your site separates languages by | Rule to use |
|---|---|
A folder in the address, such as /fr/ |
Page address - starts with - /fr/ |
| The visitor’s browser language PRO | Language. See Country and language rules |
For the default-language widget on a site that uses folders, use Except on rules for the other languages’ folders.
Page address rules look at the path, not the domain. If your languages live on separate domains or subdomains with the same paths, a Page address rule cannot tell them apart.
Right-to-left
On a site whose language is written right to left, such as Arabic, Persian or Hebrew, WordPress marks the page as right-to-left and the plugin follows.
The widget
| Part | In a right-to-left page |
|---|---|
| Text, lists, the contact form | Aligned and ordered for right-to-left reading |
| Channel rows | The icon sits on the side the reader starts from |
| The greeting’s close button, the unread badge | Mirrored |
| The corner the launcher sits in | Not mirrored |
The Position setting, Left or Right, is a position on the screen and is kept as chosen. A site that put the launcher in the bottom-right corner keeps it there in every language. To have it on the left on right-to-left pages, choose Left for that widget.
The admin app
The admin app’s layout follows the direction of the WordPress admin, which WordPress sets from the user’s language.
Dates and times
Dates on the admin screens use the formats under Settings -> Formatting and the site’s timezone. Day names in the Pro business hours editor are written in the admin’s language. See Settings.
What to do next
- Target pages by address in Builder: When and where.
- Review the form’s default wording in Contact form.