public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Maximiliano Sandoval <m.sandoval@proxmox.com>
To: Kuma8866 via pve-devel <pve-devel@lists.proxmox.com>
Cc: Kuma8866 <kuma8866@163.com>
Subject: Re: [pve-devel] PVE_i18n_GitPatch.2025-12-19
Date: Tue, 30 Dec 2025 14:47:56 +0100	[thread overview]
Message-ID: <s8otsx8krn7.fsf@proxmox.com> (raw)
In-Reply-To: <mailman.162.1766485018.353.pve-devel@lists.proxmox.com> (Kuma's message of "Mon, 22 Dec 2025 19:19:13 +0800 (CST)")

Kuma8866 via pve-devel <pve-devel@lists.proxmox.com> writes:

> From: Kuma8866 <kuma8866@163.com>
> Subject: PVE_i18n_GitPatch.2025-12-19
> To: pve-devel@lists.proxmox.com
> Date: Mon, 22 Dec 2025 19:19:13 +0800 (CST) (1 week, 1 day, 2 hours ago)
>
>
>
> 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.
>
> ----------
>
> _______________________________________________
> pve-devel mailing list
> pve-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

Hello, thanks for showing interest in contributing!

At the moment, I do not see any attachment, it might be because of the
tarball format. I would recommend to take a look at our Developer
Documentation [1] for more information on how to send patches to the
mailing list.

> ‌Source Code Updates‌: Add gettext() to the source code to enable string extraction and translation;

Alternatively, you could tell me which strings (and where) are affected
and I can take a look and send a fix for this item.

> ‌zh_CN.po File Update

Alternatively, you can send the zh_CN.po file to office (at) proxmox.com as
described at our documentation [3], but note that this is also affected
by the point below.

> I am not concerned about the Contributor License Agreement, as I am
> not a long-term contributor to this project.

Please note that we can only include code/contributions licensed under
the respective repository's license, i.e. only if the contributor has
signed the CLA [2].

[1] https://pve.proxmox.com/wiki/Developer_Documentation#Sending_Patches
[2] https://pve.proxmox.com/wiki/Developer_Documentation#Software_License_and_Copyright
[3] https://pve.proxmox.com/pve-docs/pve-admin-guide.html#translation

-- 
Maximiliano


_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

      reply	other threads:[~2025-12-30 13:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-22 11:19 Kuma8866 via pve-devel
2025-12-30 13:47 ` Maximiliano Sandoval [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=s8otsx8krn7.fsf@proxmox.com \
    --to=m.sandoval@proxmox.com \
    --cc=kuma8866@163.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal