public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: Seth David Schoen <schoen@loyalty.org>,
	Helge Kreutzmann <debian@helgefjell.de>
Cc: mario.blaettermann@gmail.com, linux-man@vger.kernel.org
Subject: Re: Dear linux man-pages maintainer,
Date: Sun, 12 Mar 2023 00:29:45 +0100	[thread overview]
Message-ID: <5f55b64b-0cdf-6a2f-3af8-b9dd9e8ff070@gmail.com> (raw)
In-Reply-To: <20230311185634.GA441010@demorgan>


[-- Attachment #1.1: Type: text/plain, Size: 1220 bytes --]

Hi Seth, Helge,

On 3/11/23 19:56, Seth David Schoen wrote:
> Hi Helge,
> 
> I am not the maintainer or anything, but I think it's great that
> translators give feedback on the original text.
> 
> I have two disagreements with your changes:
> 
> (1) You proposed correcting "null byte" to "NUL byte".  However, "null
> byte" is a standard way to refer to a byte with the numerical value of
> zero.  This byte is also the same as the ASCII character NUL; it could
> be regarded as the "encoding" of that character.

Agree.

> 
> (2) You proposed correcting "runlevel" to "run level".  The word
> "runlevel" is a coinage by operating system developers; in ordinary
> English it would indeed have to be two words, but it's common to write
> it with no space in this context.

About this, in the Linux man-pages we tend to favor correct English,
and not words like runlevel or userspace.  So, when it is a noun it
is run level, and when it's an adjective, it's run-level.  I'll have
a look at it, and see what needs fixing.

Cheers,

Alex

> 
> https://en.wikipedia.org/wiki/Runlevel

-- 
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2023-03-11 23:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-11 17:13 Dear linux man-pages maintainer, Helge Kreutzmann
2023-03-11 18:56 ` Seth David Schoen
2023-03-11 19:51   ` Helge Kreutzmann
2023-03-11 23:29   ` Alejandro Colomar [this message]
2023-03-11 23:38     ` Alejandro Colomar
2023-03-12  5:20     ` Helge Kreutzmann
2023-03-12  5:47       ` Seth David Schoen
2023-03-12  6:02         ` Helge Kreutzmann
2023-03-12 11:05           ` Alejandro Colomar

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=5f55b64b-0cdf-6a2f-3af8-b9dd9e8ff070@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=debian@helgefjell.de \
    --cc=linux-man@vger.kernel.org \
    --cc=mario.blaettermann@gmail.com \
    --cc=schoen@loyalty.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