Re: lib/48478: rendering problem in nanosleep(2)

[John Nemeth <jnemeth%cue.bc.ca@localhost>]

The following reply was made to PR lib/48478; it has been noted by GNATS.

From: John Nemeth <jnemeth%cue.bc.ca@localhost>
To: gnats-bugs%netbsd.org@localhost, lib-bug-people%netbsd.org@localhost, 
gnats-admin%netbsd.org@localhost,
        netbsd-bugs%netbsd.org@localhost
Cc: joerg%netbsd.org@localhost
Subject: Re: lib/48478: rendering problem in nanosleep(2)
Date: Tue, 24 Dec 2013 18:35:26 -0800

 On Dec 25, 12:10am, dholland%netbsd.org@localhost wrote:
 }
 } >Number:         48478
 } >Synopsis:       rendering problem in nanosleep(2)
 } >State:          open
 } >Class:          sw-bug
 } >Arrival-Date:   Wed Dec 25 00:10:00 +0000 2013
 } >Originator:     David A. Holland
 } >Release:        NetBSD 6.99.28 (20131210)
 } >Organization:
 } >Environment:
 } System: NetBSD valkyrie 6.99.28 NetBSD 6.99.28 (VALKYRIE) #14: Tue Dec 10 
15:15:49 EST 2013  dholland@valkyrie:/usr/src/sys/arch/amd64/compile/VALKYRIE 
amd64
 } Architecture: x86_64
 } Machine: amd64
 } >Description:
 } 
 } STANDARDS
 }      The nanosleep() function conforms to IEEE Std 1003.1b-1993 
(``POSIX.1'').
 }      The clock_nanosleep() function conforms to.
 }                                               ^^^
 } 
 } The roff source contains
 } 
 } The
 } .Fn clock_nanosleep
 } function conforms to
 } .St -p1003.1j-2000 .
 } 
 } but apparently this doesn't work; mandoc prints as above, and groff
 } does the same except that it inserts a space before the period.
 
      This is fixed in mdocml 1.12.2, which hasn't been imported yet.
 
 }-- End of excerpt from dholland%netbsd.org@localhost
 
 cc: responsible person (according to 3RDPARTY)