public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Robin Roevens <robin.roevens@disroot.org>
To: development@lists.ipfire.org
Subject: Re: German translation for string
Date: Thu, 29 Sep 2022 22:23:28 +0200	[thread overview]
Message-ID: <b4335455749fb114d33f2aac20209666c53b73b4.camel@sicho.home> (raw)
In-Reply-To: <9ed09dad-579e-6389-6951-fab4d915da52@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1428 bytes --]

Hi Matthias

I don't see much difference between my sentence and yours, or at least
I mean the same with mine, but I agree that yours is probably more
clear towards the end user. So I'll go with your suggestion.

Thanks!

Robin

Matthias Fischer schreef op do 29-09-2022 om 21:49 [+0200]:
> On 29.09.2022 21:31, Robin Roevens wrote:
> > Hi all
> 
> Hi,
> 
> > I'm looking for a German translation of the string "No valid
> > runlevel
> > symlink was found for service initscript."
> 
> IMHO a more or less literal translation could be:
> 
> "Für diesen Dienst initscript wurde kein gültiger Runlevel-Symlink
> gefunden."
> 
> But since its about "Addonctrl now displays an explicit error when
> you
> try to enable/disable a service which has no runlevel symlink.", I
> would
> prefer something like:
> 
> "No valid runlevel symlink was found for the initscript of this
> service."
> 
> And:
> "Für das Initscript dieses Dienstes wurde kein gültiger Runlevel-
> Symlink
> gefunden."
> 
> jm2c
> 
> Best,
> Matthias
> 
> > which will be displayed on the services.cgi page when an addon
> > service
> > has no symlink in /etc/rc.d/rc3.d hence it can't be enabled on boot
> > by
> > using the webUI. (see also
> > https://bugzilla.ipfire.org/show_bug.cgi?id=12935#17 )
> > 
> > Thanks!
> > 
> > Robin
> > 
> 
> 

-- 
Dit bericht is gescanned op virussen en andere gevaarlijke
inhoud door MailScanner en lijkt schoon te zijn.


      reply	other threads:[~2022-09-29 20:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-29 19:31 Robin Roevens
2022-09-29 19:49 ` Matthias Fischer
2022-09-29 20:23   ` Robin Roevens [this message]

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=b4335455749fb114d33f2aac20209666c53b73b4.camel@sicho.home \
    --to=robin.roevens@disroot.org \
    --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