Translations
Join our Translator Hall of Fame – See below for how to create or update a translation
Languages
OpenConf's author, committee member, and public pages are available in multiple languages. The Admin specifies the languages under the Localization section of the Configuration page. If more than one language is enabled, a language menu () is displayed atop right of the OpenConf home page. Note that system emails will be in the selected language of the signed in user whose action resulted in the message being sent out.
| Language | Code | Translated | PO File ⓘ | Demo |
|---|---|---|---|---|
| Deutsch — German | de |   | .po | v7 • v8 |
| English | en | | .po | v7 • v8 |
| English (UK) | en-GB | | .po | v7 • v8 |
| Español — Spanish | es | | .po | v7 • v8 |
| Français — French | fr | | .po | v7 • v8 |
| Italiano — Italian | it | | .po | v7 • v8 |
| Magyar — Hungarian | hu | | .po | v7 • v8 |
| Nederlands — Dutch | nl | | .po | v7 • v8 |
| Português (Brasil) — Portuguese (Brazil) | pt-BR | | .po | v7 • v8 |
| Türkçe — Turkish | tr | | .po | v7 • v8 |
| босански — Bosnian | bs | | .po | v7 • v8 |
| 中文 （台灣） — Chinese (Traditional) | zh-Hant | | .po | v7 • v8 |
| 中文（简体） — Chinese (Simplified) | zh-Hans | | .po | v7 • v8 |
| 日本語 — Japanese | ja | | .po | v7 • v8 |
| The languages below are only available with version 7 | ||||
| العربية — Arabic | ar | | .po | v7 |
| Indonesian — bahasa Indonesia | id | | .po | v7 |
| ﻑﺍﺮﺴﯾ — Persian | fa | | .po | v7 |
| српски srpski — Serbian (Cyrillic) | sr_RS | | .po | v7 |
| ру́сский язы́к — Russian | ru | | .po | v7 |
Need a different language? See below on how to create your own translation,
or contact us if you are interested in sponsoring a new language.
Requirements
The use of OpenConf's multilingual interface requires that PHP gettext be enabled, and the system have the proper locale(s) configured. See the openconf/lib/locale/locale.inc file for locales specified for each language. If a particular locale for a language is missing on your system, email us the language, operating system type and version, and supported locale name.
Creating a translation for a new language
If you would like to sponsor a new translation by having our team coordinate the translation outsourcing effort, please email us the desired language(s) and we will let you know the sponsorship fee. In order to create and contribute your own translation, follows these steps:
- Email us and let us know which language/locale you are interested in translating to. This way if someone else is already working on a translation, we can better coordinate the effort and prevent duplicate work.
- Download and install poEDIT.
- Download the latest PO file for English (en) above. Do not use the PO file in your installation as it may not contain the latest update.
- Start up poEDIT and open the PO file.
- Select poEDIT menu Catalog > Settings, change the Language and Country fields, then click OK.
- Translate everything that you can, staying true to the OpenConf meaning, and save your work.
Please be sure to use UTF-8 encoding, and leave all %s, %d, %#$s, and [:zzz:] strings in place (unless otherwise indicated). - Email the revised .po file to translate -at- openconf.com, along with a signed copy of the copyright disclaimer.
Note that at present OpenConf 8 and later does not support right-to-left languages.
Updating an existing translation
If you are looking to simply add or replace a few string translations in your local installation, create a custom translation file for each desired language:
- Make a copy of the file openconf/lib/locale/extras-template.inc and call it extras.inc
- Open the file in a plain text or code editor
- Replace *** in the first code line:
$OC_translationExtrasAR['***'] = array(
with the language code in the above table for the desired language (e.g., es for Spanish, fr for French, pt-BR for Brazilian Portuguese) - Add string/translation pairs using the format shown, with one pair per line and each contained within single quotes:
'original English string' => 'translated string',
Note:
- For long English strings or containing special characters, if needed, an MD5 hash of the original English string may be used instead as of version 7.
- If the English string contains HTML, make sure to also include it in the translated string as they must match exactly including any spacing. Copying text from a formatted text box (e.g., Home Page Notice on Configuration page) will not allow a match for translation; use the browser to view source the page the string is displayed in and copy the HTML snippet for the string instead.
- If either the original or translated string includes a single-quote ( ' ), the quote must be prefixed by a backslash ( \' ); smart quotes are best avoided.
- Move the extras.inc file you created into the openconf/lib/locale/***/ directory
In order to make extensive corrections to an existing translation:
- Download and install poEDIT.
- Download the latest PO file for your language above.
- Start up poEDIT and open the PO file.
- Update desired stringsand save your work. Make sure to use UTF-8 encoding, and leave all %s, %d, %#$s, and [:zzz:] strings in place (unless otherwise indicated). Fuzzy (gold) strings will likely need to be replaced.
- Install the revised translation by copying the .mo file auto-generated by poEDIT to the openconf/lib/locale/[LOCALE]/LC_MESSAGES/ folder. Note that you may need to restart the HTTP server for the new translations to take effect.
Translation Tips
- Keep the meaning as close to the original as possible, even if your particular event uses something different. You can always generate a separate translation file for your own use. For example, "Make Submission" is preferable to "Submit Paper", as not every use of OpenConf deals with papers.
- Use UTF-8 encoding, and be careful when copying/pasting from another program.
- GetText imposes a string limit of 4096 character bytes
- Do not replace %s, %d, %#$s (unless otherwise indicated)
- Field names include both a long form (e.g., Submission Title) and short form (e.g., Title). The short form is used in confirmation messages and display to Admin.
- When in doubt about a meaning, right-click on the word in poEDIT and look up the reference in the code. If you are still unsure of a meaning, contact us.
- If you are testing a translation that you have made and the server is not displaying the newly translated strings, try restarting the HTTP server. PHP's gettext caches the translations.
- The .po/.mo file names include the OpenConf version number, and will thus change with each new OpenConf release. See the above comment as to why.
Translator Hall of Fame
The following individuals have translated or reviewed translations of OpenConf. We thank them for their assistance.
| Language | Translator |
|---|---|
| Arabic | Bencherif Mohamed Abdelkader, Algeria |
| Bosnian | Emir Čičkušić, Bosnia and Herzegovina |
| Chinese (Simplified) | Guohua Tang, China |
| Hungarian | Domokos József, Romania |
| Indonesian | Ferry Wahyu Wibowo, Indonesia |
| Japanese | Hiroyuki Miyazaki, Japan |
| Persian | Alireza Zamani, Iran |
| Portuguese (Brazilian) | Tadeu Pontes, Brazil Ronnie Fagundes de Brito, Brazil |
| Russian | Victor Fedoseev, Russia |
| Serbian (Cyrillic) | Darko Divnic, Republika Srpska |
| Spanish | Netzahualcoyotl Hernández Cruz, Mexico Jessica Cukierman, Argentina | Turkish | Deniz Akkoyun, Turkey Erdal Ustundag, Turkey Devrim Seral, Cyprus |