• Home
• Editions
• Demo
• Downloads
• Services
• Support
• Translations
• Pricing & Purchase

OpenConf Translations

OpenConf is now multilingual! To enable translations, visit the Chair's Settings: Configuration page, and modify the Localization section at the bottom of the page. If you can help create new translations or update existing ones, please see below. As of release 4.10, all author and reviewer pages are internationalized.

Languages available

Language	Code	Translated*	PO File
العربية — Arabic	ar		.po
中文（简体）— Chinese (Simplified)	zh-Hans		.po
English	en		.po
English (UK)	en-GB		.po
Français — French	fr		.po
日本語 — Japanese	ja		.po
Português (Brasil) — Portuguese (Brazil)	pt-BR		.po
српски srpski — Serbian (Cyrillic)	sr-RS		.po
Español — Spanish	es		.po
Türkçe — Turkish	tr		.po

* The author pages for these language are completely (or nearly) translated:
Chinese (96%), Portuguese (100%), Turkish (100%)

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 the language, operating system and version, and supported locale name to translate -at- openconf.com.

Updating an existing translation

1. Email us and let us know which language/locale translation you are interested in updating. This way if someone else is already working on an update, we can better coordinate the translation effort and prevent duplicate work.
2. Download and install poEDIT.
3. Download the latest PO file for your language above. Do not use the PO file in your installation as it may not contain the latest update.
4. Start up poEDIT and open the PO file.
5. 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 strings in place.
   Fuzzy (gold) strings will likely need to be replaced.
6. Test out the 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.
7. Email the revised .po file to translate -at- openconf.com, along with a signed copy of the copyright disclaimer if you have not yet submitted one.

Creating a translation for a new language

1. 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.
2. Download and install poEDIT.
3. 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.
4. Start up poEDIT and open the PO file.
5. Select poEDIT menu Catalog > Settings, change the Language and Country fields, then click OK.
6. 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 strings in place.
7. Email the revised .po file to translate -at- openconf.com, along with a signed copy of the copyright disclaimer if you have not yet submitted one.

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 event using OpenConf is dealing with papers.
• Use UTF-8 encoding, and be careful when copying/pasting from another program.
• Do not replace %s, %d, %#$s
• 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 Chair.
• When in doubt, 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.