From: Maximiliano Sandoval <m.sandoval@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH proxmox-i18n 0/7] Makefile simplifications and improvements
Date: Mon, 20 Jul 2026 13:13:34 +0200 [thread overview]
Message-ID: <20260720111343.353644-1-m.sandoval@proxmox.com> (raw)
The main difference is that we add --previous to the msgmerge command used to
update the PO files. This can add some extra information to translations, which
can make it easier to determine whether the previous translation is still valid
or what kind of modifications it needs.
Addtionally, there are a couple of cleanups.
Maximiliano Sandoval (7):
make: catalog-%.mo: explicitly set template file
make: simplify msgmerge commands
make: clean: Cleanup *.mo files
make: do_update: use long options for msgmerge
make: do_update: use --update for msgmerge
make: add --previous flag to msgmerge
gitignore: remove proxmox-datacenter-manager.pot
.gitignore | 1 -
Makefile | 16 ++++++----------
2 files changed, 6 insertions(+), 11 deletions(-)
--
2.47.3
next reply other threads:[~2026-07-20 11:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 11:13 Maximiliano Sandoval [this message]
2026-07-20 11:13 ` [PATCH proxmox-i18n 1/7] make: catalog-%.mo: explicitly set template file Maximiliano Sandoval
2026-07-20 11:13 ` [PATCH proxmox-i18n 2/7] make: simplify msgmerge commands Maximiliano Sandoval
2026-07-20 11:13 ` [PATCH proxmox-i18n 3/7] make: clean: Cleanup *.mo files Maximiliano Sandoval
2026-07-20 11:13 ` [PATCH proxmox-i18n 3/7] make: clean: remove " Maximiliano Sandoval
2026-07-20 11:13 ` [PATCH proxmox-i18n 4/7] make: do_update: use long options for msgmerge Maximiliano Sandoval
2026-07-20 11:13 ` [PATCH proxmox-i18n 5/7] make: do_update: use --update " Maximiliano Sandoval
2026-07-20 11:13 ` [PATCH proxmox-i18n 6/7] make: add --previous flag to msgmerge Maximiliano Sandoval
2026-07-20 11:13 ` [PATCH proxmox-i18n 7/7] gitignore: remove proxmox-datacenter-manager.pot Maximiliano Sandoval
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=20260720111343.353644-1-m.sandoval@proxmox.com \
--to=m.sandoval@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/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.
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.