Index: /trunk/doc/pslib/ChangeLogSDRS.tex
===================================================================
--- /trunk/doc/pslib/ChangeLogSDRS.tex	(revision 1689)
+++ /trunk/doc/pslib/ChangeLogSDRS.tex	(revision 1690)
@@ -291,3 +291,4 @@
 \item Clarified behavior of \code{psLogSetDestination} (no need to
   specify a protocol for \code{stderr,stdout,none}).
+\item Leading dot in facility name for \code{psTrace} is optional.
 \end{itemize}
Index: /trunk/doc/pslib/psLibSDRS.tex
===================================================================
--- /trunk/doc/pslib/psLibSDRS.tex	(revision 1689)
+++ /trunk/doc/pslib/psLibSDRS.tex	(revision 1690)
@@ -1,3 +1,3 @@
-%%% $Id: psLibSDRS.tex,v 1.105 2004-09-03 20:44:12 price Exp $
+%%% $Id: psLibSDRS.tex,v 1.106 2004-09-03 21:22:20 price Exp $
 \documentclass[panstarrs,spec]{panstarrs}
 
@@ -725,5 +725,6 @@
 implicitly children of the top level facility (\code{.}).  The second
 rule is simply an organizational technique to make the listing of
-facility information clear.
+facility information clear.  In specifying a facility, the leading
+dot shall be optional, as a convenience to the user.
 
 The API to place a trace message in the code, and simultaneously set