From: Tom Rymes <tom@rymes.net>
To: development@lists.ipfire.org
Subject: Re: [PATCH] Rename misleading "check filesystem" reboot option NL translation
Date: Fri, 18 Nov 2022 13:02:46 -0500 [thread overview]
Message-ID: <e5ded51b-e961-48eb-5e3b-c649847fe361@rymes.net> (raw)
In-Reply-To: <20221118154234.26067-1-robin.roevens@disroot.org>
[-- Attachment #1: Type: text/plain, Size: 949 bytes --]
I'm still confused by what a user might expect, OTHER than a fsck check?
On 11/18/2022 10:42 AM, Robin Roevens wrote:
> Some users assume that "check filesystem" does more than just
> trigger a simple "fsck" run. This patch changes the button label to avoid
> confusion. - NL translation
>
> Signed-off-by: Robin Roevens <robin.roevens(a)disroot.org>
> ---
> langs/nl/cgi-bin/nl.pl | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/langs/nl/cgi-bin/nl.pl b/langs/nl/cgi-bin/nl.pl
> index 4fd6955cc..ebac2754a 100644
> --- a/langs/nl/cgi-bin/nl.pl
> +++ b/langs/nl/cgi-bin/nl.pl
> @@ -1804,6 +1804,7 @@
> 'read list' => 'lijst met readonly hosts',
> 'real address' => 'Echte adressen',
> 'reboot' => 'Herstarten',
> +'reboot fsck' => 'Herstart & start ‘fsck’',
> 'reboot ask' => 'Herstarten?',
> 'reboot question' => 'Extra vraag voor herstart en afsluiten',
> 'reboot schedule' => 'Inplannen IPFire herstarts',
next prev parent reply other threads:[~2022-11-18 18:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 10:49 [PATCH] Rename misleading "check filesystem" reboot option Leo-Andres Hofmann
2022-11-18 12:07 ` Bernhard Bitsch
2022-11-18 22:44 ` Leo-Andres Hofmann
2022-11-19 0:15 ` Tom Rymes
2022-11-20 19:49 ` Robin Roevens
2022-11-21 11:16 ` Michael Tremer
2022-11-18 15:42 ` [PATCH] Rename misleading "check filesystem" reboot option NL translation Robin Roevens
2022-11-18 18:02 ` Tom Rymes [this message]
2022-11-19 11:53 ` Michael Tremer
2022-11-19 12:47 ` Leo-Andres Hofmann
2022-11-19 15:20 ` Tom Rymes
2022-11-19 16:59 ` Adolf Belka
2022-11-21 11:29 ` Michael Tremer
2022-11-21 21:46 ` Robin Roevens
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=e5ded51b-e961-48eb-5e3b-c649847fe361@rymes.net \
--to=tom@rymes.net \
--cc=development@lists.ipfire.org \
/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