From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Julien Lepiller <julien@lepiller.eu>
Cc: 58571@debbugs.gnu.org, two@envs.net
Subject: bug#58571: translations are incompletely pulled from weblate
Date: Tue, 18 Oct 2022 15:32:02 +0200 [thread overview]
Message-ID: <87fsfl9s19.fsf@pelzflorian.de> (raw)
In-Reply-To: <47774FCD-86D4-4FFD-8323-CCC4791045C6@lepiller.eu> (Julien Lepiller's message of "Mon, 17 Oct 2022 23:57:39 +0200")
Julien Lepiller <julien@lepiller.eu> writes:
> One thing I suspect is that weblate takes quite a lot of time to pull
> changes from the intermediate repository, so if you provide a
> translation while the repo is being synced, I think they might be
> reset when the file is finally loaded by weblate.
Something similar happened to me once: Immediately after Weblate
reported I had successfully uploaded a PO file, I decided to translate a
new untranslated string. This made Weblate lose all translations from
the previous PO file upload.
tl;dr: Yes, Weblate sometimes can lose translations.
> For anyone in that situation, the translations are not lost. You can
> always go back to them and you'll see they are untranslated, but
> you'll see a red box on the right saying it's already translated. If
> the text is correct, you can click "fix string" to apply the
> translation.
Good to hear.
Regards,
Florian
next prev parent reply other threads:[~2022-10-18 13:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-16 16:33 bug#58571: translations are incompletely pulled from weblate two--- via Bug reports for GNU Guix
2022-10-17 17:12 ` pelzflorian (Florian Pelz)
2022-10-17 21:57 ` Julien Lepiller
2022-10-18 13:32 ` pelzflorian (Florian Pelz) [this message]
2022-10-18 7:11 ` Maxime Devos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fsfl9s19.fsf@pelzflorian.de \
--to=pelzflorian@pelzflorian.de \
--cc=58571@debbugs.gnu.org \
--cc=julien@lepiller.eu \
--cc=two@envs.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).