mirror of https://github.com/mkerrisk/man-pages
Removed trailing white space at end of lines
This commit is contained in:
parent
70ecd1c7cf
commit
91085d8525
|
@ -124,7 +124,7 @@ modules (dynamically loaded shared libraries)
|
|||
to convert to and from a character set.
|
||||
Before calling
|
||||
.BR iconv (3),
|
||||
the
|
||||
the
|
||||
.B iconv
|
||||
program must first allocate a conversion descriptor using
|
||||
.BR iconv_open (3).
|
||||
|
|
|
@ -1524,7 +1524,7 @@ On a Linux NFS server, this can be determined by looking at
|
|||
which expresses the period in seconds.
|
||||
The default value for this file is 90.)
|
||||
.\"
|
||||
.\" Jeff Layton:
|
||||
.\" Jeff Layton:
|
||||
.\" Note that this is not a firm timeout. The server runs a job
|
||||
.\" periodically to clean out expired stateful objects, and it's likely
|
||||
.\" that there is some time (maybe even up to another whole lease period)
|
||||
|
|
|
@ -1104,7 +1104,7 @@ flag, its st_ctime and st_mtime fields are set to the current time.
|
|||
.SS Open file descriptions
|
||||
The term open file description is the one used by POSIX to refer to the
|
||||
entries in the system-wide table of open files.
|
||||
In other contexts, this object is
|
||||
In other contexts, this object is
|
||||
variously also called an "open file object",
|
||||
a "file handle", an "open file table entry",
|
||||
or\(emin kernel-developer parlance\(ema
|
||||
|
@ -1119,7 +1119,7 @@ and the two file descriptors consequently share
|
|||
the file offset and file status flags.
|
||||
Such sharing can also occur between processes:
|
||||
a child process created via
|
||||
.BR fork (2)
|
||||
.BR fork (2)
|
||||
inherits duplicates of its parent's file descriptors,
|
||||
and those duplicates refer to the same open file descriptions.
|
||||
|
||||
|
|
|
@ -1806,7 +1806,7 @@ Then filesystems contained in this file are tried
|
|||
.TP
|
||||
.I /proc/fs
|
||||
.\" FIXME Much more needs to be said about /proc/fs
|
||||
.\"
|
||||
.\"
|
||||
Contains subdirectories that in turn contain files
|
||||
with information about (certain) mounted filesystems.
|
||||
.TP
|
||||
|
|
|
@ -216,7 +216,7 @@ is major 8, minor 3, so you could use 'root=0x803' as an
|
|||
alternative.)
|
||||
.TP
|
||||
.BR "'rootdelay='"
|
||||
This parameter sets the delay (in seconds) to pause before attempting
|
||||
This parameter sets the delay (in seconds) to pause before attempting
|
||||
to mount the root filesystem.
|
||||
.TP
|
||||
.BR "'rootflags=...'"
|
||||
|
|
|
@ -112,7 +112,7 @@ This is a variant of Latin-1 that replaces Icelandic letters with
|
|||
Turkish ones.
|
||||
.TP
|
||||
8859-10 (Latin-6)
|
||||
Latin-6 added the Inuit (Greenlandic) and Sami (Lappish) letters that were
|
||||
Latin-6 added the Inuit (Greenlandic) and Sami (Lappish) letters that were
|
||||
missing in Latin-4 to cover the entire Nordic area.
|
||||
.TP
|
||||
8859-11
|
||||
|
@ -265,9 +265,9 @@ In the same fashion as the ISO 8859 series, Thai characters are mapped into
|
|||
Unicode (ISO 10646) is a standard which aims to unambiguously represent
|
||||
every character in every human language.
|
||||
Unicode's structure permits 20.1 bits to encode every character.
|
||||
Since most computers don't include 20.1-bit integers, Unicode is
|
||||
usually encoded as 32-bit integers internally and either a series of
|
||||
16-bit integers (UTF-16) (needing two 16-bit integers only when
|
||||
Since most computers don't include 20.1-bit integers, Unicode is
|
||||
usually encoded as 32-bit integers internally and either a series of
|
||||
16-bit integers (UTF-16) (needing two 16-bit integers only when
|
||||
encoding certain rare characters) or a series of 8-bit bytes (UTF-8).
|
||||
.LP
|
||||
Linux represents Unicode using the 8-bit Unicode Transformation Format
|
||||
|
@ -302,9 +302,9 @@ or Greek texts, this expands ordinary text files by 100%, since text in
|
|||
those languages is mostly outside of ASCII.
|
||||
For Japanese users this means
|
||||
that the 16-bit codes now in common use will take three bytes.
|
||||
While there are algorithmic conversions from some character sets
|
||||
(especially ISO 8859-1) to Unicode, general conversion requires
|
||||
carrying around conversion tables, which can be quite large for 16-bit
|
||||
While there are algorithmic conversions from some character sets
|
||||
(especially ISO 8859-1) to Unicode, general conversion requires
|
||||
carrying around conversion tables, which can be quite large for 16-bit
|
||||
codes.
|
||||
.LP
|
||||
Note that UTF-8 is self-synchronizing: 10xxxxxx is a tail, any other
|
||||
|
@ -323,7 +323,7 @@ Rendering of Unicode data streams is typically handled through
|
|||
"subfont" tables which map a subset of Unicode to glyphs.
|
||||
Internally
|
||||
the kernel uses Unicode to describe the subfont loaded in video RAM.
|
||||
This means that in the Linux console in UTF-8 mode, one can use a character
|
||||
This means that in the Linux console in UTF-8 mode, one can use a character
|
||||
set with 512 different symbols.
|
||||
This is not enough for Japanese, Chinese, and
|
||||
Korean, but it is enough for most other purposes.
|
||||
|
|
|
@ -47,7 +47,7 @@ The
|
|||
.B iconvconfig
|
||||
program reads iconv module configuration files and writes
|
||||
a fast-loading gconv module configuration cache file.
|
||||
In addition to the system provided gconv modules, the user can specify
|
||||
In addition to the system provided gconv modules, the user can specify
|
||||
custom gconv module directories with the environment variable
|
||||
.BR GCONV_PATH .
|
||||
However, iconv module configuration caching is only used when
|
||||
|
|
Loading…
Reference in New Issue