From: Maximiliano Sandoval <m.sandoval@proxmox.com>
To: Thomas Lamprecht <t.lamprecht@proxmox.com>
Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH proxmox-i18n v2 2/2] make: add proxmox-datacenter-manager translations
Date: Fri, 21 Mar 2025 13:47:35 +0100 [thread overview]
Message-ID: <s8o4izmfs0d.fsf@proxmox.com> (raw)
In-Reply-To: <202fcecb-7ee4-4f63-aede-3d00e7352ee9@proxmox.com>
Thomas Lamprecht <t.lamprecht@proxmox.com> writes:
> btw. instead of pinging a series unconditionally a better approach might
> be to use that as an opportunity to self-test the whole series, i.e. apply
> them locally and see if all works out; that would have made most issues of
> this series visible.
> If that succeeded, then asking someone directly for an end-to-end test
> and/or review before sending the second ping or so out would also be more
> productive IMO, as a tested-by gives maintainers at least some basic
> assurance that the whole thing works in principle...
> this fails with errors like
>
> proxmox-yew-comp.pot:185: duplicate message definition...
> proxmox-widget-toolkit.pot:2081: ...this is the location of the first definition
>
> Which is a result from the former file having this combined:
>
> msgid "Warning"
> msgid_plural "Warnings"
> msgstr[0] ""
> msgstr[1] ""
>
> While the latter has it split:
>
> msgid "Warning"
> msgstr ""
>
> msgid "Warnings"
> msgstr ""
>
> There are others if this is fixed. I see no reference to other patches or steps
> we need to apply/take before this series, so what's the idea here?
The requirements are:
- https://lore.proxmox.com/pdm-devel/20250122150132.426276-1-m.sandoval@proxmox.com/
- https://lore.proxmox.com/yew-devel/20250127094651.139204-1-m.sandoval@proxmox.com/
_______________________________________________
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-03-21 13:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-24 14:37 [pve-devel] [PATCH proxmox-i18n v2 1/2] makefile: prefer using xgettext over msgcat Maximiliano Sandoval
2025-01-24 14:37 ` [pve-devel] [PATCH proxmox-i18n v2 2/2] make: add proxmox-datacenter-manager translations Maximiliano Sandoval
2025-01-30 14:16 ` Maximiliano Sandoval
2025-02-05 16:05 ` Maximiliano Sandoval
2025-02-11 13:00 ` Maximiliano Sandoval
2025-02-18 11:56 ` Maximiliano Sandoval
2025-02-25 15:12 ` Maximiliano Sandoval
2025-03-19 8:33 ` Maximiliano Sandoval
2025-02-25 15:33 ` Shannon Sterz
2025-02-25 15:48 ` Maximiliano Sandoval
2025-03-21 12:40 ` Thomas Lamprecht
2025-03-21 12:47 ` Maximiliano Sandoval [this message]
2025-03-21 12:36 ` [pve-devel] [PATCH proxmox-i18n v2 1/2] makefile: prefer using xgettext over msgcat Thomas Lamprecht
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=s8o4izmfs0d.fsf@proxmox.com \
--to=m.sandoval@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=t.lamprecht@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