[PATCH 09/20] signal.2, utf-8.7: srcfix

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Use `IP` macro instead of `TP` for paragraph tags with no semantic
value.

Signed-off-by: G. Branden Robinson <g.branden.robinson@xxxxxxxxx>
---
 man2/signal.2 |  9 +++------
 man7/utf-8.7  | 21 +++++++--------------
 2 files changed, 10 insertions(+), 20 deletions(-)

diff --git a/man2/signal.2 b/man2/signal.2
index b21abc3b8..63b81e50f 100644
--- a/man2/signal.2
+++ b/man2/signal.2
@@ -51,20 +51,17 @@ or the address of a programmer-defined function (a "signal handler").
 If the signal
 .I signum
 is delivered to the process, then one of the following happens:
-.TP 3
-*
+.IP * 3
 If the disposition is set to
 .BR SIG_IGN ,
 then the signal is ignored.
-.TP
-*
+.IP *
 If the disposition is set to
 .BR SIG_DFL ,
 then the default action associated with the signal (see
 .BR signal (7))
 occurs.
-.TP
-*
+.IP *
 If the disposition is set to a function,
 then first either the disposition is reset to
 .BR SIG_DFL ,
diff --git a/man7/utf-8.7 b/man7/utf-8.7
index 5ff634306..0b9a1493f 100644
--- a/man7/utf-8.7
+++ b/man7/utf-8.7
@@ -33,8 +33,7 @@ does not have these problems and is the common way in which
 Unicode is used on UNIX-style operating systems.
 .SS Properties
 The UTF-8 encoding has the following nice properties:
-.TP 0.2i
-*
+.IP * 0.2i
 UCS
 characters 0x00000000 to 0x0000007f (the classic US-ASCII
 characters) are encoded simply as bytes 0x00 to 0x7f (ASCII
@@ -44,23 +43,18 @@ This means that files and strings which contain only
 ASCII
 and
 UTF-8 .
-.TP
-*
+.IP *
 All UCS characters greater than 0x7f are encoded as a multibyte sequence
 consisting only of bytes in the range 0x80 to 0xfd, so no ASCII
 byte can appear as part of another character and there are no
 problems with, for example,  \[aq]\e0\[aq] or \[aq]/\[aq].
-.TP
-*
+.IP *
 The lexicographic sorting order of UCS-4 strings is preserved.
-.TP
-*
+.IP *
 All possible 2\[ha]31 UCS codes can be encoded using UTF-8.
-.TP
-*
+.IP *
 The bytes 0xc0, 0xc1, 0xfe, and 0xff are never used in the UTF-8 encoding.
-.TP
-*
+.IP *
 The first byte of a multibyte sequence which represents a single non-ASCII
 UCS character is always in the range 0xc2 to 0xfd and indicates how long
 this multibyte sequence is.
@@ -68,8 +62,7 @@ All further bytes in a multibyte sequence
 are in the range 0x80 to 0xbf.
 This allows easy resynchronization and
 makes the encoding stateless and robust against missing bytes.
-.TP
-*
+.IP *
 UTF-8 encoded UCS characters may be up to six bytes long, however the
 Unicode standard specifies no characters above 0x10ffff, so Unicode characters
 can be only up to four bytes long in
-- 
2.30.2

Attachment: signature.asc
Description: PGP signature


[Index of Archives]     [Kernel Documentation]     [Netdev]     [Linux Ethernet Bridging]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux