Translating ProcessMaker
From ProcessMaker
Wouldn't it be great to have ProcessMaker completely translated to your mother-language? The ProcessMaker team is always on the look-out for new translations and for people who are willing to update the existing ones.
Contents |
Adding a New Translation
If you want to add a new language to ProcessMaker, please go to ADMIN (formerly SETUP) > LANGUAGES, and select the English language from the list (or another language from which you want to translate). Then click its Export link to download the file processmaker.en.po. This should create a PO translation file which is up-to-date with your currently installed version of ProcessMaker.
Open it with a editor for PO translation files. ProcessMaker uses gettext portable object (.po) files, which is a standard format for translating software into different languages. The portable object format is not very complicated and can be edited with any standard plain text editor such Notepad++ for Windows or vim or gedit for Linux. Nonetheless, it is recommended to use a specialized PO editor to avoid errors in the translation. A good cross-platform editor for .po files is poEdit. KBabel is also highly recommended for users of Linux. The Translate Toolkit provides several helpful tools for checking translations.
PS: Please don't use the Launchpad Rosetta platform for ProcessMaker translations. It is not compatible.
Translating with PoEdit
Download PoEdit and install it. Then open the file processmaker.en.po with PoEdit.
First edit the header information for the PO file. Go to Catalog > Setup:
Change the Language from English to your language and change the Country from USA to your country. Also add your name and address so people can contact you with revisions and updates about the translation. Set the character set to UTF-8.
PoEdit displays a list of phrases to translate at top. Select a phrase to translate. In the top box is displayed the original English phrase to translate and in the bottom box is displayed the translation. In the translation window, translate the phrase from English to your language.
Press the Tab key to switch between the list of phrases and the translation box for each phrase. It is also a good idea to show the translator comments window to see if there are any translator comments left by a previous translator. Activate the option under View > Show translator comments. Also show the window for automatic comments from the programmers by activating the option under View > Show automatic translator comments.
When translating, ignore any text inside square brackets, when translating. For instance, a Spanish translator would translate "[JAVASCRIPT/CANCEL] Cancel" as "Cancelar".
Phrases highlighted in yellow are marked as "fuzzy", which means that the original phrase in the software has changed, so the phrase needs to be retranslated. If you are unsure how to translate a phrase, it is better to leave it blank, rather than use a wrong translation. Another option is to do a preliminary translation of a phrase, but indicate that the phrase needs to be reviewed in the future by clicking the "fuzzy" icon in the toolbar. This will indicate to the next translator to review the translation. A comment can also be left for the next translator by going to Edit > Edit Comment. Before marking a phrase as "fuzzy", make sure that you are using a version of ProcessMaker which doesn't contain this bug.
When done, save the file as processmaker.<LANG>.po, where <LANG> is the 2 letter 639-1 ISO language code.
Then login into ProcessMaker as the admin user (or any other user with PM_SETUP_ADVANCE in their role). Go to ADMIN (formerly SETUP) > LANGUAGES and click on "Import or Update" to upload the new translation to the ProcessMaker. At the next login, the language should be available for use.
Note: A bug in PoEdit 1.4.X causes it to transform one automatic comment line into two lines. Before importing the PO language file into ProcessMaker, open the PO file with a bare text editor (such as Notepad++, vim or gedit) and search for the translation of "rms/fields/date.xml?PME_MAS" (which can be found at roughly line 3322). Change its automatic comment from two lines to one.
Change the two lines:
#: msgid "Mask Sufixes: #: %Y=Year, %m=Month, %d=Day"
To the single line:
#: msgid "Mask Sufixes: %Y=Year, %m=Month, %d=Day"
Translating with a plain text editor
If using a plain text editor, change the PO header information in bold:
msgid "" msgstr "" "Project-Id-Version: PM 4.0.1\n" "POT-Creation-Date: \n" "PO-Revision-Date: 2009-10-05 09:18+0100 \n" "Last-Translator: Fernando Ontiveros<fernando@colosa.com>\n" "Language-Team: Colosa Developers Team <developers@colosa.com>\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer_Encoding: 8bit\n" "X-Poedit-Language: English\n" "X-Poedit-Country: United States\n" "X-Poedit-SourceCharset: utf-8\n" "Content-Transfer-Encoding: 8bit\n"
Then translate the msgstr strings in bold:
# TRANSLATION # LABEL/ID_END_OF_PROCESS #: LABEL/ID_END_OF_PROCESS msgid "End of process" msgstr "Fin de proceso" # TRANSLATION # LABEL/ID_TAREA_COLGANTE #: LABEL/ID_TAREA_COLGANTE msgid "Leaf task" msgstr "tarea de hoja"
Do NOT change the string for the msgid. Make sure that each msgstr is enclosed in double quotes. To use a double quotation mark within a string, precede it with a backslash \" .
Updating an Existing Translation
If you want to update an existing translation for ProcessMaker, first download the translation file, import the translation into ProcessMaker as explained in the Translations page to update the file with the latest phrases. Then go to ADMIN (formerly SETUP) > LANGUAGES and select the language and click Export. Then edit the translation file as described above.
If you would like to include your translation in ProcessMaker, please email the .po file as an attachment to amos@colosa.com. If you would like your name to be listed on the translation credits page, please let us know us know in the email.
Thank you for your help with translations!
