summaryrefslogtreecommitdiff
path: root/usr/src/man/man5
diff options
context:
space:
mode:
Diffstat (limited to 'usr/src/man/man5')
-rw-r--r--usr/src/man/man5/condition.520
-rw-r--r--usr/src/man/man5/epoll.56
-rw-r--r--usr/src/man/man5/filesystem.517
-rw-r--r--usr/src/man/man5/lf64.538
-rw-r--r--usr/src/man/man5/locale.548
5 files changed, 39 insertions, 90 deletions
diff --git a/usr/src/man/man5/condition.5 b/usr/src/man/man5/condition.5
index 5ebaf3ef50..1282ea26e8 100644
--- a/usr/src/man/man5/condition.5
+++ b/usr/src/man/man5/condition.5
@@ -44,12 +44,10 @@
.\" Copyright (c) 1998 Sun Microsystems, Inc. All Rights Reserved.
.\" Copyright (c) 2001, The IEEE and The Open Group. All Rights Reserved.
.\"
-.TH CONDITION 5 "Jul 20, 1998"
+.TH CONDITION 5 "May 16, 2020"
.SH NAME
condition \- concepts related to condition variables
.SH DESCRIPTION
-.sp
-.LP
Occasionally, a thread running within a mutex needs to wait for an event, in
which case it blocks or sleeps. When a thread is waiting for another thread to
communicate its disposition, it uses a condition variable in conjunction with a
@@ -68,8 +66,6 @@ If another thread changes the condition, it may wake up waiting threads by
signaling the associated condition variable. The waiting threads, upon
awakening, reacquire the mutex and re-evaluate the condition.
.SS "Initialize"
-.sp
-.LP
Condition variables and mutexes should be global. Condition variables that are
allocated in writable memory can synchronize threads among processes if they
are shared by the cooperating processes (see \fBmmap\fR(2)) and are initialized
@@ -99,26 +95,18 @@ initialization of the condition variable. Solaris condition variables also
implement as the default, intra-process; however, they set this attribute
according to the argument, \fItype\fR, passed to their initialization function.
.SS "Condition Wait"
-.sp
-.LP
The condition wait interface allows a thread to wait for a condition and
atomically release the associated mutex that it needs to hold to check the
condition. The thread waits for another thread to make the condition true and
that thread's resulting call to signal and wakeup the waiting thread.
.SS "Condition Signaling"
-.sp
-.LP
A condition signal allows a thread to unblock the next thread waiting on the
condition variable, whereas, a condition broadcast allows a thread to unblock
all threads waiting on the condition variable.
.SS "Destroy"
-.sp
-.LP
The condition destroy functions destroy any state, but not the space,
associated with the condition variable.
.SH ATTRIBUTES
-.sp
-.LP
See \fBattributes\fR(5) for descriptions of the following attributes:
.sp
@@ -133,8 +121,6 @@ MT-Level MT-Safe
.TE
.SH SEE ALSO
-.sp
-.LP
\fBfork\fR(2), \fBmmap\fR(2), \fBsetitimer\fR(2), \fBshmop\fR(2),
\fBcond_broadcast\fR(3C), \fBcond_destroy\fR(3C), \fBcond_init\fR(3C),
\fBcond_signal\fR(3C), \fBcond_timedwait\fR(3C), \fBcond_wait\fR(3C),
@@ -144,13 +130,11 @@ MT-Level MT-Safe
\fBpthread_condattr_init\fR(3C), \fBsignal\fR(3C), \fBattributes\fR(5),
\fBmutex\fR(5), \fBstandards\fR(5)
.SH NOTES
-.sp
-.LP
If more than one thread is blocked on a condition variable, the order in which
threads are unblocked is determined by the scheduling policy.
.sp
.LP
-\fBUSYNC_THREAD\fR does not support multiple mapplings to the same logical
+\fBUSYNC_THREAD\fR does not support multiple mappings to the same logical
synch object. If you need to \fBmmap()\fR a synch object to different locations
within the same address space, then the synch object should be initialized as a
shared object \fBUSYNC_PROCESS\fR for Solaris, and
diff --git a/usr/src/man/man5/epoll.5 b/usr/src/man/man5/epoll.5
index 1cf5d39947..2e64991cbf 100644
--- a/usr/src/man/man5/epoll.5
+++ b/usr/src/man/man5/epoll.5
@@ -8,7 +8,7 @@
.\" A full copy of the text of the CDDL should have accompanied this
.\" source. A copy of the CDDL is also available via the Internet at
.\" http://www.illumos.org/license/CDDL.
-.TH EPOLL 5 "Apr 17, 2014"
+.TH EPOLL 5 "May 16, 2020"
.SH NAME
epoll \- Linux-compatible I/O event notification facility
.SH SYNOPSIS
@@ -28,7 +28,7 @@ the Linux facility, including the following interfaces:
.ie t \(bu
.el o
\fBepoll_create\fR(3C) creates an \fBepoll\fR instance, returning a file
-descriptor. It contains a size arugment which is meaningful only in as
+descriptor. It contains a size argument which is meaningful only in as
much as it cannot be 0.
.RE
.RS +4
@@ -59,7 +59,7 @@ via \fBepoll_ctl\fR(3C), blocking the caller if no such events are pending.
.TP
.ie t \(bu
.el o
-\fBepoll_pwait\fR(3C) opeates in a similar manner to \fBepoll_wait\fR(3C), but
+\fBepoll_pwait\fR(3C) operates in a similar manner to \fBepoll_wait\fR(3C), but
allows the caller to specify a signal mask to be set atomically with respect
to waiting for events.
.RE
diff --git a/usr/src/man/man5/filesystem.5 b/usr/src/man/man5/filesystem.5
index f0420111c4..8b4cd14157 100644
--- a/usr/src/man/man5/filesystem.5
+++ b/usr/src/man/man5/filesystem.5
@@ -20,11 +20,10 @@
.\" Copyright 2016 Nexenta Systems, Inc.
.\" Copyright 2017 Peter Tribble
.\"
-.TH FILESYSTEM 5 "Nov 26, 2017"
+.TH FILESYSTEM 5 "Apr 15, 2020"
.SH NAME
filesystem \- File system organization
.SH SYNOPSIS
-.LP
.nf
/
.fi
@@ -35,7 +34,6 @@ filesystem \- File system organization
.fi
.SH DESCRIPTION
-.LP
The file system tree is organized for administrative convenience. Distinct
areas within the file system tree are provided for files that are private to
one machine, files that can be shared by multiple machines of a common
@@ -85,7 +83,6 @@ the \fBplatform-specific\fR file is installed only on a subset of supported
platforms. Most platform-specific files are gathered under \fB/platform\fR and
\fB/usr/platform\fR.
.SS "Root File System"
-.LP
The root file system contains files that are unique to each machine. It
contains the following directories:
.sp
@@ -1544,7 +1541,6 @@ Databases used by \fBNIS\fR and \fBypbind\fR(1M).
.RE
.SS "\fB/usr\fR File System"
-.LP
Because it is desirable to keep the root file system small and not volatile, on
disk-based systems larger file systems are often mounted on \fB/home\fR,
\fB/opt\fR, \fB/usr\fR, and \fB/var\fR.
@@ -1566,16 +1562,6 @@ The \fB/usr\fR file system contains the following subdirectories:
.sp
.ne 2
.na
-\fB\fB/usr/4lib\fR\fR
-.ad
-.sp .6
-.RS 4n
-\fBa.out\fR libraries for the Binary Compatibility Package.
-.RE
-
-.sp
-.ne 2
-.na
\fB\fB/usr/5bin\fR\fR
.ad
.sp .6
@@ -2951,7 +2937,6 @@ Directory for newer versions of POSIX-compliant utilities.
.RE
.SH SEE ALSO
-.LP
\fBat\fR(1), \fBex\fR(1), \fBiconv\fR(1), \fBlp\fR(1),
\fBisainfo\fR(1), \fBmail\fR(1), \fBmailx\fR(1), \fBnroff\fR(1),
\fBpriocntl\fR(1), \fBrefer\fR(1), \fBsar\fR(1), \fBsh\fR(1), \fBspell\fR(1),
diff --git a/usr/src/man/man5/lf64.5 b/usr/src/man/man5/lf64.5
index f1be4e3d83..f2c59d78a6 100644
--- a/usr/src/man/man5/lf64.5
+++ b/usr/src/man/man5/lf64.5
@@ -4,11 +4,10 @@
.\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
.\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
.\" Copyright (c) 2015, Joyent, Inc. All rights reserved.
-.TH LF64 5 "Jan 14, 2015"
+.TH LF64 5 "May 17, 2020"
.SH NAME
lf64 \- transitional interfaces for 64-bit file offsets
.SH DESCRIPTION
-.LP
The data types, interfaces, and macros described on this page provide explicit
access to 64-bit file offsets. They are accessible through the transitional
compilation environment described on the \fBlfcompile64\fR(5) manual page. The
@@ -16,7 +15,6 @@ function prototype and semantics of a transitional interface are equivalent to
those of the standard version of the call, except that relevant data types are
64-bit entities.
.SS "Data Types"
-.LP
The following tables list the standard data or struct types in the left-hand
column and their corresponding explicit 64-bit file offset types in the
right-hand column, grouped by header. The absence of an entry in the left-hand
@@ -99,7 +97,7 @@ l l .
struct \fBstatvfs\fR struct \fBstatvfs64\fR
\fBfsblkcnt_t\fR f_blocks; \fBfsblkcnt64_t\fR f_blocks;
\fBfsblkcnt_t\fR f_bfree; \fBfsblkcnt64_t\fR f_bfree;
- \fBfsblkcnt_t\fR f_bavial; \fBfsblkcnt64_t\fR f_bavial;
+ \fBfsblkcnt_t\fR f_bavail; \fBfsblkcnt64_t\fR f_bavail;
\fBfsfilcnt_t\fR f_files; \fBfsfilcnt64_t\fR f_files;
\fBfsfilcnt_t\fR f_ffree; \fBfsfilcnt64_t\fR f_ffree;
\fBfsfilcnt_t\fR f_favail; \fBfsfilcnt64_t\fR f_favail;
@@ -138,7 +136,6 @@ l l .
.TE
.SS "System Interfaces"
-.LP
The following tables display the standard API and the corresponding
transitional interfaces for 64-bit file offsets. The interfaces are grouped by
header. The interface name and the affected data types are displayed in courier
@@ -148,11 +145,11 @@ font.
.TS
l l
l l .
-int \fBaio_cancel\fR(..., int \fBaio_cancel64\fR(...,
+int \fBaio_cancel\fR(..., int \fBaio_cancel64\fR(...,
struct \fBaiocb\fR *); struct \fBaiocb64\fR *);
int \fBaio_error\fR( int \fBaio_error64\fR(
const struct \fBaiocb\fR *); const struct \fBaiocb64\fR *);
-int \fBaio_fsync\fR(..., int \fBaio_fsync64\fR(...,
+int \fBaio_fsync\fR(..., int \fBaio_fsync64\fR(...,
struct \fBaiocb\fR *); struct \fBaiocb64\fR *);
int \fBaio_read\fR(struct \fBaiocb\fR *); int \fBaio_read64\fR(struct \fBaiocb64\fR *);
int \fBaio_return\fR(struct \fBaiocb\fR *); int \fBaio_return64\fR(struct \fBaiocb64\fR *);
@@ -161,7 +158,7 @@ int \fBaio_suspend\fR( int \fBaio_suspend64\fR(
int \fBaio_waitn\fR(aiocb_t *[], int \fBaio_waitn64\fR(aiocb64_t *[],
...); ...);
int \fBaio_write\fR(struct \fBaiocb\fR *); int \fBaio_write64\fR(struct \fBaiocb64\fR *);
-int \fBlio_listio\fR(..., int \fBlio_listio64\fR(...,
+int \fBlio_listio\fR(..., int \fBlio_listio64\fR(...,
const struct \fBaiocb\fR *, ...); const struct \fBaiocb64\fR *, ...);
.TE
@@ -171,12 +168,12 @@ int \fBlio_listio\fR(..., int \fBlio_listio64\fR(...,
l l
l l .
int \fBalphasort\fR( int \fBalphasort64\fR(
- const struct dirent **, const struct dirent64 **,
+ const struct dirent **, const struct dirent64 **,
const struct dirent **) const struct dirent64 **)
struct \fBdirent *\fR\fBreaddir()\fR; struct \fBdirent64 *\fR\fBreaddir64()\fR;
struct \fBdirent *\fR\fBreaddir_r()\fR; struct \fBdirent64 *\fR\fBreaddir64_r()\fR;
-int \fBscandir\fR(..., int \fBscandir64\fR(...,
- struct dirent *(*[]), struct dirent64 *(*[]),
+int \fBscandir\fR(..., int \fBscandir64\fR(...,
+ struct dirent *(*[]), struct dirent64 *(*[]),
int (*)(const struct dirent *), int (*)(const struct dirent64 *),
int (*)(const struct dirent **, int (*)(const struct dirent64 **,
const struct dirent **)) const struct dirent64 **))
@@ -202,10 +199,10 @@ l l
l l .
int \fBftw\fR(..., int \fBftw64\fR(...,
const struct \fBstat\fR *, ...); const struct \fBstat64\fR *, ...);
-
+
int \fBnftw\fR(.. int \fBnftw64\fR(...,
const struct \fBstat\fR *, ...); const struct \fBstat64\fR *, ...);
-
+
.TE
.SS "<\fBlibgen.h\fR>"
@@ -252,7 +249,7 @@ int \fBaiowrite\fR(..., \fBoff_t\fR, ...); int \fBaiowrite64\fR(..., \fBoff64_t\
l l
l l .
int \fBgetdents\fR(..., \fBdirent\fR); int \fBgetdents64\fR(..., \fBdirent64\fR);
-
+
.TE
.SS "<\fBsys/mman.h\fR>"
@@ -278,11 +275,11 @@ int \fBsetrlimit\fR(..., int \fBsetrlimit64\fR(...,
.TS
l l
l l .
-ssize_t \fBsendfile\fR(..., ssize_t \fBsendfile64\fR(...,
+ssize_t \fBsendfile\fR(..., ssize_t \fBsendfile64\fR(...,
\fBoff_t\fR *, ...); \fBoff64_t\fR *, ...);
-ssize_t \fBsendfilev\fR(..., const ssize_t \fBsendfilev64\fR(..., const
+ssize_t \fBsendfilev\fR(..., const ssize_t \fBsendfilev64\fR(..., const
struct \fBsendfilevec\fR *, ...); struct \fBsendfilevec64\fR *, ...);
-
+
.TE
.SS "<\fBsys/stat.h\fR>"
@@ -291,7 +288,7 @@ ssize_t \fBsendfilev\fR(..., const ssize_t \fBsendfilev64\fR(..., const
l l
l l .
int \fBfstat\fR(..., struct \fBstat\fR *); int \fBfstat64\fR(..., struct \fBstat64\fR *);
-int \fBfstatat\fR(..., int \fBfstatat64\fR(...,
+int \fBfstatat\fR(..., int \fBfstatat64\fR(...,
struct \fBstat\fR *, int); struct \fBstat64\fR *, int);
int \fBlstat\fR(..., struct \fBstat\fR *); int \fBlstat64\fR(..., struct \fBstat64\fR *);
int \fBstat\fR(..., struct \fBstat\fR *); int \fBstat64\fR(..., struct \fBstat64\fR *);
@@ -304,7 +301,7 @@ l l
l l .
int \fBstatvfs\fR(..., int \fBstatvfs64\fR(...,
struct \fBstatvfs\fR *); struct \fBstatvfs64\fR *);
-int \fBfstatvfs\fR(..., int \fBfstatvfs64\fR(...,
+int \fBfstatvfs\fR(..., int \fBfstatvfs64\fR(...,
struct \fBstatvfs\fR *); struct \fBstatvfs64\fR *);
.TE
@@ -328,7 +325,7 @@ int \fBalphasort\fR( int \fBalphasort64\fR(
struct \fBdirect *\fR\fBreaddir()\fR; struct \fBdirect64 *\fR\fBreaddir64()\fR;
int \fBscandir\fR(..., int \fBscandir64\fR(...,
struct \fBdirect\fR *(*[]);, ...); struct \fBdirect64\fR *(*[]);, ...);
-
+
.TE
.SS "<\fBunistd.h\fR>"
@@ -347,5 +344,4 @@ int \fBtruncate\fR(..., \fBoff_t\fR); int \fBtruncate64\fR(..., \fBoff64_t\fR);
.TE
.SH SEE ALSO
-.LP
\fBlfcompile\fR(5), \fBlfcompile64\fR(5)
diff --git a/usr/src/man/man5/locale.5 b/usr/src/man/man5/locale.5
index dd8d3ba858..e6d63073aa 100644
--- a/usr/src/man/man5/locale.5
+++ b/usr/src/man/man5/locale.5
@@ -43,12 +43,11 @@
.\" Copyright (c) 1992, X/Open Company Limited. All Rights Reserved.
.\" Portions Copyright (c) 2003, Sun Microsystems, Inc. All Rights Reserved.
.\"
-.TH LOCALE 5 "April 9, 2016"
+.TH LOCALE 5 "May 16, 2020"
.SH NAME
locale \- subset of a user's environment that depends on language and cultural
conventions
.SH DESCRIPTION
-.LP
A \fBlocale\fR is the definition of the subset of a user's environment that
depends on language and cultural conventions. It is made up from one or more
categories. Each category is identified by its name and controls specific
@@ -139,7 +138,6 @@ the value of the corresponding environment variable is used. If the environment
variable is unset or is set to the empty string, the \fBsetlocale()\fR
function sets the appropriate environment.
.SS "Locale Definition"
-.LP
Locales can be described with the file format accepted by the \fBlocaledef\fR
utility.
.sp
@@ -341,7 +339,6 @@ decimal or hexadecimal constants. Symbolic names not present in the charmap
file can be specified and will be ignored, as specified under item 1 above.
.RE
.SS "LC_CTYPE"
-.LP
The \fBLC_CTYPE\fR category defines character classification, case conversion
and other character attributes. In addition, a series of characters can be
represented by three adjacent periods representing an ellipsis symbol
@@ -719,7 +716,6 @@ the mapping will be the reverse mapping of the one specified for \fBtoupper\fR.
.RE
.SS "LC_COLLATE"
-.LP
The \fBLC_COLLATE\fR category provides a collation sequence definition for
numerous utilities (such as \fBsort\fR(1), \fBuniq\fR(1), and so forth),
regular expression matching (see \fBregex\fR(5)), and the \fBstrcoll\fR(3C),
@@ -744,7 +740,7 @@ as an entity).
\fBUser-defined ordering of collating elements\fR. Each collating element is
assigned a collation value defining its order in the character (or basic)
collation sequence. This ordering is used by regular expressions and pattern
-matching and, unless collation weights are explicity specified, also as the
+matching and, unless collation weights are explicitly specified, also as the
collation weight to be used in sorting.
.RE
.RS +4
@@ -833,7 +829,6 @@ Specify the end of the collation-order statements.
.RE
.SS "collating-element \fIkeyword\fR"
-.LP
In addition to the collating elements in the character set, the
\fBcollating-element\fR keyword is used to define multi-character collating
elements. The syntax is:
@@ -868,7 +863,6 @@ Example:
\fBcollating-element\fR <\fBll\fR> from "\fBll\fR"
.in -2
.SS "collating-symbol \fIkeyword\fR"
-.LP
This keyword will be used to define symbols for use in collation sequence
statements; that is, between the \fBorder_start\fR and the \fBorder_end\fR
keywords. The syntax is:
@@ -907,7 +901,6 @@ associated with a relative position in the character order sequence. While such
a symbolic name does not represent any collating element, it can be used as a
weight.
.SS "order_start \fIkeyword\fR"
-.LP
The \fBorder_start\fR keyword must precede collation order entries and also
defines the number of weights for this collation sequence definition and other
collation rules.
@@ -987,7 +980,6 @@ order_start forward;backward
.LP
If no operands are specified, a single \fBforward\fR operand is assumed.
.SS "Collation Order"
-.LP
The \fBorder_start\fR keyword is followed by collating identifier entries. The
syntax for the collating element entries is:
.sp
@@ -1139,7 +1131,7 @@ l l
l l .
\fBorder_start\fR \fBforward;backward\fR
\fBUNDEFINED\fR \fBIGNORE;IGNORE\fR
-\fB<LOW>\fR
+\fB<LOW>\fR
\fB<space>\fR \fB<LOW>;<space>\fR
\fB\&.\|.\|.\fR \fB<LOW>;.\|.\|.\fR
\fB<a>\fR \fB<a>;<a>\fR
@@ -1152,7 +1144,7 @@ l l .
\fB<Ch>\fR \fB<ch>;<Ch>\fR
\fB<s>\fR \fB<s>;<s>\fR
\fB<eszet>\fR \fB"<s><s>";"<eszet><eszet>"\fR
-\fBorder_end\fR
+\fBorder_end\fR
.TE
.sp
@@ -1186,10 +1178,8 @@ collating symbol <\fBch\fR> and belongs to the same primary equivalence class
as the multi-character collating element <\fBCh\fR>.
.RE
.SS "order_end \fIkeyword\fR"
-.LP
The collating order entries must be terminated with an \fBorder_end\fR keyword.
.SS "LC_MONETARY"
-.LP
The \fBLC_MONETARY\fR category defines the rules and symbols that are used to
format monetary numeric information. This information is available through the
\fBlocaleconv\fR(3C) function
@@ -1637,18 +1627,18 @@ The following table shows the result of various combinations:
.TS
l l l l l l
l l l l l l .
- \fBp_sep_by_space\fR
- 2 1 0
-\fBp_cs_precedes\fR= 1 \fBp_sign_posn\fR= 0 \fB($1.25)\fR \fB($1.25)\fR \fB($1.25)\fR
- \fBp_sign_posn\fR= 1 \fB+$1.25\fR \fB+$1.25\fR \fB+$1.25\fR
- \fBp_sign_posn\fR= 2 \fB$1.25+\fR \fB$1.25+\fR \fB$1.25+\fR
- \fBp_sign_posn\fR= 3 \fB+$1.25\fR \fB+$1.25\fR \fB+$1.25\fR
- \fBp_sign_posn\fR= 4 \fB$+1.25\fR \fB$+1.25\fR \fB$+1.25\fR
-\fBp_cs_precedes\fR= 0 \fBp_sign_posn\fR= 0 \fB(1.25 $)\fR \fB(1.25 $)\fR \fB(1.25$)\fR
- \fBp_sign_posn\fR= 1 \fB+1.25 $\fR \fB+1.25 $\fR \fB+1.25$\fR
- \fBp_sign_posn\fR= 2 \fB1.25$ +\fR \fB1.25 $+\fR \fB1.25$+\fR
- \fBp_sign_posn\fR= 3 \fB1.25+ $\fR \fB1.25 +$\fR \fB1.25+$\fR
- \fBp_sign_posn\fR= 4 \fB1.25$ +\fR \fB1.25 $+\fR \fB1.25$+\fR
+ \fBp_sep_by_space\fR
+ 2 1 0
+\fBp_cs_precedes\fR= 1 \fBp_sign_posn\fR= 0 \fB($1.25)\fR \fB($1.25)\fR \fB($1.25)\fR
+ \fBp_sign_posn\fR= 1 \fB+$1.25\fR \fB+$1.25\fR \fB+$1.25\fR
+ \fBp_sign_posn\fR= 2 \fB$1.25+\fR \fB$1.25+\fR \fB$1.25+\fR
+ \fBp_sign_posn\fR= 3 \fB+$1.25\fR \fB+$1.25\fR \fB+$1.25\fR
+ \fBp_sign_posn\fR= 4 \fB$+1.25\fR \fB$+1.25\fR \fB$+1.25\fR
+\fBp_cs_precedes\fR= 0 \fBp_sign_posn\fR= 0 \fB(1.25 $)\fR \fB(1.25 $)\fR \fB(1.25$)\fR
+ \fBp_sign_posn\fR= 1 \fB+1.25 $\fR \fB+1.25 $\fR \fB+1.25$\fR
+ \fBp_sign_posn\fR= 2 \fB1.25$ +\fR \fB1.25 $+\fR \fB1.25$+\fR
+ \fBp_sign_posn\fR= 3 \fB1.25+ $\fR \fB1.25 +$\fR \fB1.25+$\fR
+ \fBp_sign_posn\fR= 4 \fB1.25$ +\fR \fB1.25 $+\fR \fB1.25$+\fR
.TE
.sp
@@ -1696,7 +1686,6 @@ END LC_MONETARY
The entry \fBn/a\fR indicates that the value is not available in the POSIX
locale.
.SS "LC_NUMERIC"
-.LP
The \fBLC_NUMERIC\fR category defines the rules and symbols that will be used
to format non-monetary numeric information. This information is available
through the \fBlocaleconv\fR(3C) function.
@@ -1795,7 +1784,6 @@ _
The entry \fBn/a\fR indicates that the value is not available in the POSIX
locale.
.SS "LC_TIME"
-.LP
The \fBLC_TIME\fR category defines the interpretation of the field descriptors
supported by \fBdate\fR(1) and affects the behavior of the \fBstrftime\fR(3C),
\fBwcsftime\fR(3C), \fBstrptime\fR(3C), and \fBnl_langinfo\fR(3C) functions.
@@ -2062,7 +2050,6 @@ field descriptor will be used instead of the value.
.RE
.SS "LC_TIME \fIC-language\fR Access"
-.LP
The following information can be accessed. These correspond to constants
defined in <\fBlanginfo.h\fR> and used as arguments to the
\fBnl_langinfo\fR(3C) function.
@@ -2324,7 +2311,6 @@ _
.TE
.SS "LC_TIME \fIGeneral\fR Information"
-.LP
Although certain of the field descriptors in the POSIX locale (such as the name
of the month) are shown with initial capital letters, this need not be the case
in other locales. Programs using these fields may need to adjust the
@@ -2362,7 +2348,6 @@ in 1776" while 7/14/1789 would come out as "The 14 day of July in 1789" The
above example is for illustrative purposes only. The \fB%O\fR modifier is
primarily intended to provide for Kanji or Hindi digits in \fBdate\fR formats.
.SS "LC_MESSAGES"
-.LP
The \fBLC_MESSAGES\fR category defines the format and values for affirmative
and negative responses.
.sp
@@ -2455,7 +2440,6 @@ l | l | l .
In an application conforming to the SUSv3 standard, the information on
\fByesstr\fR and \fBnostr\fR is not available.
.SH SEE ALSO
-.LP
\fBdate\fR(1), \fBlocale\fR(1), \fBlocaledef\fR(1), \fBsort\fR(1), \fBtr\fR(1),
\fBuniq\fR(1), \fBlocaleconv\fR(3C), \fBnl_langinfo\fR(3C),
\fBsetlocale\fR(3C), \fBstrcoll\fR(3C), \fBstrftime\fR(3C), \fBstrptime\fR(3C),
generated by cgit v1.2.3 (git 2.39.1) at 2025-04-25 02:43:10 +0000