Interface language

[surquizu]

also error

I have attached two possible solutions in post # 44, one eliminating the small font size and other changing the encoding to UTF-8-BOM as it is the one test that had worked well. The file whith error has a coding "system". I don't see more diferences (only the last addeded of large text strings and texts strings with double translation).

[tshering]

Originally Posted by surquizu

also error

I have attached two possible solutions in post # 44, one eliminating the small font size and other changing the encoding to UTF-8-BOM as it is the one test that had worked well. The file whith error has a coding "system". I don't see more diferences (only the last addeded of large text strings and texts strings with double translation).

I have to remove the BOM anyway, so that does not make a difference. As for your trial to eliminate the small font size, this seems not to work as expected (I upload the patch nonetheless), see the attached screen_20150417b.png. The main problem (seen in the picture of post #41) seems to me to be the fact that html tags are interpreted as normal text. This explains also why the font size (set in the span tag) is not respected. Why the html tags are not treated as such in this position, I do not understand. I tried something different. That seems to work on Touch (screen_20150417c.png), maybe it is working on your reader too. If you see again html code, could you please remove all other patches (like the Bad eyes patch) so that we can narrow down the possibilities?

Please take over all changes of post #40 into your xlsx file. Watch out for "\ n" (2 cases), and replace them by "\n".

[surquizu]

Originally Posted by tshering

That seems to work on Touch (screen_20150417c.png), maybe it is working on your reader too.

The modification you've done works well. It looks perfect and it has the word "Llegit" that I could not put. Fantastic.

thank you very much.

Please take over all changes of post #40 into your xlsx file. Watch out for "\ n" (2 cases), and replace them by "\n".

My apologies.

[tshering]

Originally Posted by surquizu

The modification you've done works well.

I am glad it turned out that way.

[mietek81]

Ok, so what should I do, where should I begin to start translating interface into polish?

[tshering]

Originally Posted by mietek81

Ok, so what should I do, where should I begin to start translating interface into polish?

Are all characters of the Polish alphabet supported by the system fonts? If some are not, you might reconsider whether to start the translation project.
If you would like to start, please decide which of the supported languages you would like to replace. Considering the average word length of the languages, German might be convenient. I upload the German translation strings. If you would like to overwrite another language, please tell me.
The uploaded archive contains two text files, one for invariable expressions, and one for expressions that differ according to singular and plural, cf. posts #17 and #37 for the format. In each case the Polish translation must not consist of more characters than the German does.

[mietek81]

Yes, I think that all diacritics are now supported. In some very old firmware they were not displaying in books synopsis but now they are, so I suppose it is ok.
Yes, German can be lost in translation

Can I switch parts of translation strings like this
from

AddToShelfWidget{ref}%n BOOK(S){tr}%n BUCH{tr2}%n BÜCHER

to

AddToShelfWidget{ref}%n BOOK(S){tr}%n TOM{tr2}TOMÓW: %n

or completly skip the %n parts or replace it with number 1 where applicable? Or maybe the %n is not for number?

Damn.. Polish word for Book/Buch (Książka) is way to long. Many polish words are longer then german. This is going to be hard and take a lot of time..

Ok, so there is first major problem. English "yes" is German "Ja" and Polish "Tak". I could use "OK" but that might not be looking good in all places. Maybe I should use another language instead of German? Which language has "yes" with at least 3 letters?

[scoky]

Originally Posted by tshering

Are all characters of the....... does.

Hi tshering, could you tell me how to generate zlib file to patch nickel? I just want to have a try to make a Chinese language translation.
Thanks.

[tshering]

mietek81,
I just noticed by chance that you added something to your old post!

Originally Posted by mietek81

Can I switch parts of translation strings like this
from

AddToShelfWidget{ref}%n BOOK(S){tr}%n BUCH{tr2}%n BÜCHER

to

AddToShelfWidget{ref}%n BOOK(S){tr}%n TOM{tr2}TOMÓW: %n

or completly skip the %n parts or replace it with number 1 where applicable? Or maybe the %n is not for number?

You can change the position of %n as you like.

Originally Posted by mietek81

Damn.. Polish word for Book/Buch (Książka) is way to long. Many polish words are longer then german. This is going to be hard and take a lot of time..

The size limit is a big problem with this approach.

Originally Posted by mietek81

Ok, so there is first major problem. English "yes" is German "Ja" and Polish "Tak". I could use "OK" but that might not be looking good in all places. Maybe I should use another language instead of German? Which language has "yes" with at least 3 letters?

English, French, ... I upload the files for all supported languages. Maybe you can find one that fits somehow.

[tshering]

Originally Posted by scoky

Hi tshering, could you tell me how to generate zlib file to patch nickel?

Generally speaking, one has to (1) extract the zlib stream from nickel, (2) decompress its content, (3) replace the translation strings by your own, (4) compress it, and (5) re-insert it into nickel.
Describing the details however is a little difficult for me. If I find time, I will try to publish a tool that will assist you in the steps 1 to 4.

Originally Posted by scoky

I just want to have a try to make a Chinese language translation.

For now, I can only offer that you upload (or PM) your sample translation file and I provide you with the zlib file.

[mietek81]

Ok, Kobo just released 3.15 version of firmware. So I guess that something might have changed and strings extracted from older firmware can be different?

[tshering]

Originally Posted by mietek81

Ok, Kobo just released 3.15 version of firmware. So I guess that something might have changed and strings extracted from older firmware can be different?

This is true. Some strings have disappeared, others have been slightly changed. Did you already settle for a language?

[tshering]

surquizu,

I guess this was an unfortunate time to start the translation project. There changed a lot in FW 3.15.0. I upload the files containing the differences between 3.13.1 and 3.15.0.

[surquizu]

Originally Posted by tshering

surquizu,

I guess this was an unfortunate time to start the translation project. There changed a lot in FW 3.15.0. I upload the files containing the differences between 3.13.1 and 3.15.0.

Thank you. I'll update the translation for the 3.15

[surquizu]

Originally Posted by tshering

surquizu,

I guess this was an unfortunate time to start the translation project. There changed a lot in FW 3.15.0. I upload the files containing the differences between 3.13.1 and 3.15.0.

Hi Tshering,

Attached the file with the translation of text strings of firmware 3.15.0. And also I have prepared a test file to locate errors of context in translation.

thanks