From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 6B35B7957B for ; Tue, 4 May 2021 14:21:11 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 5D9A89593 for ; Tue, 4 May 2021 14:20:41 +0200 (CEST) Received: from 7.mo6.mail-out.ovh.net (7.mo6.mail-out.ovh.net [46.105.59.196]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id 3919A9586 for ; Tue, 4 May 2021 14:20:40 +0200 (CEST) Received: from player159.ha.ovh.net (unknown [10.110.171.40]) by mo6.mail-out.ovh.net (Postfix) with ESMTP id 6C71425027A for ; Tue, 4 May 2021 13:44:15 +0200 (CEST) Received: from koc.pl (user-5-173-132-114.play-internet.pl [5.173.132.114]) (Authenticated sender: daniel@xn--ko-wla.pl) by player159.ha.ovh.net (Postfix) with ESMTPSA id CADE31DC77CB5 for ; Tue, 4 May 2021 11:44:14 +0000 (UTC) Authentication-Results: garm.ovh; auth=pass (GARM-102R004f14c1917-8b18-4474-a83f-6152c7725251, BF76F074E1D94FD8158D0AF2F63A084BC562C079) smtp.auth=daniel@koć.pl X-OVh-ClientIp: 5.173.132.114 From: =?UTF-8?Q?Daniel_Ko=c4=87?= To: pve-devel@lists.proxmox.com References: <01e6faf2-cb15-d021-bf50-f5606ba1909d@proxmox.com> Message-ID: Date: Tue, 4 May 2021 13:44:14 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1 MIME-Version: 1.0 In-Reply-To: <01e6faf2-cb15-d021-bf50-f5606ba1909d@proxmox.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Content-Language: pl-PL X-Ovh-Tracer-Id: 3714906746709959279 X-VR-SPAMSTATE: OK X-VR-SPAMSCORE: 0 X-VR-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgeduledrvdefiedggeehucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuqfggjfdpvefjgfevmfevgfenuceurghilhhouhhtmecuhedttdenucenucfjughrpefhuffvfhfkffgfgggjtgfgsehtkeertddtfeejnecuhfhrohhmpeffrghnihgvlhgpmfhotgcuoegurghnihgvlhesgihnqddqkhhoqdiflhgrrdhplheqnecuggftrfgrthhtvghrnhepkeeuveeggfethfekfeethffhudffueefgeeugeeujeeufeduueeugfelieeifffgnecukfhppedtrddtrddtrddtpdehrddujeefrddufedvrdduudegnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmohguvgepshhmthhpqdhouhhtpdhhvghlohepphhlrgihvghrudehledrhhgrrdhovhhhrdhnvghtpdhinhgvtheptddrtddrtddrtddpmhgrihhlfhhrohhmpegurghnihgvlhesgihnqddqkhhoqdiflhgrrdhplhdprhgtphhtthhopehpvhgvqdguvghvvghlsehlihhsthhsrdhprhhogihmohigrdgtohhm X-SPAM-LEVEL: Spam detection results: 0 AWL 0.001 Adjusted score from AWL reputation of From: address KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment NICE_REPLY_A -0.001 Looks like a legit reply (A) RCVD_IN_DNSWL_NONE -0.0001 Sender listed at https://www.dnswl.org/, no trust RCVD_IN_MSPIKE_H3 0.001 Good reputation (+3) RCVD_IN_MSPIKE_WL 0.001 Mailspike good senders SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: Re: [pve-devel] Some translation strings missing X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 May 2021 12:21:11 -0000 W dniu 04.05.2021 o 09:12, Thomas Lamprecht pisze: > Some of those are things like "OSD" or "Ceph" which cannot be translated, I don't see there is a strong dividing line. The only ones that really should not be translated are those which would create technical problems. Other than that there could be for example transliterations (like "Цэпх" or "Цэф" for Ceph in cyryllic - just like McDonald's in Russia or Bulgaria), aliases ("IP 4" instead of "IPv4") or maybe long versions etc. One never knows. On the other hand there are also some rare unneeded ones, like: #: pve-manager/www/manager6/storage/Base.js:65 msgid "1" msgstr "" #: pve-manager/www/manager6/data/ResourceStore.js:186 msgid "maxcpu" msgstr "" > Do you want to take a shot at this and send a patch? It shouldn't be > too hard, > relatively speaking. Yes, I will try that so we can move forward. It would also help me send translation changes so they can be easily applied. > The latter was not made a gettext as it's a long text, really different > from the other classic field or button label texts. It changed a few times > already, and it's way harder to review for correctness. Further, we > currently cannot detect gettext instances spanning over multiple lines, so > the parser would need adaption. > That's not saying I'd reject making it a gettext in general, just stating > the reasoning for initially not doing so. Sure, I understand that. Just some thoughts: At some point it would be good to let translators catch up with the latest changes before the release. I see no problem with rearranging text like this, but it can be "freezed" for translation in RC phase and "unfrozen" after the release. I was translating some rare big chunks of gettext before, so it exists in the real world. -- "Holy mother forking shirt balls!" [E. Shellstrop]