SymbX/systemd
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Reword sentences that contain psuedo-English "resp."

Browse Source 
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>
This commit is contained in:
Andrew Eikum
2012-10-16 01:03:01 +02:00
committed by Lennart Poettering
parent edfb521a21
commit 16dad32e43
23 changed files with 100 additions and 97 deletions
Download Patch File Download Diff File Expand all files Collapse all files
man/systemd.exec.xml
+9 -9
View File
@@ -75,7 +75,7 @@
for more information on the specific unit
configuration files. The execution specific
configuration options are configured in the [Service],
[Socket], [Mount] resp. [Swap] section, depending on the unit
[Socket], [Mount], or [Swap] sections, depending on the unit
type.</para>
</refsect1>
@@ -117,10 +117,10 @@
<term><varname>Group=</varname></term>
<listitem><para>Sets the Unix user
resp. group the processes are executed
as. Takes a single user resp. group
or group that the processes are executed
as, respectively. Takes a single user or group
name or ID as argument. If no group is
set the default group of the user is
set, the default group of the user is
chosen.</para></listitem>
</varlistentry>
@@ -868,8 +868,8 @@
the value is suffixed with K, M, G or
T the specified memory size is parsed
as Kilobytes, Megabytes, Gigabytes,
resp. Terabytes (to the base
1024). This controls the
or Terabytes (to the base
1024), respectively. This controls the
<literal>memory.limit_in_bytes</literal>
and
<literal>memory.soft_limit_in_bytes</literal>
@@ -889,9 +889,9 @@
path (such as
<filename>/dev/null</filename>)
followed by a combination of r, w, m
to control reading, writing resp.
to control reading, writing, or
creating of the specific device node
by the unit. This controls the
by the unit, respectively. This controls the
<literal>devices.allow</literal>
and
<literal>devices.deny</literal>
@@ -948,7 +948,7 @@
If the bandwidth is suffixed with K, M,
G, or T the specified bandwidth is
parsed as Kilobytes, Megabytes,
Gigabytes, resp. Terabytes (Example:
Gigabytes, or Terabytes, respectively (Example:
"/dev/disk/by-path/pci-0000:00:1f.2-scsi-0:0:0:0
5M"). This controls the
<literal>blkio.read_bps_device</literal>