Article ID: 6075, created on Feb 25, 2009, last review on May 8, 2014

  • Applies to:
  • Plesk 9.x for Linux/Unix

Symptoms

I compiled custom locale according to Parallels Plesk Panel 9.0 for Linux/Unix Localization Guide. Namely, opened the default English locale files in Windows and made the translation. Then compiled resulting files to a new language pack and installed it.

When select new locale on login page {Interface language} or in Parallels Plesk Panel on page {Home -> Account -> Interface Preferences -> Interface language} skin looks bad. Some fields look overlapped or missing. The problem does not depend of web browser, it exist for Safari, Firefox, IE7, etc.

Cause

Locale files contains extra bytes <EF><BB><BF> before first tag <?php.
As an example let's consider custom locale hu-HU, that is compiled in directory plesk90.hu-HU.locale.

To see these extra bytes you should open a file from directory dist/plib/locales/hu-HU/ with command less.

~# less /PATH/TO/plesk90.hu-HU.locale/dist/plib/locales/hu-HU/common_messages_hu-HU.php
<EF><BB><BF><?php  <- corrupted tag with extra bytes

// This file contains structured and commented locale keys for common features between PFW & PFU

$GLOBALS['lmsg_arr'] += array (
.....


Other text editors except less and hexdump do not show them.

These bytes are considered as HTML code by web browsers (for example firebug) and cause extra symbols/line brakes are included and skin is shown incorrectly.

They may appear when Cyrillic is being saved to UFT-8.

Resolution

To resolve the problem you should remove these extra bytes form the files.

You may copy the first line from files in default English locale and past it to files from your locale. The first line should look like the following:

~# less /usr/local/psa/admin/plib/locales/en-US/common_messages_en-US.php
<?php  <- correct tag without extra bytes

// This file contains structured and commented locale keys for common features between PFW & PFU

$GLOBALS['lmsg_arr'] += array (
.....

6ef0db7f1685482449634a455d77d3f4 a914db3fdc7a53ddcfd1b2db8f5a1b9c 29d1e90fd304f01e6420fbe60f66f838 56797cefb1efc9130f7c48a7d1db0f0c

Email subscription for changes to this article
Save as PDF