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.socket.xml
+11 -11
View File
@@ -150,9 +150,9 @@
<term><varname>ListenSequentialPacket=</varname></term>
<listitem><para>Specifies an address
to listen on for a stream
(SOCK_STREAM), datagram (SOCK_DGRAM)
resp. sequential packet
(SOCK_SEQPACKET) socket. The address
(SOCK_STREAM), datagram (SOCK_DGRAM),
or sequential packet
(SOCK_SEQPACKET) socket, respectively. The address
can be written in various formats:</para>
<para>If the address starts with a
@@ -434,9 +434,9 @@
<term><varname>SendBuffer=</varname></term>
<listitem><para>Takes an integer
argument controlling the receive
resp. send buffer sizes of this
socket. This controls the SO_RCVBUF
resp. SO_SNDBUF socket options (see
or send buffer sizes of this
socket, respectively. This controls the SO_RCVBUF
and SO_SNDBUF socket options (see
<citerefentry><refentrytitle>socket</refentrytitle><manvolnum>7</manvolnum></citerefentry>
for details.).</para></listitem>
</varlistentry>
@@ -499,7 +499,7 @@
<varname>MessageQueueMessageSize=</varname></term>
<listitem><para>These two settings
take integer values and control the
mq_maxmsg resp. mq_msgsize field when
mq_maxmsg field or the mq_msgsize field, respectively, when
creating the message queue. Note that
either none or both of these variables
need to be set. See
@@ -581,9 +581,9 @@
<term><varname>ExecStartPost=</varname></term>
<listitem><para>Takes one or more
command lines, which are executed
before (resp. after) the listening
before or after the listening
sockets/FIFOs are created and
bound. The first token of the command
bound, respectively. The first token of the command
line must be an absolute file name,
then followed by arguments for the
process. Multiple command lines may be
@@ -597,9 +597,9 @@
<term><varname>ExecStopPre=</varname></term>
<term><varname>ExecStopPost=</varname></term>
<listitem><para>Additional commands
that are executed before (resp. after)
that are executed before or after
the listening sockets/FIFOs are closed
and removed. Multiple command lines
and removed, respectively. Multiple command lines
may be specified following the same
scheme as used for
<varname>ExecStartPre=</varname> of