public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Shannon Sterz <s.sterz@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH manager v2 3/3] ui: prefix panel: adjust capitalization of "prefix list"
Date: Mon, 18 May 2026 15:23:47 +0200	[thread overview]
Message-ID: <20260518132347.291801-4-s.sterz@proxmox.com> (raw)
In-Reply-To: <20260518132347.291801-1-s.sterz@proxmox.com>

"prefix list" is not a proper noun and as such should follow regular
english capitalization rules. this is in-line with how frr treats this
term [1].

[1]: https://docs.frrouting.org/en/latest/filter.html#ip-prefix-list

Suggested-by: Gabriel Goller <g.goller@proxmox.com>
Signed-off-by: Shannon Sterz <s.sterz@proxmox.com>
---
 www/manager6/sdn/PrefixListPanel.js | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/www/manager6/sdn/PrefixListPanel.js b/www/manager6/sdn/PrefixListPanel.js
index 05ec3655a..f1a406acc 100644
--- a/www/manager6/sdn/PrefixListPanel.js
+++ b/www/manager6/sdn/PrefixListPanel.js
@@ -201,7 +201,7 @@ Ext.define('PVE.sdn.PrefixListEntriesView', {
     // TRANSLATORS: Refers to an FRR prefix list, some languages may prefer to
     // keep "prefix list" as-is:
     // https://docs.frrouting.org/en/latest/filter.html#ip-prefix-list
-    emptyText: gettext('Prefix List has no entries configured.'),
+    emptyText: gettext('Prefix list has no entries configured.'),
 
     config: {
         prefixList: null,
@@ -306,11 +306,11 @@ Ext.define('PVE.sdn.PrefixListPanel', {
                     // TRANSLATORS: Refers to an FRR prefix list, some
                     // languages may prefer to keep "prefix list" as-is:
                     // https://docs.frrouting.org/en/latest/filter.html#ip-prefix-list
-                    ? gettext('Prefix List has no entries configured.')
+                    ? gettext('Prefix list has no entries configured.')
                     // TRANSLATORS: Refers to an FRR prefix list, some
                     // languages may prefer to keep "prefix list" as-is:
                     // https://docs.frrouting.org/en/latest/filter.html#ip-prefix-list
-                    : gettext('no Prefix List selected');
+                    : gettext('No prefix list selected');
             },
         },
     },
-- 
2.47.3





  parent reply	other threads:[~2026-05-18 13:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-18 13:23 [PATCH manager v2 0/3] add translation notes for prefix lists and route maps; align capitalization of "prefix list" Shannon Sterz
2026-05-18 13:23 ` [PATCH manager v2 1/3] ui: add translation notes for prefix lists Shannon Sterz
2026-05-18 13:23 ` [PATCH manager v2 2/3] ui: add translation notes for route maps Shannon Sterz
2026-05-18 13:23 ` Shannon Sterz [this message]
2026-05-18 20:06 ` applied: [PATCH manager v2 0/3] add translation notes for prefix lists and route maps; align capitalization of "prefix list" 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=20260518132347.291801-4-s.sterz@proxmox.com \
    --to=s.sterz@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