Hi Lucas,
the files from the "translations" CI job always include a freshly regenerated inkscape.pot file, and all the .po files in the archive are synced with this .pot file. (The results from the CI job are also used to produce the translation statistics linked from the website). It's guaranteed to have the most recent strings of the respective branch.
Note, that you used an artifact from "1.0.x" branch (which is correct as this is the branch the final Inkscape 1.0 will be created from), however your MR targets master branch (which already has different strings than 1.0.x). Ideally you'd create an MR against 1.0.x branch as well, to make sure the updated translation actually applies (and ends up in Inkscape 1.0).
As for the 1.0 release it's supposed to happen around May 1st, so you have time to work on your translations until then (the sooner the better of course, as MRs need to be merged which might take a few days as well).
Cheers
Patrick
Forwarded from correct email address
---------- Forwarded message ---------
From: Lucas Vieites <lucas@codexion.com>
Date: Sun, Apr 12, 2020 at 10:12 AM
Subject: Re: [Inkscape-translator] Last call for translations for Inkscape 1.0
To: translators <inkscape-translator@lists.inkscape.org>
Hi there,I just updated the es.po from https://gitlab.com/inkscape/inkscape/-/jobs/artifacts/1.0.x/download?job=translations and created merge request https://gitlab.com/inkscape/inkscape/-/merge_requests/1720This file was different from the one I downloaded from the git branch a few days ago; it had different strings pending translation.
I hope this is will bring the 1.0 release to 100% but we can't be sure until the po files are regenerated. Will we have a window to update any pending strings once this happens before the release date for 1.0?
On Sat, Apr 11, 2020 at 9:32 PM Patrick Storz <eduard.braun2@gmx.de> wrote:
Hi all,
updates of .po files have been skipped to allow cherry-picking of
translation updates between master and 1.0.x (otherwise you'd always
maintain both translations in parallel).
If people feel it's time for a an update of *all* .po files let me know,
then I'm happy to push an update, but note that this will most likely
make cherry-picking impossible in most cases.
Anyway, as mentioned before, the very latest .pot/.po files can always
be downloaded from
https://gitlab.com/inkscape/inkscape/-/jobs/artifacts/1.0.x/download?job=translations,
so you can always base your work on the most up-to-date content if you want.
Cheers
Patrick
Am 11.04.2020 um 19:16 schrieb Yuri Chornoivan:
> субота, 11 квітня 2020 р. 17:21:03 EEST Maren Hachmann написано:
>> Am 11.04.20 um 16:00 schrieb Yuri Chornoivan:
>>> субота, 11 квітня 2020 р. 16:25:49 EEST Maren Hachmann написано:
>>>> Hi everybody!
>>>>
>>>> Things are starting to get serious with Inkscape 1.0!
>>>>
>>>> Currently, it looks as if there are about 2 weeks left for adding
>>>> translations to the 'big' release.
>>>>
>>>> So if you'd still like to help your fellow language speakers out with a
>>>> well translated Inkscape 1.0 (or its tutorials, man page, keyboard
>>>> shortcuts or Windows installer), please head to the Wiki page
>>>>
>>>> https://wiki.inkscape.org/wiki/index.php/Translation_information
>>>>
>>>> to see which files would need your attention.
>>>>
>>>> Thanks all, stay (or get) healthy and have a wonderful weekend,
>>>>
>>>> Maren
>>> Hi,
>>>
>>> Just to be sure,
>>>
>>> 1. Will the release tarballs be produced from 1.0.X branch of the main
>>> repo?
>> - As far as I know, yes. You can indicate that it's for 1.0 if in doubt,
>> the people who merge will read your info.
>>
>>> 2. Is the inkscape.pot from 2019-12-02 in the 1.0.X branch synced with the
>>> current code?
>> - As far as I can see, the file is from February 25th.
>> https://gitlab.com/inkscape/inkscape/-/blob/1.0.x/po/inkscape.pot
>>
>> I think further syncs were skipped because of string freeze (and some
>> newly added strings have not been marked for translation in the code,
>> for whatever reason... - it makes no difference at all, I don't get it -
>> if it's not translated, it's not translated. Only changing strings would
>> make a difference.), but Patrick may be able to tell you more about that.
>>
>> Kind Regards
>> Maren
> For those who are interested, since 2019-12-02 (the date of the last update of
> POT file) the string freeze in 1.0.x branch was broken with addition of the
> following lines:
>
> "Print system data directory" (/src/inkscape-application.cpp:575)
> "Print user data directory" (/src/inkscape-application.cpp:576)
> "MARGIN" (/src/inkscape-application.cpp:601)
> "Add a new selection set" (/src/ui/dialog/tags.cpp:983)
> "Line Type" (/src/ui/toolbar/lpe-toolbar.cpp:142)
> "Selection Se_ts..." (/src/verbs.cpp:3261)
> "SVG 2 Specification" (/src/verbs.cpp:3302)
>
> It would be good to re-sync the POT file with the code in 1.0.x branch.
>
> Thanks for your help.
>
> Best regards,
> Yuri
>
>
>
>
>
> _______________________________________________
> Inkscape-translator mailing list
> Inkscape-translator@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/inkscape-translator
_______________________________________________
Inkscape-translator mailing list
Inkscape-translator@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/inkscape-translator
_______________________________________________ Inkscape Translators mailing list -- inkscape-translator@lists.inkscape.org To unsubscribe send an email to inkscape-translator-leave@lists.inkscape.org