Translating Quform

This documentation page is for Quform version 1 and may not be applicable for Quform 2 click here to visit the documentation for Quform 2.

Do you speak English and another language? Help us translate Quform

The Quform plugin includes a translation file /languages/iphorm-form-builder.pot. You can use this file along with translating software such as Poedit to translate the plugin. Please follow the instructions below to translate the plugin.

What you will need

  • Translation software to read .pot files and save translations as .mo files, we recommend Poedit
  • The Quform plugin and translation file which you can find at /languages/iphorm-form-builder.pot inside the plugin files
  • Your WordPress Locale code which you can find at https://wpcentral.io/internationalization/. In the table row for your language, you’ll find the locale code in the WordPress Locale column. For example:
    • For Polish the locale code is pl_PL
    • For Spanish the locale code is es_ES
    • For German the locale code is de_DE

Step 1

Download and install Poedit or a similar translation tool. Click here to go to the Poedit download page. Once you’ve installed Poedit, run the program. If this is your first time running Poedit, you’ll be prompted to enter your name and email address. This information is added to the top of the translated files as the last translator. You can leave these blank if you’d rather not enter them. Press OK.

personal

Step 2

On the Poedit menu, go to File →New catalog from .POT file and open the file iphorm-form-builder/languages/iphorm-form-builder.pot

new

Step 3a

A Settings dialog box will appear, fill out the information.

  • Project name and version – this should be automatically filled out
  • Team – set this to the name of your translation team or leave it blank
  • Team’s email address – set this to the email address of your translation team or leave it blank
  • Language – select the language you intend to translate to
  • Country – select the country of the above language
  • Charset – select the character set of the translation or leave it at utf-8
  • Source code charset – set it to utf-8
  • Plural formsIMPORTANT set this to the plural form setting for your language, you can find your plural form setting on this page

project

Step 3b

Go to the Paths tab and next to Base path enter ../ as shown below. Click OK.

path

Step 4

You’ll now be prompted to save the file as a .po file. You will need to change the filename to be iphorm-[LOCALE_CODE].po, replace [LOCALE_CODE] with your locale code that you obtained in the What you will need step above. Here are some examples:

  • For Polish, save the file as iphorm-pl_PL.po
  • For Spanish, save the file as iphorm-es_ES.po
  • For German, save the file as iphorm-de_DE.po

Step 5

When the file loads, you should see the list of text strings needing translated. If you look at the bottom, you should see 2 boxes, one containing the text needing translated and an empty box below it. In the empty box, enter your translation.

You can use the shortcut key Ctrl + Down Arrow to jump to the next translation. If the translation is the same in both languages, you can right-click the string and select Copy original to translation field.

Continue this process until the translation is complete.

Unusual characters combinations (formatting placeholders)

If you have never done a translation before, you may notice some odd looking character combinations, such as %s \n \t %1$s, these are formatting placeholders and they should remain inside the translated string, in exactly the same position if possible. Also double quotes will have a backslash before them \" and they should remain this way in your translation.

Finding more information or context of a string

If you need to find out the context of a string so that you can accurately translate it, you can right-click it and under References, click one of the filenames, this will open the file and show where the string appears in the code. You may be able to figure it out from there.

Step 6

Save the file, Poedit should create another file ending in .mo in the same place as your .po file. So you should have two files that should be in the iphorm-form-builder/languages/ folder:

  • iphorm-[LOCALE_CODE].po
  • iphorm-[LOCALE_CODE].mo

Step 7

If you haven’t done so already, you should set up WordPress to use your locale. Open the file wp-config.php, found in the WordPress root folder. Find the line that looks like this:

1
define('WPLANG', '');
define('WPLANG', '');

Inside the empty single quotes, enter your WordPress locale, for example:

1
define('WPLANG', 'pl_PL');
define('WPLANG', 'pl_PL');

Once this step has been done, the plugin should be translated inside WordPress, congratulations!

Share your translation?

Quform invites you to share your translations with others. Please consider emailing your .po and .mo files to info@themecatcher.net.

Be inspired. © 2024 ThemeCatcher Ltd. 20-22 Wenlock Road, London, England, N1 7GU | Company No. 08120384 | Built with React | Privacy Policy