diff options
| author | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2016-12-11 17:01:07 -0500 |
|---|---|---|
| committer | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2016-12-11 17:13:19 -0500 |
| commit | 1eecafb8c1b737d0139cac9098239c80ad16806d (patch) | |
| tree | 291459dbed196e0d1f7733c49197042609ef81e4 /man/sd_notify.xml | |
| parent | 15ffcc3456e054c0f9fd293afe449fed292b5d38 (diff) | |
man: use unicode ellipsis in more places
As requested in
https://github.com/systemd/systemd/pull/4864#pullrequestreview-12372557.
docbook will substitute triple dots for the ellipsis in man output, so this has
no effect on the troff output, only on HTML, making it infinitesimally nicer.
In some places we show output from programs, which use dots, and those places
should not be changed. In some tables, the alignment would change if dots were
changed to the ellipsis which is only one character. Since docbook replaces the
ellipsis automatically, we should leave those be. This patch changes all other
places.
Diffstat (limited to 'man/sd_notify.xml')
| -rw-r--r-- | man/sd_notify.xml | 20 |
1 files changed, 10 insertions, 10 deletions
diff --git a/man/sd_notify.xml b/man/sd_notify.xml index 94542b80b8..6e98041912 100644 --- a/man/sd_notify.xml +++ b/man/sd_notify.xml @@ -66,7 +66,7 @@ <funcdef>int <function>sd_notifyf</function></funcdef> <paramdef>int <parameter>unset_environment</parameter></paramdef> <paramdef>const char *<parameter>format</parameter></paramdef> - <paramdef>...</paramdef> + <paramdef>…</paramdef> </funcprototype> <funcprototype> @@ -81,7 +81,7 @@ <paramdef>pid_t <parameter>pid</parameter></paramdef> <paramdef>int <parameter>unset_environment</parameter></paramdef> <paramdef>const char *<parameter>format</parameter></paramdef> - <paramdef>...</paramdef> + <paramdef>…</paramdef> </funcprototype> <funcprototype> @@ -152,7 +152,7 @@ </varlistentry> <varlistentry> - <term>STATUS=...</term> + <term>STATUS=…</term> <listitem><para>Passes a single-line UTF-8 status string back to the service manager that describes the service state. This @@ -160,11 +160,11 @@ state feedback, fsck-like programs could pass completion percentages and failing programs could pass a human-readable error message. Example: <literal>STATUS=Completed 66% of file - system check...</literal></para></listitem> + system check…</literal></para></listitem> </varlistentry> <varlistentry> - <term>ERRNO=...</term> + <term>ERRNO=…</term> <listitem><para>If a service fails, the errno-style error code, formatted as string. Example: <literal>ERRNO=2</literal> @@ -172,7 +172,7 @@ </varlistentry> <varlistentry> - <term>BUSERROR=...</term> + <term>BUSERROR=…</term> <listitem><para>If a service fails, the D-Bus error-style error code. Example: @@ -180,7 +180,7 @@ </varlistentry> <varlistentry> - <term>MAINPID=...</term> + <term>MAINPID=…</term> <listitem><para>The main process ID (PID) of the service, in case the service manager did not fork off the process itself. @@ -227,7 +227,7 @@ </varlistentry> <varlistentry> - <term>FDNAME=...</term> + <term>FDNAME=…</term> <listitem><para>When used in combination with <varname>FDSTORE=1</varname>, specifies a name for the @@ -248,7 +248,7 @@ </varlistentry> <varlistentry> - <term>WATCHDOG_USEC=...</term> + <term>WATCHDOG_USEC=…</term> <listitem><para>Reset <varname>watchdog_usec</varname> value during runtime. Notice that this is not available when using <function>sd_event_set_watchdog()</function> @@ -362,7 +362,7 @@ initialization:</para> <programlisting>sd_notifyf(0, "READY=1\n" - "STATUS=Processing requests...\n" + "STATUS=Processing requests…\n" "MAINPID=%lu", (unsigned long) getpid());</programlisting> </example> |