Corrected documentation on --input-file.

This commit is contained in:
Micah Cowan 2009-07-06 21:11:03 -07:00
parent 5febddec70
commit ed533c23c7
2 changed files with 8 additions and 3 deletions

View File

@ -1,3 +1,9 @@
2009-07-06 Micah Cowan <micah@cowan.name>
* wget.texi (Logging and Input File Options): Alter description of
--input-file, implying that --force-html isn't necessary when the
input is in HTML file.
2009-07-03 Micah Cowan <micah@cowan.name> 2009-07-03 Micah Cowan <micah@cowan.name>
* wget.texi (Download Options): --iri=no --> --no-iri * wget.texi (Download Options): --iri=no --> --no-iri

View File

@ -486,9 +486,8 @@ specified as @var{file}, @sc{url}s are read from the standard input.
If this function is used, no @sc{url}s need be present on the command If this function is used, no @sc{url}s need be present on the command
line. If there are @sc{url}s both on the command line and in an input line. If there are @sc{url}s both on the command line and in an input
file, those on the command lines will be the first ones to be file, those on the command lines will be the first ones to be
retrieved. The @var{file} need not be an @sc{html} document (but no retrieved. If @samp{--force-html} is not specified, then @var{file}
harm if it is)---it is enough if the @sc{url}s are just listed should consist of a series of URLs, one per line.
sequentially.
However, if you specify @samp{--force-html}, the document will be However, if you specify @samp{--force-html}, the document will be
regarded as @samp{html}. In that case you may have problems with regarded as @samp{html}. In that case you may have problems with