diff options
| author | Andrew Eikum <aeikum@codeweavers.com> | 2012-10-15 13:59:12 -0500 |
|---|---|---|
| committer | Lennart Poettering <lennart@poettering.net> | 2012-10-16 01:03:01 +0200 |
| commit | 16dad32e437fdf2ffca03cc60a083d84bd31886f (patch) | |
| tree | 470098d66b70b7f29b3fd5cbb105a93bcea73a98 /man/journalctl.xml | |
| parent | edfb521a21c44f7b4c91d4ef6bffd84f2c241363 (diff) | |
Reword sentences that contain psuedo-English "resp."
As you likely know, Arch Linux is in the process of moving to systemd.
So I was reading through the various systemd docs and quickly became
baffled by this new abbreviation "resp.", which I've never seen before
in my English-mother-tongue life.
Some quick Googling turned up a reference:
<http://www.transblawg.eu/index.php?/archives/870-Resp.-and-other-non-existent-English-wordsNicht-existente-englische-Woerter.html>
I guess it's a literal translation of the German "Beziehungsweise", but
English doesn't work the same way. The word "respectively" is used
exclusively to provide an ordering connection between two lists. E.g.
"the prefixes k, M, and G refer to kilo-, mega-, and giga-,
respectively." It is also never abbreviated to "resp." So the sentence
"Sets the default output resp. error output for all services and
sockets" makes no sense to a natural English speaker.
This patch removes all instances of "resp." in the man pages and
replaces them with sentences which are much more clear and, hopefully,
grammatically valid. In almost all instances, it was simply replacing
"resp." with "or," which the original author (Lennart?) could probably
just do in the future.
The only other instances of "resp." are in the src/ subtree, which I
don't feel privileged to correct.
Signed-off-by: Andrew Eikum <aeikum@codeweavers.com>
Diffstat (limited to 'man/journalctl.xml')
| -rw-r--r-- | man/journalctl.xml | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/man/journalctl.xml b/man/journalctl.xml index 3786fdf514..0bbcee33ab 100644 --- a/man/journalctl.xml +++ b/man/journalctl.xml @@ -275,9 +275,9 @@ <term><option>--until=</option></term> <listitem><para>Start showing entries - newer or of the specified date, - resp. older or of the specified - date. Date specifications should be of + on or newer than the specified date, + or on or older than the specified + date, respectively. Date specifications should be of the format "2012-10-30 18:17:16". If the time part is omitted, 00:00:00 is assumed. If only the seconds component @@ -290,14 +290,14 @@ <literal>tomorrow</literal> are understood, which refer to 00:00:00 of the day before the current day, the - current day, resp the day after the - current day. <literal>now</literal> + current day, or the day after the + current day, respectively. <literal>now</literal> refers to the current time. Finally, relative times may be specified, prefixed with <literal>-</literal> or <literal>+</literal>, referring to - times before resp. after the current - time.</para></listitem> + times before or after the current + time, respectively.</para></listitem> </varlistentry> <varlistentry> |