We recommend using a text editor which supports highlighting syntax for
editing the locale files. Using such an editor makes translating more
comfortable, and also helps you detect accidental changes to the syntax
of the files.
Note: Use an editor that supports editing texts in UTF-8.
Caution: Do not change the encoding of the files: It must be UTF-8. Otherwise,
the messages you have translated may be displayed incorrectly.
There is a number of recommendations that might be useful when
translating Plesk locale files, specifically concerning PHP array
syntax, message variables, HTML entities, and special characters.
PHP array syntax
# It is important that commas at the end of each string are not
removed. Otherwise, the PHP array will be corrupted, and Plesk GUI will
display localization keys instead of the translated messages.
# Pay attention to the usage of quotation marks. Follow these
guidelines to avoid making a mistake:
1. If the message text does not contain any quotes, enclose the text
with either single or double quotes.
- If the message text contains at least one single quote or apostrophe:
- precede each quote with a backslash:
'b_add_ip_for_clients' => 'Add IP address to client's pools.',
or
- enclose the message in double quotes:
'b_add_ip_for_clients' => "Add IP address to client's pools.",
- If a message text contains at least one double quote:
- precede each quote with a backslash:
'odbc__mysql_option' =>
"Options that specify how MyODBC should work. See <a href="http://dev.mysql.com/doc/mysql/en/Connection_parameters.html">http://dev.mysql.com/doc/mysql/en/Connection_parameters.html</a>",
<…