all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: two@envs.net, 58571@debbugs.gnu.org
Subject: bug#58571: translations are incompletely pulled from weblate
Date: Tue, 18 Oct 2022 09:11:24 +0200	[thread overview]
Message-ID: <d214880c-c003-4bd0-05dd-8caea4f169f4@telenet.be> (raw)
In-Reply-To: <166593800749.1114521.5823817717458210706@mail.envs.net>


[-- Attachment #1.1.1: Type: text/plain, Size: 894 bytes --]

On 16-10-2022 18:33, two--- via Bug reports for GNU Guix wrote:
> hi
> in https://git.savannah.gnu.org/cgit/guix.git/tree/po/guix/uk.po i see kyrylo's translations are pulled there from weblate, but mine (https://translate.fedoraproject.org/changes/?project=guix&lang=uk&user=two22) are not, these strings stay untranslated or erroneous. [...]

If I guess correctly, translations are currently moved from weblate to 
Guix by overwriting the local .po with a copy from weblate and likewise 
in the other direction.

However, a 'msgmerge' program exists: 
‘https://www.gnu.org/software/gettext/manual/html_node/msgmerge-Invocation.html’. 
Maybe that could be used?

Also, on pushing new .po to weblate, 'git push' has a '--with-lease' 
option, which IIUC is a kind of 'atomic compare-and-swap' operation, 
which could help with avoiding race conditions.

Greetings,
Maxime.

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]

      parent reply	other threads:[~2022-10-18  7:18 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)
2022-10-18  7:11 ` Maxime Devos [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d214880c-c003-4bd0-05dd-8caea4f169f4@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=58571@debbugs.gnu.org \
    --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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.