From: Kuma8866 via pve-devel <pve-devel@lists.proxmox.com>
To: pve-devel@lists.proxmox.com
Cc: Kuma8866 <kuma8866@163.com>
Subject: [pve-devel] PVE_i18n_GitPatch.2025-12-19
Date: Mon, 22 Dec 2025 19:19:13 +0800 (CST) [thread overview]
Message-ID: <mailman.162.1766485018.353.pve-devel@lists.proxmox.com> (raw)
[-- Attachment #1: Type: message/rfc822, Size: 4933 bytes --]
From: Kuma8866 <kuma8866@163.com>
To: pve-devel@lists.proxmox.com
Subject: PVE_i18n_GitPatch.2025-12-19
Date: Mon, 22 Dec 2025 19:19:13 +0800 (CST)
Message-ID: <bd5365c.be28.19b45c8eadb.Coremail.kuma8866@163.com>
Dear Proxmox-i18n Team,
Hello!
I am pleased to submit my contributions to the Proxmox-i18n project, which include the following three updates:
Source Code Updates: Add gettext() to the source code to enable string extraction and translation;
Translation Entry Updates: Chinese translation entries have been thoroughly reviewed and revised in accordance with the latest project context and terminology guidelines to ensure accuracy and consistency.
zh_CN.po File Update: All translation updates have been consolidated into the zh_CN.po file, which has been locally compiled and verified to ensure there are no syntax errors.
All changes have been packaged into git patch file, attached to this email, for your review and potential merge.
Note:
Recommend using SourceTree https://sourcetreeapp.com/ to apply patches.
I am not concerned about the Contributor License Agreement, as I am not a long-term contributor to this project.
Untar：
mkdir -p "PVE_i18n_GitPatch" && tar -xf "PVE_i18n_GitPatch.2025-12-19.tar" -C "PVE_i18n_GitPatch"
Thank you for your outstanding contributions to the Proxmox community. I look forward to your feedback.
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
reply other threads:[~2025-12-23 10:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=mailman.162.1766485018.353.pve-devel@lists.proxmox.com \
--to=pve-devel@lists.proxmox.com \
--cc=kuma8866@163.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox