| |
|
|
|
 |
|
|
 |
|
| |
Translation and Internationalization
Locale support for the Webconfig utility is available.
If you are interested in translating ClarkConnect to your language,
please contact contribs@clarkconnect.com.
We use an online tool for most of the translation.
However, you should become familiar with the
standards and conventions used by the ClarkConnect software engine before starting with the online tool.
Directory structure
The locale files are located in three different directories.
Each of these directories holds different types of information.
-
/var/webconfig/api/lang
Translation for the software API
-
/var/webconfig/htdocs/admin/lang
Translation for the web pages
-
/var/webconfig/htdocs/menus
Translation for the web page menus
Filename standard
Following standard locale conventions,
locale files are appended with the two letter language code followed by an underscore followed by the
internationally recognized country code (in caps). For example, a German
locale file looks like <filename>.de_DE.
|
|
|
File contents standards
Since most of the system is written in PHP,
the locale files contain simple PHP define statements.
However, some non-PHP (namely, perl and shell scripts) do parse these PHP files.
A sample locale for the Postfix mail server is shown below:
 |
Internationalization for Postfix Mail Server |
 |
 |
define('POSTFIX_LANG_BOUNCED', 'Bounced');
define('POSTFIX_LANG_CATCHALL', 'Catch All User');
define('POSTFIX_LANG_DEFERRED', 'Deferred');
define('POSTFIX_LANG_DELIVERED', 'Delivered');
define('POSTFIX_LANG_DESTINATIONS', 'Destination Domains');
... snip ...
|
 |
You will see two formats for the define statements:
- CLASSNAME_LANG_TAG for the software API
- WEB_LANG_TAG for the web page translations
|
|
|