[pve-devel] [PATCH pve-manager v2] Do not turn the strings CT and VM into separate localizable strings

According to the PO files, translators keep 'CT' and 'VM' unchanged --- change since v1: * keep CT/VM out of the gettext string, to reduce the amount of translation needed www/manager6/lxc/CmdMenu.js | 10 +- www/manager6/qemu/CmdMenu.js | 8 2 files changed, 9

[pve-devel] [PATCH pve-manager v3] Do not use the term 'VM' as a generic name for containers and qemu VMs

and get the Window text to display from the calling function --- change since v2: * use the same gettext string for CTs and VMs to reduce the amount of stuff to localize www/manager6/lxc/Config.js | 11 +-- www/manager6/qemu/Config.js| 10 --

[pve-devel] [RFC PATCH common] property strings: introduce key grouping feature

Use case: networks for kvm use a = scheme where the model represents the network card. The schema previously could not represent this, so we now introduce a 'group' key which works similar to an alias with the difference that the data structure also gets an entry named after the group filled with

[pve-devel] [RFC PATCH common] schema extension: grouped keys

The name is open for discussion I guess ;-) See the commit message for a detailed description. This is a slightly more convenient alternative to simple 'conflicts'. With 'conflicts' the user of a property string needs to figure out which keys have been used, which in the use case for which this

[pve-devel] [PATCH common] cleanup: whitespace and than/then typo

--- src/PVE/JSONSchema.pm | 87 +-- 1 file changed, 43 insertions(+), 44 deletions(-) diff --git a/src/PVE/JSONSchema.pm b/src/PVE/JSONSchema.pm index 7716ed3..426b64f 100644 --- a/src/PVE/JSONSchema.pm +++ b/src/PVE/JSONSchema.pm @@ -1028,11