18 Creating And Installing LP
Translation Tips
For editing the files that build Plesk online help system, we recommend using a
WYSIWYG HTML editor which supports working with files in UTF-8. Using such editor
makes the process of translation more comfortable because it
lets you concentrate on modifying the help content without the necessity of
separating it from the HTML syntax;
prevents you from modifying anything besides the help content, which guarantees
that the files will not be corrupted somehow.
Important: Do not change the files encoding: It must be UTF-8. Otherwise, the texts
you translated may be displayed incorrectly.
Compiling LP
Once you translated the locale-defining files to a required language, you are ready to
compile them to a language pack, which will be easily installed to Plesk afterwards.
To compile an LP:
1 Unpack the std_lp.tgz archive downloaded with this Localization
Kit.
2 Go to the directory std/dist/ created during unpacking the archive
on the previous step.
3 In the std/dist/, create the LP directories structure (for details,
refer to the Language Pack Content (on page 9) section) assuming that
std/dist/ is an LP root. Replace <locale> in directories names with
the name of your language pack.
For example, if making up a language pack for Dutch spoken in The Netherlands
(nl-NL), the directories you create must be std/dist/plib/locales/nl-NL and
std/dist/htdocs/locales/nl-NL. For the list of locale/LP names supported
by Plesk, refer to the Locale Codes (on page 20) section.
4 Copy your translated LP files to the directories created on the
previous step.
Be sure to include to the std/dist/ directory all directories and files building an
LP: Even if you are making a "partial" LP (only GUI and contextual help messages
translated), include the default online help files and folders. Otherwise, your LP will
not be compiled (in case when htdocs/... folders are missing), or no online help
will be available after applying the LP (in case when files in the htdocs/.../
folders are missing).
