pdftex --help gives

-output-comment=STRING use STRING for PDF file comment instead of date

but the manpage says that "In DVI mode, use string for the DVI file comment instead of the date. This option is ignored in PDF mode."

And i couldn't find any trace of STRING in the PDF file, but it's in the DVI file. So it seems this would be more correct:

-output-comment=STRING use STRING for DVI file comment instead of date

I send an example patch: Best regards Akira ------------------------------------------------ --- texmfmp-help.h.orig Mon Jun 07 19:39:40 2004 +++ texmfmp-help.h Sun May 09 12:53:26 2004 @@ -31,7 +31,7 @@ " most commonly `aleph'.", "", " Alternatively, if the first non-option argument begins with a backslash,", - " interpret all non-option arguments as a line of e-Omega input.", + " interpret all non-option arguments as a line of Aleph input.", "", " Alternatively, if the first non-option argument begins with a &, the", " next word is taken as the FMT to read, overriding all else. Any", @@ -360,7 +360,9 @@ " the bits of NUMBER", "[-no]-mktex=FMT disable/enable mktexFMT generation (FMT=tex/tfm)", "-mltex enable MLTeX extensions such as \\charsubdef", - "-output-comment=STRING use STRING for PDF file comment instead of date", + "-output-comment=STRING use STRING for DVI file comment instead of date", + " in the case of DVI output (no effect for PDF)", + "-output-format=FORMAT use FORMAT for job output; FORMAT is `dvi' or `pdf'", "[-no]-parse-first-line disable/enable parsing of the first line of the", " input file", "-progname=STRING set program (and fmt) name to STRING", @@ -416,7 +418,9 @@ " the bits of NUMBER", "[-no]-mktex=FMT disable/enable mktexFMT generation (FMT=tex/tfm)", "-mltex enable MLTeX extensions such as \\charsubdef", - "-output-comment=STRING use STRING for PDF file comment instead of date", + "-output-comment=STRING use STRING for DVI file comment instead of date", + " in the case of DVI output (no effect for PDF)", + "-output-format=FORMAT use FORMAT for job output; FORMAT is `dvi' or `pdf'", "[-no]-parse-first-line disable/enable parsing of the first line of the", " input file", "-progname=STRING set program (and fmt) name to STRING", @@ -443,10 +447,10 @@ " Any remaining COMMANDS are processed as pdfxTeX input, after TEXNAME is read.", " If the first line of TEXNAME is %&FMT, and FMT is an existing .fmt file,", " use it. Else use `NAME.fmt', where NAME is the program invocation name,", - " most commonly `pdfetex'.", + " most commonly `pdfxtex'.", "", " Alternatively, if the first non-option argument begins with a backslash,", - " interpret all non-option arguments as a line of pdfeTeX input.", + " interpret all non-option arguments as a line of pdfxTeX input.", "", " Alternatively, if the first non-option argument begins with a &, the", " next word is taken as the FMT to read, overriding all else. Any", @@ -472,7 +476,9 @@ " the bits of NUMBER", "[-no]-mktex=FMT disable/enable mktexFMT generation (FMT=tex/tfm)", "-mltex enable MLTeX extensions such as \\charsubdef", - "-output-comment=STRING use STRING for PDF file comment instead of date", + "-output-comment=STRING use STRING for DVI file comment instead of date", + " in the case of DVI output (no effect for PDF)", + "-output-format=FORMAT use FORMAT for job output; FORMAT is `dvi' or `pdf'", "[-no]-parse-first-line disable/enable parsing of the first line of the", " input file", "-progname=STRING set program (and fmt) name to STRING",