Two thoughts:
- I don't know if you're aware but the translation in 0.92.x
branch is much more complete. It might make sense to work
with that one as a starting point for the translation in master.
- You should probably sync cs.po with the latest inkscape.pot
before putting work into the translation.
Also you might want to coordinate translation efforts for Czeck locale with helix84 who provided the last updates for 0.92.x (I subscribed him).
Let me know if/when I should merge; I'll hold off for now and let you decide how you want to proceed.
Hi Eduard,
thanks for a message.
I wasn't aware about some other newer more complete translation. I thought here http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/files/head:/po/ are always most recent translations!
Can you tell me where I can find the 0.92 translation?
Maybe you can just merge my cs.po in 0.92 translations, so that some possible untranslated or fuzzy messages in 0.92 translation will import from my cs.po, if any?
First of all Inkscape moved to GitLab, so the latest files will be at https://gitlab.com/inkscape/inkscape/tree/master/po
However those are for the "master" branch (i.e. most recent unstable development version or future Inkscape 0.93).
The translation files for the stable branch ("0.92.x") are at https://gitlab.com/inkscape/inkscape/tree/0.92.x/po
and there you'll find cs.po was last updated 2017-01-01, i.e. is much more current (and I think it even has some of the strings you translated)
Unfortunately translations won't "import" automatically between branches, so they have to be kept up to date side-by-side by translators (at least until somebody comes up with a very clever way how to simplify this).
Ok, I'll download cs.po from 0.92 and continue with it. How can I upload updated version there?
Since now 0.93 is under development, would it again mean that my translations done under 0.92 branch will not apply to 0.93 and 0.93 messages, which are already in 0.92, will have to be again translated in 0.93?
Hi, yes, I put the most current translation into the 0.92 branch when I did the last update because the next release was going to be from there. I haven't had much time to complete it since then. Moreover, the GitLab migration has happened and I haven't asked for commit access to git yet.
Anyway, any help with the Czech translation is welcome. I won't have time to work in it at least until the end of the year. Please, take a look at the gettext msgmerge tool or the Translate Toolkit pomerge tool which will help you with both merging the .po from 0.92.x to the master .po and with updating the .po to the latest .pot.
Hint: the software Lokalize supports automated merging of translations from one open translation file into the other, so you'd only need to work once on strings that are in both files.
Hi there, there have been a number of changes to the Czech Inkscape translations since this bug was opened. If you have new translations, please send a merge request on GitLab. Thank you!
Hi Ivan, thanks for the update!
Two thoughts:
- I don't know if you're aware but the translation in 0.92.x
branch is much more complete. It might make sense to work
with that one as a starting point for the translation in master.
- You should probably sync cs.po with the latest inkscape.pot
before putting work into the translation.
Also you might want to coordinate translation efforts for Czeck locale with helix84 who provided the last updates for 0.92.x (I subscribed him).
Let me know if/when I should merge; I'll hold off for now and let you decide how you want to proceed.