util-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Benno Schulenberg <bensberg@justemail.net>
To: JWP <elseifthen@gmx.com>
Cc: Karel Zak <kzak@redhat.com>, "Util-Linux" <util-linux@vger.kernel.org>
Subject: Re: [PATCH 3/4] hwclock: update man page for v2.26 rc
Date: Sun, 11 Jan 2015 12:44:35 +0100	[thread overview]
Message-ID: <1420976675.3854707.212394769.57AD68B2@webmail.messagingengine.com> (raw)
In-Reply-To: <54B16A8A.3090605@gmx.com>


On Sat, Jan 10, 2015, at 19:08, JWP wrote:
> I agree we do not want full
> changelogs in files. My thinking in this particular case was, that there
> has not been a significant update to this man-page in a couple of decades

Hmm...  Looking at 'git log -p -w --follow sys-utils/hwclock.8.in', the
first version of the man page dates from 1996.  Before 1998 there was a
substantial addition (Alpha stuff) and again for version 2.9i (unfortunately
undated).

BTW, Karel, where are the older versions of util-linux stored
(the ones before 2.13)?  I can't find them on kernel.org, but did find them
on http://ftp.europeonline.com/pub/linux/utils/util-linux/ .

(Also BTW, Karel, where has the homepage of util-linux gone?
It is no longer http://userweb.kernel.org/~kzak/util-linux/ .)

> Also, since I authored some completely new content I was thinking of any
> copyright/copyleft issues; although I did not actually claim any.

Ah!  Probably you should claim copyright.  Davidlohr Bueso did this,
for example, for a substantial addition to partx.  So I would suggest
that, instead of the changelog item, you add the following two lines
to the man page header:

Copyright 1996 Bryan Henderson <bryanh@giraffe-data.com>
Copyright 2015 J. William Piggott <elseifthen@gmx.com>

And if you find out who wrote the other substantial additions, you
could add copyright lines for them too.

(No need to specify which part of the page your copyright applies to,
that is what git is for.)

> Before adding this I checked other utli-linux man-pages and some of them
> have extensive top comments. Including some changelogs,

Well, the extensive top comments are for the most part just verbose
licenses.  The only two changelogs I see are in fstab.5 and swapon.8,
and those things are entirely obsolete.  The recent top comments are
added because they are about recent commands or substantial additions,
and they are just copyright lines, not changelogs.

> I did not think this new hwclock would be used in DEC
> Alpha's either, but it is. Despite its name, I have read that util-
> linux is used elsewhere. BSD comes to mind.

But if this modern hwclock is used, wouldn't the rest of the system
be modern too?  That is: have up-to-date man macros?

> > s/none are/none is/
> > because at most one may be given.
> 
> But there are multiple choices and 'none' is plural.

No, "none" isn't always plural.  :)
http://www.quickanddirtytips.com/education/grammar/none-or-none-are

> So, what I do not understand is why translation
> software would flag a text line for changes in whitespace, punctuation,
> formatting structure like line-breaks, or non-printing characters.

Whitespace might be used to line things up neatly, and gettext has
no way of knowing when this change is relevant or not, so it must
flag each and every change.

> I 
> understand punctuation can change the meaning, but it seems unlikely that
> it would impact the translation, assuming the translator parsed out the 
> intended meaning the first time.

Huh?  If the meaning of a string changes, surely the translation
will be different too...  Aah!  You mean: the translator translated
the string correctly even though it had faulty punctuation or tabbing
or spelling or something similar.  Ah, but you can't be sure of that.
So, the minutest change in a string must invalidate its translation.

Benno

-- 
http://www.fastmail.com - The way an email service should be


  reply	other threads:[~2015-01-11 11:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-08  4:10 [PATCH 0/4] hwclock: x86_64 -- UTC Defaults -- v2.26 man updates JWP
2015-01-08  4:13 ` [PATCH 1/4] hwclock: enable --directisa for x86_64 JWP
2015-01-09  9:51   ` Karel Zak
2015-01-08  4:15 ` [PATCH 2/4] hwclock: Incorrect UTC defaults JWP
2015-01-08  4:18 ` [PATCH 3/4] hwclock: update man page for v2.26 rc JWP
2015-01-10 12:44   ` Benno Schulenberg
2015-01-10 18:08     ` JWP
2015-01-11 11:44       ` Benno Schulenberg [this message]
2015-01-11 18:59         ` JWP
2015-01-12  9:37         ` Karel Zak
2015-01-08  4:22 ` [PATCH 4/4] hwclock: man page 'Since v2.26' notes JWP

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=1420976675.3854707.212394769.57AD68B2@webmail.messagingengine.com \
    --to=bensberg@justemail.net \
    --cc=elseifthen@gmx.com \
    --cc=kzak@redhat.com \
    --cc=util-linux@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).