public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Dominik Csapak <d.csapak@proxmox.com>,
	Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Markus Frank <m.frank@proxmox.com>
Subject: Re: [pve-devel] [PATCH manager v13 5/6] add clipboard checkbox to VM Options
Date: Fri, 10 Nov 2023 11:00:25 +0100	[thread overview]
Message-ID: <5509f827-ca5b-49dc-9fe5-c9ed670b5990@proxmox.com> (raw)
In-Reply-To: <7fee6828-6da5-4d2e-bedb-9e4e451e963f@proxmox.com>

Am 10/11/2023 um 10:34 schrieb Dominik Csapak:
>> +				value: 'You cannot use the default SPICE clipboard' +
>> +				    ' if the VNC Clipboard is selected',
> 
> nit: i'd maybe like an additional sentence here that says
> the user has to install the spice-tools in the guest
> (to avoid confusion)
> 
> also maybe we should pack these warnings in gettexts
> (what is our current policy for that regarding long texts @thomas?)

The thing is: you can *never* loose with using gettext for actual text
(i.e., all but abbreviated technology terms, like VXLAN, or trade marks)

Because in the worst case nobody would going to translate it, so users
would still see the message in the original English, just as they'd if
gettext wasn't used at all.
But for a few languages we got very prolific translator, some of whom
already complained in the past about missing gettext use, so it's more
likely that these things get translated, helping users that feel more
comfortable in their native language.

So, in general, if in doubt let's use gettext, besides for the
aforementioned case, where the text consists only of abbreviations and/or
trade mark terms.




  reply	other threads:[~2023-11-10 10:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-21 11:47 [pve-devel] [PATCH qemu-sever/novnc/manager/docs v13 0/6] Feature VNC-Clipboard Markus Frank
2023-09-21 11:47 ` [pve-devel] [PATCH qemu-sever v13 1/6] enable VNC clipboard parameter in vga_fmt Markus Frank
2023-11-10  9:33   ` Dominik Csapak
2023-09-21 11:47 ` [pve-devel] [PATCH qemu-sever v13 2/6] add clipboard variable to return at status/current Markus Frank
2023-09-21 11:47 ` [pve-devel] [PATCH qemu-sever v13 3/6] test cases for clipboard spice & std Markus Frank
2023-09-21 11:47 ` [pve-devel] [PATCH novnc v13 4/6] add "show clipboard button" patch to series Markus Frank
2023-09-21 11:47 ` [pve-devel] [PATCH manager v13 5/6] add clipboard checkbox to VM Options Markus Frank
2023-11-10  9:34   ` Dominik Csapak
2023-11-10 10:00     ` Thomas Lamprecht [this message]
2023-09-21 11:47 ` [pve-devel] [PATCH docs v13 6/6] add VNC clipboard documentation Markus Frank
2023-11-10  9:34 ` [pve-devel] [PATCH qemu-sever/novnc/manager/docs v13 0/6] Feature VNC-Clipboard Dominik Csapak

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=5509f827-ca5b-49dc-9fe5-c9ed670b5990@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=d.csapak@proxmox.com \
    --cc=m.frank@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal