3. first testing if everything is ok ..
reload your ispconfig .. if you don't see any changes all is ok

4. Now translate text in new created files to your language ..
remember that you have to use right charset encoding .. same as you will use on ispconfig pages. It will be a lot of work .. you will translate a lot of sentenses more than once .. so be patient .. sometimes check your work by reloading ispconfig .. it should be partialy translated ..

Done? Now you have to change charset encoding in some files.

5. changing and adding meta tags

For properly working encoding you have to change or insert meta tags to some files .. here is list of its ..

Go to /root/ispconfig/isp/ and copy error_en to error_XX (in my case error_cz) and edit *.html files in created directory.

And it is all .. that was quite easy .. wasn't that?

Little suggestion for Falco and Till .. if it is possible it would be nice to have meta tags in files listed here with charset encoding variable from config.inc.php file .. translation will be more easy ..

Nice guide. I think we can refer to this if anyone else is asking for translation guidelines.

SupuS said:

Little suggestion for Falco and Till .. if it is possible it would be nice to have meta tags in files listed here with charset encoding variable from config.inc.php file .. translation will be more easy ..

Nice guide. I think we can refer to this if anyone else is asking for translation guidelines.

We'll check if/how this can be done.

Click to expand...

just an idea...:

in osCommerce they put this lines in some english.php file located under /languages:

------------------------------------------------------------------
// look in your $PATH_LOCALE/locale directory for available locales..
// on RedHat6.0 I used 'en_US'
// on FreeBSD 4.0 I use 'en_US.ISO_8859-1'
// this may not work under win32 environments..
setlocale(LC_TIME, 'en_US.ISO_8859-1');
define('DATE_FORMAT_SHORT', '%m/%d/%Y'); // this is used for strftime()
define('DATE_FORMAT_LONG', '%A %d %B, %Y'); // this is used for strftime()
define('DATE_FORMAT', 'm/d/Y'); // this is used for date()
define('PHP_DATE_TIME_FORMAT', 'm/d/Y H:i:s'); // this is used for date()
define('DATE_TIME_FORMAT', DATE_FORMAT_SHORT . ' %H:%M:%S');
....
....
and these lines too:

in the tad <html dir="ltr" lang="en"> is really nescessary or just nice to have

Click to expand...

I saw bold text only .. this tag elements are relevant for xhtml only .. so I think it isn't necessary for ispconfig now .. because it is in html. Change ispconfig to xhtml valid will be hard work .. because it use xhtml invalid elements in code .. adding dir="ltr" lang="en" elements and changing DTD is not sufficient to valid xhtml code

I'm translating ispconfig to Turkish. Language & html files ok but how about database backend? When sorting in Turkish, some letters must be placed between c and d, h and j.. etc. So to do this, in db backend you have to use utf8 or latin5. i think utf8 fits all of us?

hello everyone!
i am new at ispconfig, now i have translate Isp config in japanese from english, i have already change all en.lng files by the direction from this forums, (i make jp.lng files )
but the problem now i am facing is ,
1. after completing translation including changing the charshet of config.inc.php(i changed it to UTF-8) , when i add client and login to that client management by browser, then nothing can be seen in browser.
2.if i login by using Internet Explorer, the management tools doesnt reloaded,
its give a massege likeOrdner werden geladen....
Loading folders....
is that anything probelm of my setting over tranlating? or the charshet i have choosed for ispconfig (UTF-8) is not appropiate for the translation of ispconfig.
on the other hand, the distribution is centos 5.1 ,and running over the kernel
2.6.18-53.1.14.el5xen.
please give me some suggegsotion.