Translation status

[bp0]

hardinfo.pot now has 1213 strings (+84), with 69 c-format strings ( 860b43d1a6f8640517e8772a250f273533e96ed7)

• [ ] de.po : (1016 / 1213 remain untranslated, needs work/fuzzy: 2)
• [ ] es.po : (538 / 1213 remain untranslated, needs work/fuzzy: 0)
• [ ] fr.po : (807 / 1213 remain untranslated, needs work/fuzzy: 0)
• [ ] pt_BR.po : (151 / 1213 remain untranslated, needs work/fuzzy: 0)
• [ ] ru.po : (422 / 1213 remain untranslated, needs work/fuzzy: 0)
• [ ] zh_CN.po : (835 / 1213 remain untranslated, needs work/fuzzy: 0)

[mckaygerhard]

do you think its necesary a manpage autocreation tool based by example in help2man? and then translated dinamically? on only let the english only manpage due the project its not so big to?

[bp0]

I vote English only, simple to maintain. Does the command line interface even properly support translation? LANGUAGE=ru hardinfo --help is still in English for me. Also, LANGUAGE=de LC_ALL=de_DE.utf8 hardinfo -r -t text is in English. LANGUAGE=de hardinfo starts the GUI in German. Seems like the CLI translation support isn't working.

Edit: This was fixed in 4e05ca524fd75bccbb87d790f10118c650320cda.

[mckaygerhard]

well we can generate a main englysh, later translate to.. umm wel as you note seems complicated now that --help output does not support translation!

[mckaygerhard]

hi! i can see the about dialog has to many string depending of coding contribution.. can be made a parsing script tool that updates in every compilation taking that from AUHTORS.md file? i mean, due this lines of authors contributors are not translatables! i just an idea due every commit that change any translated part, will let the xx.po files related outdated... and that's why i cannot concentrate in updated the languajes that i can contribute (English, some russian and greek)

[bp0]

i just an idea due every commit that change any translated part, will let the xx.po files related outdated...

I don't completely understand what you are saying, but if you are saying that old translations are lost when one translation changes, that really isn't true. Only that one string needs to be retranslated, and the old translation is added to the "obsolete strings" section of the .po file. Whenever I change a translated string, I try to, and usually do, restore the old translated version.

and that's why i cannot concentrate in updated the languajes that i can contribute (English, some russian and greek)

I would guess that English isn't your first language, but I would never have guessed it was Greek. :smile: Don't you speak Spanish or Portuguese? I have the sense you are from South America.

[mckaygerhard]

i have two problems.. the keyboards of the machines are too softly and i write too fast.. yes i 'm very lazy to write.. and i started to write in the typewriter machines.. so i hate the very soft way of the modern keyboards.. my mom ithe the "greek speaker" (well speak many languajes, i the only in my family that only speak one languaje), and yes snif snif i'm from suth america... trying to provide many things that here ther its not are yet for us... as my profile can show it

My fault due I do not explain well and write in a run over, I meant that there are too many changes in the same pull, and although it does not change much in the translation files, from the translator's point of view it is doubtful to know to him if there any string changes or No, specially if want to contribute and have many task on mind of other bussiness

as each pull pulls many things and is not focused, such changes you never know when it affects or not a translation pull .. in summary it is difficult to follow you and it would be difficult to another if it is not possible to coordinate the changes and these Not be mixed, which will greatly avoid conflicts in the merge

[vegnuli]

finished the spanish, i ask there's something working in the russian translation?

[mckaygerhard]

i finished the spanish, if nobody i can also try the russian ..

[mckaygerhard]

hi! the manpage will be translated? there's something working in the ru.po? i only run the script and the es.po file will be updated right!?!

[bp0]

hi! the manpage will be translated?

If someone wants to create a manpage in another language, using LANGUAGE=XX hardinfo --help as a starting point, that is fine. Unless they are willing to translate all the other parts, I don't know that it is any more valuable than just hardinfo --help.

there's something working in the ru.po?

TotalCaesar659, has been pretty consistent in updating ru.po.

i only run the script and the es.po file will be updated right!?!

When you run the script, all .po files will get updated with new strings added to the code since last update, via hardinfo.pot. You don't have to commit any .po files you don't edit, though. You don't even have to commit hardinfo.pot, but it is nice to update it now and then. Latest update is 92ea12b9212fa44413277d82fa3df479384dab89. If nothing changed in the code since then, the script doesn't need to be run at all. It also doesn't need to be run to edit existing translations.

[mckaygerhard]

so, thanks @bp0! cach it! ... and .. my coffe!?