Originally posted by bluescript
hmm, ok... simply overwriting the English language files with the German ones rendered Plesk unusable - no login page, said it couldn't find the default locale... strange. well, good idea I backed it up before. so after restoring I tried again, installing the German language-pack in addition to the English one - and simply renaming the folders: en-US to de-DE and vice versa.
go with your phpmyadmin into the "psa"
SELECT *
FROM `clients`
LIMIT 0 , 30
you find there the default-locale en-US. It is possible to edit
it there to de-DE.
Originally posted by bluescript
what's interesting is that the German langpack is obviously incomplete - dates back to February. some elements are not translated, like "Server Preferences" or "Interface Management"
Search complete, found 'Server Preferences' 0 time(s).
Search complete, found 'Interface Management' 0 time(s).
Hmm? Which version do you use?
Originally posted by bluescript
So I edited /usr/local/psa/admin/htdocs/locales/default and pointed it to de-DE (the former en-US). This way the missing items are at least displayed in English...
no,
vi -R /usr/local/psa/admin/htdocs/locales/default
en-US:ENGLISH:GERMANIC:UNITED STATES;
-->
de-DE:GERMAN:GERMANIC:GERMANY;
Originally posted by bluescript
one thing I'd like to know: where in the database are the langpack descriptions stored (like "English (United States)")? this is no doubt just a cosmetic detail but if this could be modified as well, that'd be real perfect.
fid-locale
-----
<select name="locale" id="fid-locale" onChange="locale_oC(document.forms[0], document.forms[1])"><option value="default">User default</option>
<option value="en-US" SELECTED>ENGLISH (United States)</option>
</select>
------
SHELL thinks:
---------
product_log="/tmp/${my_name_1}.log"
config="/etc/$product/$product.conf"
test_for_root
get_etc_conf
dist_dir="$product_root"
admin_user="${product}adm"
admin_group="${product}adm"
admin_passwd="`cat /etc/$product/.psa.shadow`"
mysql="$mysql_bin_dir/mysql -N -uadmin -p$admin_passwd ${product}"
locale="de-DE"
locale_full="de-DE:GERMAN:GERMANIC:GERMANY;"
echo >> $product_log #initializing log
echo "START LOGGING: `date`" >> $product_log
------
So, have a look into your
vi -R /usr/local/psa/admin/htdocs/locales/default
))
I think, you need not to rename the folder. Remember, the
"en-US" is only a folder which is at the same time also the
default-folder. And the content itself can be in another
language, of course.
But in the other side, if you upgrade to 7.6 or whatever, then
it might happen, that the content will be overwritten. So, for a
long-timeable solution, you should also exchange the en-US
within the SQL. And there are 57 entries.
I personally would let the en-US be as it is with all the english
content. And you add the 2nd language which is also the
default-language. It is only _new_ that you have another
_default_ language. The licence is only if you want to use
_two_ languages, but this is not the case.
vi -R /usr/local/psa/admin/htdocs/locales/default
en-US:ENGLISH:GERMANIC:UNITED STATES;
-->
de-DE:GERMAN:GERMANIC:GERMANY;
So, I think, Plesk only picks up the content from the default-folder
which is here the "de-DE"-folder. But it is a _must_ that the
content really exist.
Keep me informed about this and what you could find out, tx.
Originally posted by bluescript
on a sidenote: who exactly is it that maintains the language packs? I mean the German langpack is clearly outdated but is still labelled as being designed for Plesk 7.5.3. charging $99 for an incomplete language pack seems a bit questionable to me?
Oh, they also want USD 199 for out-to-date Appl.Vaults, see
http://forum.plesk.com/showthread.php?s=&threadid=23626
Facebook
Twitter
