Info before updating/fixing italian translation

koraynilay via Gnupg-devel <[email protected]> Tue, 21 Apr 2026 01:09:17 +0200
Newsgroups gmane.comp.encryption.gpg.devel
Message-ID <[email protected]>
--===============7135881471520168127==
Content-Type: multipart/signed;
 boundary=f0d99c3ed0d14fd5f551dc8347209e992501f87c41fcae9ab9f728d94b00;
 micalg=""; protocol="application/pgp-signature"

--f0d99c3ed0d14fd5f551dc8347209e992501f87c41fcae9ab9f728d94b00
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=UTF-8

Hello, I'm looking at fixing some strings in the italian translation of
GnuPG (po/it.po) but I noticed that when running make all translations
get rearranged, would it be better to first make a commit like "resync
translation(s)" and then do my modifications after, or would it be
better to keep my changes before the po(s) get changed during make?

Furthermore, if the "resync" commit is the better way, would it be best
to commit all languages' files or only the one I'm interested in?

Thanks in advance.

P.S. sorry if it's the wrong list or there are other mistakes, I'm still
new to this type of contribution style ahah.

Best,
koraynilay

--f0d99c3ed0d14fd5f551dc8347209e992501f87c41fcae9ab9f728d94b00
Content-Type: application/pgp-signature; name="signature.asc"


--f0d99c3ed0d14fd5f551dc8347209e992501f87c41fcae9ab9f728d94b00--


--===============7135881471520168127==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Gnupg-devel mailing list
[email protected]
https://lists.gnupg.org/mailman/listinfo/gnupg-devel

--===============7135881471520168127==--