® Parallels Plesk Expand
Copyright Notice ISBN: N/A Parallels th 660 SW 39 Street Suite 205 Renton, Washington 98057 USA Phone: +1 (425) 282 6400 Fax: +1 (425) 282 6444 © Copyright 1999-2008, Parallels, Inc. All rights reserved Distribution of this work or derivative of this work in any form is prohibited unless prior written permission is obtained from the copyright holder. Patented technology protected by U.S.Patents 7,328,225; 7,325,017; 7,293,033; 7,099,948; 7,076,633. Patents pending in the U.S.
Contents Preface 4 About This Guide ........................................................................................................................... 4 Who Should Read This Guide ....................................................................................................... 4 Typographical Conventions ........................................................................................................... 5 Feedback ......................................................................
Preface Preface In this section: About This Guide............................................................................................... 4 Who Should Read This Guide ........................................................................... 4 Typographical Conventions ............................................................................... 5 Feedback ..........................................................................................................
Preface 5 Typographical Conventions The following kinds of formatting in the text identify special information. Formatting convention Type of Information Example Special Bold Items you must select, such as menu options, command buttons, or items in a list. Go to the QoS tab. Titles of chapters, sections, and subsections. Read the Basic Administration chapter.
Localization Overview Localization Overview Since Plesk Expand is a web application, a single instance may simultaneously target an international, multi-language audience owing to the possibility of localization. Localization means a process of adapting software for a particular country or region, which is, generally speaking, translating Plesk Expand user’s environment to a language spoken in the country or region.
Localization Overview 7 In this section: Locale Components .......................................................................................... 7 Language Pack Content .................................................................................... 7 Locale Components We distinguish the following three components in Plesk Expand locale: Interface Messages.
Localization Overview The locale that is shipped by default with Plesk Expand is named default locale. You can use default locale for creating your LP. Source files of the default locale have the following locations on the server where Plesk Expand is installed: license.html location: /usr/local/expand/frontend/htdocs/locale//license.html locale.xml location: /usr/local/expand/share/locale//locale.
Creating LP 9 Creating LP Creating a language pack involves the following steps: 1 Obtaining the default (en-US) language pack sources 2 Translating the source files content to a required language 3 Compiling your resulting files to a new language pack The next sections explain how to perform each step. In this section: Obtaining Default LP ......................................................................................... 9 Translating LP Files................................................
Creating LP To obtain source files from the Localization Kit for a partial LP: 1 Copy src/en-US/ folder downloaded with this Localization Kit to your locale source files directory // (where is the code of the locale for which you create an LP): # cp -r //src/en-US/ /// 2 Remove /help/ directory from your locale source files directory: # rm -r //// To obtain source files fro
Creating LP 11 Translating LP Files Once you obtained LP sources, the next step is to actually modify interface and contextual help messages, and online help texts. For editing LP files, use text editor that supports editing text in UTF-8, and edit all the files in this encoding. Otherwise, the messages you translated may be displayed incorrectly. We recommend using text editor which also supports highlighting syntax.
Creating LP The entries are grouped into four sections: context_help_keys section contains localization for contextual help. context_help_variables section defines message variables and placeholders for messages of the context_help_keys section. messages_keys section contains localization for interface messages. messages_variables section defines message variables and placeholders for messages of the messages_keys section.
Creating LP 13 Let us assume that the locale.xml contains the following entry: plesk_register_server Click to register a new Plesk server in {$EXP_PROD_NAME}. The corresponding message in Plesk Expand GUI looks as follows: Click to register a new Plesk server in Plesk Expand.
Creating LP Do not replace USA with your country name. For example, if you translate into Portuguese, replacing “USA” with “Portugal” will be wrong. You should use the word/abbreviation meaning USA in your language. Date and Time Presentation Format For setting up date and time presentation used in your country: 1 Find the entries responsible for country-specific date and time presentation in the messages_variables section.
Creating LP 15 Compiling LP After translation is complete, you need to compile your source files into LP. The compiling is performed with Plesk Expand locale-maker utility. To install locale-maker utility: 1 Download the locale-maker packet expand-locale-maker-1.0.03.i586.rpm from the Parallels Technology Network (http://swdn.swsoft.com/), or take the packet downloaded with this Localization Kit. 2 Install locale-maker using the following command: # rpm -Uhv expand-locale-maker-1.0.0-3.i586.
Installing LP To build an LP: Run locale-maker with the following options: # /usr/local/expand-locale-maker/sbin/locale-maker—locale-path --locale-id --title --expand-version Where is your directory with source files is a locale code in the RFC 1766 standard is a title of a locale that will be shown to Plesk Expand users after installing the locale to Plesk Expand
Appendix A. Using locale-maker Utility 17 Appendix A. Using locale-maker Utility The locale-maker utility is used to build Plesk Expand Language Packs. For instructions on how it can be installed, refer to the Compiling LP (on page 15) section.
Appendix B. Locale Codes --xmlchecker-path Specifies the path to xmlchecker which validate locale.xml file. The /usr/local/expand-locale-maker path is used by default. --locale-enginepath Specifies the path to locale_engine. --spec-file Specifies the location of the locale spec file which contains LP description. The /usr/local/expand-locale-maker/locale_engine path is used by default. The /usr/local/expand-localemaker/share/spec/locale.spec location is used by default.
Appendix B.
Appendix B.
Appendix B.