From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] [PATCH proxmox-i18n] update Japanese translations
Date: Thu, 6 Nov 2025 19:37:15 +0100 [thread overview]
Message-ID: <176245423463.2416770.17496877353840658005.b4-ty@proxmox.com> (raw)
In-Reply-To: <mailman.404.1761819945.362.pve-devel@lists.proxmox.com>
On Thu, 30 Oct 2025 11:08:41 +0900, ribbon--- via pve-devel wrote:
> This is patch for ja.po (bump version 3.6.1)
>
> --- ja.po 2025-10-28 10:48:57.420284755 +0900
> +++ jan.po 2025-10-30 10:41:53.656519167 +0900
^- the patch got broken here on preparation or send due to the `n` sneaking in
into the file name.
> @@ -8,7 +8,7 @@
> "Project-Id-Version: proxmox translations\n"
> "Report-Msgid-Bugs-To: <support@proxmox.com>\n"
> "POT-Creation-Date: 2025-09-29 18:08+0200\n"
> -"PO-Revision-Date: 2025-03-20 23:21+0900\n"
> +"PO-Revision-Date: 2025-10-30 10:41+0900\n"
> "Last-Translator: ribbon <ribbon@users.osdn.me>\n"
> "Language-Team: Japanese <kde-i18n-doc@kde.org>\n"
> "Language: ja\n"
> @@ -23,16 +23,17 @@
> #: proxmox-backup/www/tape/window/TapeBackup.js:129
> #: proxmox-backup/www/tape/window/TapeBackupJob.js:184
> msgid "# of Worker Threads"
> -msgstr ""
> +msgstr "# のワーカスレッド"
>
> [...]
With the filename fixed up manually: Applied, thanks!
[1/1] update Japanese translations
commit: 4765b09b4949aa1aa6f16519ff577cd8a8beec52
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-11-06 18:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 2:08 ribbon--- via pve-devel
2025-11-06 13:25 ` ribbon via pve-devel
2025-11-06 18:37 ` Thomas Lamprecht [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-05-30 11:23 ribbon--- via pve-devel
2025-04-08 9:59 ribbon via pve-devel
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=176245423463.2416770.17496877353840658005.b4-ty@proxmox.com \
--to=t.lamprecht@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox