The second TZ specification states that no spaces are allowed, this is true for the first specification as well. The text of these two are closely coupled so including the first specification by using 'either' is sufficient. Signed-off-by: J William Piggott <elseifthen@xxxxxxx> --- The following changes since commit b58839b96d626e67da233d4bf7ba04d5dfcd0e66: syscalls.2: Remove some details for sync_file_range2() (2015-01-18 19:56:05 +0100) are available in the git repository at: git@xxxxxxxxxx:jwpi/man-pages.git tzset for you to fetch changes up to 2b0725c0b6f6788628567ea4d5cfc396898584a0: tzset.3: TZ filespec omitts the colon (2015-01-18 14:40:21 -0500) man3/tzset.3 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/man3/tzset.3 b/man3/tzset.3 index 36d2fd7..3f9b246 100644 --- a/man3/tzset.3 +++ b/man3/tzset.3 @@ -118,7 +118,7 @@ The second format is used when there is daylight saving time: .I std offset dst [offset],start[/time],end[/time] .RE .sp -There are no spaces in the specification. +There are no spaces in either specification. The initial \fIstd\fP and \fIoffset\fP specify the standard timezone, as described above. The \fIdst\fP string and \fIoffset\fP specify the name and offset for the -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html