Important Kunena 1.5 to 1.6 Language Conversion Tool

I finally got K1.5 to K1.6 language file conversion tool ready for production use.

You can use it either from CLI or from web browser. No parameters are needed, just right files in the right places and write permissions to your language directory.

Here is the directory structure that is needed to make the script to work:

Script will generate the same file structure to your own language as in en-GB.

It will include all the strings from en-GB files:
- Most of your translations will be filled in
- Untranslated entries will be commented out with the English strings in them

Please review all the translations against English strings. We have made a lot of adjustments into them
and this script does not compare content -- it just converts old format into new.

Hmmmm how to use this script? :blush: :blush: :blush:

Hi,

Like has wrote Matias you need to create this directory strucuture at the same level that kunena15to16-langconvert.php :

Create a directory for the language that you want convert, by example fr-FR for french and put in this directory the old language file designed for k1.5 :

Then you have just to launch the kunena15to16-langconvert.php and the conversion will happen

you need LINUX OS

1.But this I can create this structure in any folder?

2.When the converter tools finished to convert, move the language files in their folders... correct?

3.Every time the version is updated I relaunch the tool to get new items to be converted in my language file? or add them manually?

I've used the conversion tool to create Macedonian language file from my 1.5.12 translation, everything went smooth so in the new file "mk-MK.com_kunena.ini" i assume i should uncomment (remove the ; before the new strings) the new translation lines and that's all right?

rinuccio sp wrote: 1.But this I can create this structure in any folder?

2.When the converter tools finished to convert, move the language files in their folders... correct?

3.Every time the version is updated I relaunch the tool to get new items to be converted in my language file? or add them manually?

1°) In the same folder where you are put the script kunena15to16-langconvert.php, on the directory fo your server in wamp ...
2°) yes
3°)The script just convert things, so you need to add manually the news strings added in K1.6

Baze wrote: I've used the conversion tool to create Macedonian language file from my 1.5.12 translation, everything went smooth so in the new file "mk-MK.com_kunena.ini" i assume i should uncomment (remove the ; before the new strings) the new translation lines and that's all right?

I don't know why the string are commented :huh:

This is the beginning of mk-MK.com_kunena in the site folder

further down it continues with:

Since i plan to migrate to kunena 1.6 beta as soon as it's out i plan to finish the language file before so let me know if i'm doing something wrong with uncomenting.. also i'm not sure what should i do with the first line "; $Id: $" should i uncomment it or it part of the comment before the language strings?

Hi,

Only worry about lines that start with ;COM....

the first couple comments are for the file header and svn info - do not change or edit them.

Hope this helps!

Script generates 3 files into admin (2) and site (1) folders. It's one time conversion; you cannot use this script to update translation later on -- I would like to create another one for that purpose when I have some time.

Your task is to take those 3 files and finish the translation.

; Translator comments come into here! <- here you can put whatever you want to, like your name, site etc..

After that line you will find the translation itself (COM_KUNENA_*). Lines that are commented out are new lines from Kunena 1.6 and they contain English strings. Your primary task is to translate and uncomment all of those new strings.

They are commented out because it makes it easier to find new lines -- if you have highlighting editor, those lines will have different coloring, which makes them very easy to find.

After you have translated all the new lines, I would take English language file and look at all the translations side by side against English (all the translations should be in the same order). You will probably find better way to translate many strings.