Adding new interface languages

[tshering]

Originally Posted by kaznelson

This link is broken...

I corrected it. The link is this.

[boriar]

Originally Posted by tshering

I guess there should already be a tool available, but I was unable to find one. But that does not mean much, since I am not very familiar with Qt. Currently I am trying to interpret the binary data of the qm file and convert it to the ts format, which actually is xml, as you already know.

@tshering: You don't need a special tool to open qm files. Open it with QtLinguist and save it like ts one. That's the program I use to make the spanish translation for pbchess-coolreader and never have a problem.

PS: tshering, sorry for not to help you with rotation issue. I have other problems with experiments in my H2O and very few spare time to test anything (work, work, work )

[tshering]

Originally Posted by boriar

@tshering: You don't need a special tool to open qm files. Open it with QtLinguist and save it like ts one. That's the program I use to make the spanish translation for pbchess-coolreader and never have a problem.

Thank you for this valuable information. I had looked at this program, but was not aware that it can read qm files. Oddly, there is no *.qm filter in the open dialog.

Had I known that those things in nickel are qm files, and further that they can be read by Qt Linguist I could have saved a lot of time.

Originally Posted by boriar

PS: tshering, sorry for not to help you with rotation issue. I have other problems with experiments in my H2O and very few spare time to test anything (work, work, work )

No problem!

[lav89]

@tshering:
I tried my translation on FW 3.13 - it works but there was smaller qty of translated items

[tshering]

Originally Posted by lav89

@tshering:
I tried my translation on FW 3.13 - it works but there was smaller qty of translated items

This was to be expected. Since 3.13 there were several changes to nickel. Changes that affect us here are: changed class names, changed source language strings, and removed functionality. You would have to replace or add the respective data in the 3.16 ts file to adjust it to 3.13. Maybe some part of the Qt Linquist package supports comparing ts files.

[surquizu]

Originally Posted by tshering

I corrected it. The link is this.

without a tutorial step by step, I don't understand how to generate the qt desde libnickel

[tshering]

Originally Posted by surquizu

without a tutorial step by step, I don't understand how to generate the qt desde libnickel

Did you continue working on the translation of our old style translations file? If you did not, I will convert your translation file for 3.15.0 to ts format, and update it to 3.16.0. Then you can enter the remaining translations with Qt Linguist or with a text editor. If you did continue working on the file, please upload the new file in the current state, and I will convert it. I will be away for the weekend, however. So do not expect the result to soon.

[tshering]

I created a trans_ca.ts for 3.16.0. The vanished translations (those of 3.15.0 that are not needed in 3.16.0) are included and marked with type="vanished". If you open the file with Qt linguist they have a grey check mark.
Before spending much time with inputting new translations, please inspect the data carefully. I am not sure whether everything worked out nicely. Have especially a look at those translations that have singular and plural forms.

If you finally create a qm file, please rename it to trans_es.qm before installing it on the reader.

Edit: I think I did it better with 3160_ca_noobsolete.zip. There are no vanished/obsolete translations included and the handling of numerus forms is better. Edit 2: This is still not usable. I removed it again.

[tshering]

I updated post '23

[surquizu]

I think it's best to use the new procedure. I'll work on the translation with the ts format.

[tshering]

Originally Posted by surquizu

I think it's best to use the new procedure. I'll work on the translation with the ts format.

Good decision! Please have a look at the file I have uploaded to this post. It is for FW 3.16.0. Your previous translations are included. Have you already Qt linguist installed?

If you find something suspicious please do not continue working and tell me. I might have to improve some parts of the update procedure.

[surquizu]

Originally Posted by tshering

Good decision! Please have a look at the file I have uploaded to this post. It is for FW 3.16.0. Your previous translations are included. Have you already Qt linguist installed?

If you find something suspicious please do not continue working and tell me. I might have to improve some parts of the update procedure.

Yes, I have installed the qt linguist, but I prefer "virtaal" to do the translation.
http://virtaal.translatehouse.org/index.html

[lav89]

Originally Posted by tshering

This was to be expected. Since 3.13 there were several changes to nickel. Changes that affect us here are: changed class names, changed source language strings, and removed functionality. You would have to replace or add the respective data in the 3.16 ts file to adjust it to 3.13. Maybe some part of the Qt Linquist package supports comparing ts files.

tshering, could you make TS file for 3.13?

[tshering]

Originally Posted by lav89

tshering, could you make TS file for 3.13?

Sure!

[surquizu]

Hi Tshering,

The method of translation with "qm" works well, but there are some texts that I can not translate. I do not understand why because the text strings in "qs" file are apparently well translated. See the images.