New sentence, new line. From Robert Elz.

This commit is contained in:
wiz 2002-10-01 18:15:59 +00:00
parent 2b99f7cc34
commit 52d8d77b60
6 changed files with 83 additions and 55 deletions

View File

@ -1,4 +1,4 @@
.\" $NetBSD: ctime.3,v 1.25 2002/02/07 07:00:34 ross Exp $
.\" $NetBSD: ctime.3,v 1.26 2002/10/01 18:15:59 wiz Exp $
.Dd March 31, 2001
.Dt CTIME 3
.Os
@ -132,7 +132,8 @@ causes
.Fn mktime
to presume initially that summer time (for example, Daylight Saving Time
in the U.S.A.) respectively,
is or is not in effect for the specified time. A negative value for
is or is not in effect for the specified time.
A negative value for
.Fa tm_isdst
causes the
.Fn mktime
@ -237,7 +238,8 @@ functions conform to
.St -p1003.1c-95 .
.Sh NOTES
The return values point to static data; the data is overwritten by
each call. The
each call.
The
.Fa tm_zone
field of a returned
.Va "struct tm"

View File

@ -34,7 +34,7 @@
.\" SUCH DAMAGE.
.\"
.\" from: @(#)strftime.3 5.12 (Berkeley) 6/29/91
.\" $NetBSD: strftime.3,v 1.15 2002/08/18 06:31:09 yamt Exp $
.\" $NetBSD: strftime.3,v 1.16 2002/10/01 18:16:00 wiz Exp $
.\"
.Dd August 18, 2002
.Dt STRFTIME 3
@ -111,8 +111,9 @@ is replaced by the ISO 8601 year with century as a decimal number.
.TP
.It Cm \&%g
is replaced by the ISO 8601 year without century as a decimal number (00-99).
This is the year that includes the greater part of the week. (Monday as the
first day of a week). See also the
This is the year that includes the greater part of the week.
(Monday as the first day of a week).
See also the
.Ql \&%V
conversion specification.
.TP

View File

@ -1,4 +1,4 @@
.\" $NetBSD: strptime.3,v 1.13 2002/08/18 06:43:32 yamt Exp $
.\" $NetBSD: strptime.3,v 1.14 2002/10/01 18:16:00 wiz Exp $
.\"
.\" Copyright (c) 1997, 1998 The NetBSD Foundation, Inc.
.\" All rights reserved.
@ -62,13 +62,15 @@ The
string consists of zero or more conversion specifications, whitespace
characters as defined by
.Fn isspace ,
and ordinary characters. All ordinary characters in
and ordinary characters.
All ordinary characters in
.Fa format
are compared directly against the corresponding characters in
.Fa buf ;
comparisons which fail will cause
.Fn strptime
to fail. Whitespace characters in
to fail.
Whitespace characters in
.Fa format
match any number of whitespace characters in
.Fa buf ,
@ -82,13 +84,14 @@ There must be white-space or other non-alphanumeric characters between any
two conversion specifications.
.Pp
Conversion of alphanumeric strings (such as month and weekday names) is
done without regard to case. Conversion specifications which cannot be
matched will cause
done without regard to case.
Conversion specifications which cannot be matched will cause
.Fn strptime
to fail.
.Pp
The LC_TIME category defines the locale values for the conversion
specifications. The following conversion specifications are supported:
specifications.
The following conversion specifications are supported:
.Bl -tag -width "xxxx"
.It Cm \&%a
the day of week, using the locale's weekday names;
@ -106,8 +109,8 @@ the same as
the date and time, using the locale's date and time format.
.It Cm \&%C
the century number [0,99];
leading zeros are permitted but not required. This conversion
should be used in conjunction with the \&%y conversion.
leading zeros are permitted but not required.
This conversion should be used in conjunction with the \&%y conversion.
.It Cm \&%d
the day of month [1,31];
leading zeros are permitted but not required.
@ -143,7 +146,7 @@ leading zeros are permitted but not required.
.It Cm \&%n
any white-space, including none.
.It Cm \&%p
the locale's equivalent of a.m. or p.m..
the locale's equivalent of a.m. or p.m.
.It Cm \&%r
the time (12-hour clock) with %p, using the locale's time format.
.It Cm \&%R
@ -174,12 +177,14 @@ the date, using the locale's date format.
the time, using the locale's time format.
.It Cm \&%y
the year within the 20th century [69,99] or the 21st century [0,68];
leading zeros are permitted but not required. If specified in conjunction
leading zeros are permitted but not required.
If specified in conjunction
with \&%C, specifies the year [0,99] within that century.
.It Cm \&%Y
the year, including the century (i.e., 1996).
.It Cm \&%%
A `%' is written. No argument is converted.
A `%' is written.
No argument is converted.
.El
.Ss Modified conversion specifications
For compatibility, certain conversion specifications can be modified
@ -189,7 +194,8 @@ and
.Cm O
modifier characters to indicate that an alternative format or specification
should be used rather than the one normally used by the unmodified
conversion specification. As there are currently neither alternative formats
conversion specification.
As there are currently neither alternative formats
nor specifications supported by the system, the behavior will be as if the
unmodified conversion specification were used.
.Pp
@ -200,7 +206,8 @@ such as month and weekday names.
If successful, the
.Fn strptime
function returns a pointer to the character following the last character
parsed. Otherwise, a null pointer is returned.
parsed.
Otherwise, a null pointer is returned.
.Sh SEE ALSO
.Xr ctime 3 ,
.Xr isspace 3 ,

View File

@ -1,4 +1,4 @@
.\" $NetBSD: time2posix.3,v 1.11 2002/02/07 07:00:34 ross Exp $
.\" $NetBSD: time2posix.3,v 1.12 2002/10/01 18:16:00 wiz Exp $
.Dd April 1, 2001
.Dt TIME2POSIX 3
.Os
@ -48,7 +48,8 @@ and
However, POSIX gives an arithmetic expression for directly computing a
.Va time_t
value from a given date/time, and the same relationship is assumed by
some (usually older) applications. Any programs creating/dissecting
some (usually older) applications.
Any programs creating/dissecting
.Va time_t Ns 's
using such a relationship will typically not handle intervals over
leap seconds correctly.
@ -61,14 +62,15 @@ functions are provided to address this
.Va time_t
mismatch by converting between local
.Va time_t
values and their POSIX equivalents. This is done by accounting for the
number of time-base changes that would have taken place on a POSIX
system as leap seconds were inserted or deleted. These converted
values can then be used in lieu of correcting the older applications,
or when communicating with POSIX-compliant systems.
values and their POSIX equivalents.
This is done by accounting for the number of time-base changes that would
have taken place on a POSIX system as leap seconds were inserted or deleted.
These converted values can then be used in lieu of correcting the
older applications, or when communicating with POSIX-compliant systems.
.Pp
.Fn time2posix
is single-valued. That is, every local
is single-valued.
That is, every local
.Va time_t
corresponds to a single POSIX
.Va time_t .
@ -76,8 +78,9 @@ corresponds to a single POSIX
is less well-behaved: for a positive leap second hit the result is not
unique, and for a negative leap second hit the corresponding POSIX
.Va time_t
doesn't exist so an adjacent value is returned. Both of these are good
indicators of the inferiority of the POSIX representation.
doesn't exist so an adjacent value is returned.
Both of these are good indicators of the inferiority of the POSIX
representation.
.Pp
The following table summarizes the relationship between a
.Va time_t

View File

@ -1,4 +1,4 @@
.\" $NetBSD: tzfile.5,v 1.10 2002/02/08 01:28:23 ross Exp $
.\" $NetBSD: tzfile.5,v 1.11 2002/10/01 18:16:00 wiz Exp $
.\"
.\" @(#)tzfile.5 7.11
.\" This file is in the public domain, so clarified as of
@ -51,7 +51,8 @@ four-byte values of type
sorted in ascending order.
These values are written in
.Dq standard
byte order. Each is used as a transition time (as returned by
byte order.
Each is used as a transition time (as returned by
.Xr time 3 )
at which the rules for computing local time change.
Next come
@ -61,7 +62,8 @@ one-byte values of type
each one tells which of the different types of
.Dq local time
types described in the file is associated with the same-indexed
transition time. These values serve as indices into an array of
transition time.
These values serve as indices into an array of
.Fa ttinfo
structures that appears next in the file;
these structures are defined as follows:

View File

@ -1,4 +1,4 @@
.\" $NetBSD: tzset.3,v 1.20 2002/02/10 02:46:27 ross Exp $
.\" $NetBSD: tzset.3,v 1.21 2002/10/01 18:16:00 wiz Exp $
.Dd April 1, 2001
.Dt TZSET 3
.Os
@ -32,7 +32,8 @@ If
.Ev TZ
appears in the environment but its value is a null string,
Coordinated Universal Time (UTC) is used (without leap second
correction). If
correction).
If
.Ev TZ
appears in the environment and its value is not a null string:
.Bl -dash
@ -74,17 +75,19 @@ Three or more bytes that are the designation for the standard
.Cm ( std )
or summer
.Cm ( dst )
time zone. Only
time zone.
Only
.Cm std
is required; if
.Cm dst
is missing, then summer time does not apply in this locale.
Upper- and lowercase letters are explicitly allowed. Any characters
except a leading colon (:), digits, comma (,) , minus (-) , plus (+),
and ASCII NUL are allowed.
Upper- and lowercase letters are explicitly allowed.
Any characters except a leading colon (:), digits, comma (,), minus (-),
plus (+), and ASCII NUL are allowed.
.It Cm offset
Indicates the value one must add to the local time to arrive at
Coordinated Universal Time. The
Coordinated Universal Time.
The
.Cm offset
has the form:
.Sm off
@ -99,26 +102,32 @@ The minutes
.Cm ( mm )
and seconds
.Cm ( ss )
are optional. The hour
are optional.
The hour
.Cm ( hh )
is required and may be a single digit. The
is required and may be a single digit.
The
.Cm offset
following
.Cm std
is required. If no
is required.
If no
.Cm offset
follows
.Cm dst ,
summer time is assumed to be one hour ahead of standard time. One or
more digits may be used; the value is always interpreted as a decimal
number. The hour must be between zero and 24, and the minutes (and
seconds) \(em if present \(em between zero and 59. If preceded by a
summer time is assumed to be one hour ahead of standard time.
One or more digits may be used; the value is always interpreted as a
decimal number.
The hour must be between zero and 24, and the minutes (and
seconds) \(em if present \(em between zero and 59.
If preceded by a
.Dq -
the time zone shall be east of the Prime Meridian; otherwise it shall be
west (which may be indicated by an optional preceding
.Dq + ) .
.It Cm rule
Indicates when to change to and back from summer time. The
Indicates when to change to and back from summer time.
The
.Cm rule
has the form:
.Sm off
@ -137,7 +146,8 @@ where the first
describes when the change from standard to summer time occurs and the
second
.Cm date
describes when the change back happens. Each
describes when the change back happens.
Each
.Cm time
field describes when, in current local time, the change to the other
time is made.
@ -153,12 +163,13 @@ The Julian day
.Ar n
\*[Le] 365).
Leap days are not counted; that is, in all years \(em including leap
years \(em February 28 is day 59 and March 1 is day 60. It is
impossible to explicitly refer to the occasional February 29.
years \(em February 28 is day 59 and March 1 is day 60.
It is impossible to explicitly refer to the occasional February 29.
.It Ar n
The zero-based Julian day (0\ \*[Le]
.Ar n
\*[Le]\ 365). Leap days are counted, and it is possible to refer to
\*[Le]\ 365).
Leap days are counted, and it is possible to refer to
February 29.
.Sm off
.It Xo Cm M Ns Ar m
@ -181,10 +192,11 @@ of the year
.Ar m
\*[Le]\ 12, where week 5 means
.Dq the\ last Ar d No day\ in\ month Ar m
which may occur in either the fourth or the fifth week). Week 1 is
the first week in which the
which may occur in either the fourth or the fifth week).
Week 1 is the first week in which the
.Ar d Ns 'th
day occurs. Day zero is Sunday.
day occurs.
Day zero is Sunday.
.El
The
.Cm time
@ -194,7 +206,8 @@ except that no leading sign
.Dq -
or
.Dq +
is allowed. The default, if
is allowed.
The default, if
.Cm time
is not given, is
.Cm 02:00:00 .