openjdk team mailing list archive

[esr@xxxxxxxxxxx]

This is automatically generated email about markup problems in a man
page for which you appear to be responsible.  If you are not the right
person or list, please tell me so I can correct my database.

See http://catb.org/~esr/doclifter/bugs.html for details on how and
why these patches were generated.  Feel free to email me with any
questions.  Note: These patches do not change the modification date of
any manual page.  You may wish to do that by hand.

I apologize if this message seems spammy or impersonal. The volume of
markup bugs I am tracking is over five hundred - there is no real
alternative to generating bugmail from a database and template.

--
                             Eric S. Raymond

Problems with rmid.1:

Missing or garbled name section.  The most common form of garbling
is a missing - or extra -. Or your manual page may have been generated
by a tool that doesn't emit a NAME section as it should.  Or your page
may add running text such as a version or authorship banner.  These
problems make it impossible to lift the page to DocBook.  They
can also confuse third-party manpage browsers and some implementations
of man -k.

This page was generated from some sort of non-man markup.  Please
fix the upstream markup so that it generates a well-formed
manual page with the indicated corrections.

--- rmid.1-unpatched	2013-05-23 17:53:07.731389070 -0400
+++ rmid.1	2013-05-23 17:53:26.123388726 -0400
@@ -25,9 +25,6 @@
 .SH "Name"
 rmid \- The Java RMI Activation System Daemon
 .LP
-.LP
-\f3rmid\fP starts the activation system daemon that allows objects to be registered and activated in a virtual machine (VM).
-.LP
 .SH "SYNOPSIS"
 .LP
 .nf

Problems with rmiregistry.1:

Missing or garbled name section.  The most common form of garbling
is a missing - or extra -. Or your manual page may have been generated
by a tool that doesn't emit a NAME section as it should.  Or your page
may add running text such as a version or authorship banner.  These
problems make it impossible to lift the page to DocBook.  They
can also confuse third-party manpage browsers and some implementations
of man -k.

This page was generated from some sort of non-man markup.  Please
fix the upstream markup so that it generates a well-formed
manual page with the indicated corrections.

--- rmiregistry.1-unpatched	2013-05-25 14:30:31.280384824 -0400
+++ rmiregistry.1	2013-05-25 14:30:46.576384538 -0400
@@ -21,14 +21,9 @@
 ."
 .TH rmiregistry 1 "16 Mar 2012"
 
-.LP
 .SH "Name"
 rmiregistry \- The Java Remote Object Registry
 .LP
-.RS 3
-The \f3rmiregistry\fP command starts a remote object registry on the specified port on the current host. 
-.RE
-
 .LP
 .SH "SYNOPSIS"
 .LP

Problems with policytool.1:

Missing or garbled name section.  The most common form of garbling
is a missing - or extra -. Or your manual page may have been generated
by a tool that doesn't emit a NAME section as it should.  Or your page
may add running text such as a version or authorship banner.  These
problems make it impossible to lift the page to DocBook.  They
can also confuse third-party manpage browsers and some implementations
of man -k.

This page was generated from some sort of non-man markup.  Please
fix the upstream markup so that it generates a well-formed
manual page with the indicated corrections.

--- policytool.1-unpatched	2013-05-25 14:01:29.856417391 -0400
+++ policytool.1	2013-05-25 14:01:29.584417396 -0400
@@ -24,8 +24,6 @@
 .LP
 .SH "Name"
 policytool \- PolicyTool Administration GUI Utility
-.LP
-\f3policytool\fP reads and writes a plain text policy file based on user input via the utility GUI.   
 .SH "SYNOPSIS"
 .LP
 .LP
@@ -54,6 +52,7 @@
 
 .LP
 .SH "DESCRIPTION"
+\f3policytool\fP reads and writes a plain text policy file based on user input via the utility GUI.   
 .LP
 .LP
 \f3policytool\fP is a GUI that allows users to create and manage policy files. For details, see 

Problems with tnameserv.1:

Missing or garbled name section.  The most common form of garbling
is a missing - or extra -. Or your manual page may have been generated
by a tool that doesn't emit a NAME section as it should.  Or your page
may add running text such as a version or authorship banner.  These
problems make it impossible to lift the page to DocBook.  They
can also confuse third-party manpage browsers and some implementations
of man -k.

This page was generated from some sort of non-man markup.  Please
fix the upstream markup so that it generates a well-formed
manual page with the indicated corrections.

--- tnameserv.1-unpatched	2013-05-25 03:19:09.509138146 -0400
+++ tnameserv.1	2013-05-25 03:20:41.657136423 -0400
@@ -1,30 +1,31 @@
-." Copyright (c) 1999, 2011, Oracle and/or its affiliates. All rights reserved.
-." DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER.
-."
-." This code is free software; you can redistribute it and/or modify it
-." under the terms of the GNU General Public License version 2 only, as
-." published by the Free Software Foundation.
-."
-." This code is distributed in the hope that it will be useful, but WITHOUT
-." ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
-." FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License
-." version 2 for more details (a copy is included in the LICENSE file that
-." accompanied this code).
-."
-." You should have received a copy of the GNU General Public License version
-." 2 along with this work; if not, write to the Free Software Foundation,
-." Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA.
-."
-." Please contact Oracle, 500 Oracle Parkway, Redwood Shores, CA 94065 USA
-." or visit www.oracle.com if you need additional information or have any
-." questions.
-."
+.\" Copyright (c) 1999, 2011, Oracle and/or its affiliates. All rights reserved.
+.\" DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER.
+.\"
+.\" This code is free software; you can redistribute it and/or modify it
+.\" under the terms of the GNU General Public License version 2 only, as
+.\" published by the Free Software Foundation.
+.\"
+.\" This code is distributed in the hope that it will be useful, but WITHOUT
+.\" ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
+.\" FITNESS FOR A PARTICULAR PURPOSE.  See the GNU General Public License
+.\" version 2 for more details (a copy is included in the LICENSE file that
+.\" accompanied this code).
+.\"
+.\" You should have received a copy of the GNU General Public License version
+.\" 2 along with this work; if not, write to the Free Software Foundation,
+.\" Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA.
+.\"
+.\" Please contact Oracle, 500 Oracle Parkway, Redwood Shores, CA 94065 USA
+.\" or visit www.oracle.com if you need additional information or have any
+.\" questions.
+.\"
 .TH tnameserv 1 "16 Mar 2012"
 
 .LP
-.SH "Name"
-Java IDL: Transient Naming Service \- \f2tnameserv\fP
+.SH "NAME"
+tnameserv \- Java IDL Transient Naming Service
 .LP
+.SH DESCRIPTION
 .LP
 This document discusses using the Java IDL Transient Naming Service, \f2tnameserv\fP. Java IDL also includes the Object Request Broker Daemon (ORBD). ORBD is a daemon process containing a Bootstrap Service, a Transient Naming Service, a \f3Persistent\fP Naming Service, and a Server Manager. The Java IDL tutorials all use ORBD, however, you can substitute \f2tnameserv\fP for \f2orbd\fP in any of the examples that use a Transient Naming Service. For documentation on the \f2orbd\fP tool, link to its orbd(1) or the 
 .na