Bonjourno! :-)
Sigh. Was hoping that someone who wrote the original
man page format might already have expertise in that area.
It's just "arcana" (obscure knowledge, not necessarily hard
to learn or use, just not widely known). Are you saying
that you wrote the original, but aren't familiar with the
even more arcane "tbl" input language for tables?: Not that
I or anyone would _expect_ knowledge of one or the other -- both
are somewhat obscure source formats (even though widely used
for manpages) these days...(*sigh*)...the sacrificing
we make in the, not unappreciated, grandfathering of the
old ways...:-)
- Linda
p.s. - I think this posting was meant to go to [email protected],
as such, am responding to it there...
Mauro Tortonesi wrote:
Alle 22:03, sabato 27 agosto 2005, hai scritto:
> Being a computer geek, I tend to like things organized
> in tables so options stand out. I took the time to rewrite
> the text for the "--progress" section of the manpage, as
> it was always difficult for me to find the values and
> differences for the different subtags. Looking at the
> "--progress=type", it doesn't quickly stand out what the
> possible values are nor that there are ". I tended more
> toward a BNF type specification, but the central change is
> making the style types stand out. So even if you don't
> like the exact wording, I do think the table format presents
> the style options more clearly (i.e. they stand out quickly
> note, output of man was used as template for the changes, so
> this isn't directly applicable as a patch. I hope that isn't
> a block to the change, as it seems simple enough but I don't
> currently have a subversion source tree setup nor do I know
> manpage source syntax by memory (not a frequently used source
> language ;^) ):
>
>
> --progress=<style>
> Legal styles are "bar[:force]" and "dot[:<dotsize>]".
>
> The "bar" style is used by default. It draws an
> ASCII progress bar graphics (a.k.a "thermometer"
> display) indicating the status of retrieval. If the
> output is not a TTY, the "dot" style will be used.
>
> To force "bar" usage when output is not a TTY, use
> the ":force" tag (i.e. --progress=bar:force )
>
> The "dot" style traces traces the retrieval by printing
> dots on the screen, each dot representing a fixed
> amount of downloaded data.
>
> An optional "dotsize" tag can be specified to change
> the the amount of downloaded data per dot, grouping
> and line as follows (K = 1024 bytes; M = 1024KBytes ):
>
> size per dots per
> "dotsize" dot line group line
> --------- --- ---- ----- ----
> default 1K 50K 10 50
> binary 8K 384K 16 48
> mega 64K 3M 8 48
>
> "default" is used if no "dotsize" tag is specified.
>
> Note that you can set "per user" defaults using the
> "progress" command in ".wgetrc". Note: specifying
> an option on the command line overrides ".wgetrc"
> settings.
i like this change, but there is a small problem. all the
documentation of wget is generated from the same texinfo sources, so
in order to support tex documentation formats we'll have to include
something like:
@ifnottex
your ascii graphics
@end
@iftex
a real tex table
@end
in wget.texi.
i've never used tex. anybody knows how to create tables in tex?
--
Aequam memento rebus in arduis servare mentem...
Mauro Tortonesi http://www.tortonesi.com
University of Ferrara - Dept. of Eng. http://www.ing.unife.it
GNU Wget - HTTP/FTP file retrieval tool http://www.gnu.org/software/wget
Deep Space 6 - IPv6 for Linux http://www.deepspace6.net
Ferrara Linux User Group http://www.ferrara.linux.it
