From: Fiona Ebner <f.ebner@proxmox.com>
To: Dietmar Maurer <dietmar@proxmox.com>,
Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH manager] ui: node: system: avoid using 'Syslog'
Date: Fri, 16 Feb 2024 08:56:48 +0100 [thread overview]
Message-ID: <97da09f7-0843-4c60-8e34-938abc9ee1ac@proxmox.com> (raw)
In-Reply-To: <1493288684.2675.1708021251418@webmail.proxmox.com>
Am 15.02.24 um 19:20 schrieb Dietmar Maurer:
>> The information gathered by the API call comes from the systemd
>> journal. While 'Syslog' could be interpreted as a shorthand for
>> "System Log", it's better to be explicit to avoid any confusion.
>
>> - title: 'Syslog',
>> + title: gettext('System Log'),
>
> From Wikipedia: https://en.wikipedia.org/wiki/Syslog
>
>> In computing, syslog /ˈsɪslɒɡ/ is a standard for message logging.
>
> IMHO, it is a commonly used technical term, and that is why we
> do not even translate it. Every reasonable admin known what is meant!
>
> With your change:
>
> - title: 'Syslog',
> + title: gettext('System Log'),
>
> we now need to translate "System Log" to >20 different languages,
> and I am quite sure those translation makes it less clear what
> it actually refers to.
A lot of people will associate "Syslog" with /var/log/syslog which just
isn't there by default for new PVE 8 installations. I don't see how
translation would be an issue at all. It's the "System log"/"System's
log"/"Log of the system" which surely can be expressed naturally in
different languages too.
next prev parent reply other threads:[~2024-02-16 7:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-15 12:59 Fiona Ebner
2024-02-15 18:20 ` Dietmar Maurer
2024-02-15 18:25 ` Dietmar Maurer
2024-02-16 7:58 ` Fiona Ebner
2024-02-16 7:56 ` Fiona Ebner [this message]
2024-02-16 8:29 ` Fiona Ebner
2024-02-16 9:01 ` Fabian Grünbichler
2024-02-16 9:22 ` Fiona Ebner
2024-02-16 9:25 ` Dietmar Maurer
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=97da09f7-0843-4c60-8e34-938abc9ee1ac@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=dietmar@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