confirmed, it's an annoying GitLab issue that hasn't been addressed for
quite some time.
I think it could potentially be fixable by adjusting our Continuous
Integration to not have the Windows builds in a separate pipeline and to
just go by date instead or whatever. (or, of course, GitLab itself could
fix it, but they have known about the problem for a couple years now, so
I'm not hopeful.)
The summary is that the additional, scheduled (so, resource-conscious)
job of the Windows builds overwrites the build results listed in the
dropdown and drops old build results from the 'latest' job.
You can still always find the latest successful build for 1.1.x here in
this list (don't choose those that are have the little 'Scheduled'
badge, but the latest one of the others):
Or, just wait a bit... (not a great idea at the moment).
Or, currently, the po and pot files in the repository are up to date,
too, but that is never guaranteed.
I'm including the developer mailing list as this is something they might
have a way to fix.
Am 16.01.22 um 15:31 schrieb Firas Hanife:
I'm not sure if it's only an issue on my side but I'm unable to get the
latest translation from 1.1.x branch artifacts.
The provided link leads to a "Page Not Found" message.
Can anyone confirm?
Il giorno sab 15 gen 2022 alle ore 17:03 Maren Hachmann
<maren(a)goos-habermann.de <mailto:email@example.com>> ha scritto:
Hello Inkscape translators!
This is the official call for translations for the upcoming Inkscape
1.1.2 , which is planned to be released in early February.
1.1.2 is expected to be the last in the 1.1.x series of Inkscape, and it
is bugfix release, so the number of updated strings is small.
If you'd like to contribute to 1.1.2 translations, please coordinate
with everyone in your language's translation team, and get the latest po
and pot files from
Further information is available from
If you are a translator for any of the languages below, please also
check your 1.1.x branch po file for errors – either using the
translation tool of your choice, or by compiling it to a mo file on your
computer and reading the output – as they contain formatting errors and
/ or do not properly indicate the language they are for (default value
is still set):
as, az, doi, en_AU, en_CA, eo, es_MX, fa, hy, kok@latin, ks@aran, mk,
ml, mni@beng, mni, mr, or, sat@deva, sat, sd@deva, sd, ur, ta
Inkscape 1.2 (currently still the same as the master branch) is
approaching its alpha stage. Translations for 1.2 are already accepted,
but it is expected that especially the newly added strings will still
change until the release.
Inkscape Translators mailing list --
To unsubscribe send an email to
Inkscape Translators mailing list -- inkscape-translator(a)lists.inkscape.org
To unsubscribe send an email to inkscape-translator-leave(a)lists.inkscape.org