engauge(1) [debian man page]
ENGAUGE-DIGITIZER(1) General Commands Manual ENGAUGE-DIGITIZER(1) NAME
engauge-digitizer - interactively convert a bitmap graph or map into numbers SYNOPSIS
engauge [options] DESCRIPTION
This manual page documents briefly the engauge command from the engauge-digitizer package. Startup -import FILE Automatically import the specified image file at startup. Image files may also be imported manually using the menu -open FILE Automatically open the specified Engauge Digitizer document file at startup. Document files may also be opened manually using the menu -help Display a list of command line options similar to this manpage in an X window and exit -manual DIRECTORY Look for the HTML user guide in the specified directory. For Debian it is installed in /usr/share/doc/engauge-digitizer/usermanual and should need no configuration. -axes XMIN XMAX YMIN YMAX Scan the imported file at startup, and locate the X and Y axes. Then digitize axis points assuming the X axis ranges from XMIN to XMAX, and the Y axis ranges from YMIN to YMAX. The X axis is assumed to be near the bottom of the image, and the Y axis is assumed to be on the left side of the image. For speed, no attempt to rotate the image if it is sideways, so the digitized points may require adjustment. This feature should be useful when using Perl or other scripts to digitize many images with known axes ranges. The axis points may also be digitized manually using the Digitize Axis Points mode -lazysegments Postpone scanning for segments that is normally performed during startup, until either the Segments dialog is used, or the Segment Fill button is selected. Shutdown -export FILE Automatically export the active document at shutdown. Documents may also be exported manually using the menu. Settings -reset Reset all settings to the factory defaults. This option is a fast and easy way to restore all settings to a useful configuration, especially when there are problems with one or more settings. Settings are stored in a text file such as $HOME/.qt/engaugerc. Debugging -pixels Show cursor location in pixel coordinates rather than graph coordinates -ctor Trace constructor calls -dtor Trace destructor calls -curvecmb Trace curve combobox operations -measurecmb Trace measure combobox operations -refresh Trace screen refreshes -scanning Trace image scanning Environment variables ENGAUGE_BROWSER To start up the date/time converter from within Engauge Digitizer, this environment variable must be set to the shell command that runs a javascript-capable browser. Examples are 'firefox', 'konqueror', ... ENGAUGE_USERMANUAL If set, this specifies the directory containing the user manual. This option, like the '-manual' command line option, should not be needed on a Debian installation. SEE ALSO
The program is documented quite nicely in the HTML user guide and tutorial, available under /usr/share/doc/engauge-digitzer/usermanual or from Help within the running program. AUTHOR
engauge-digitizer was written by Mark Mitchell <mmdigitizer@earthlink.net>. This manual page was written by Tobias Stefan Richter <tsr-debian@achos.com> for the Debian project (but may be used by others). December 14, 2006 ENGAUGE-DIGITIZER(1)
Check Out this Related Man Page
PLOTCHANGELOG(1) General Commands Manual PLOTCHANGELOG(1) NAME
plotchangelog - graph debian changelogs SYNOPSIS
plotchangelog [options] changelog ... DESCRIPTION
plotchangelog is a tool to aid in visualizing a Debian changelog. The changelogs are graphed with gnuplot(1) , with the X axis of the graph denoting time of release and the Y axis denoting the debian version number of the package. Each individual release of the package is repre- sented by a point, and the points are color coded to indicate who released that version of the package. The upstream version number of the package can also be labeled on the graph. Alternatively, the Y axis can be configured to display the size of the changelog entry for each new version. Or it can be configured to display approximately how many bugs were fixed for each new version. Note that if the package is a debian-specific package, the entire package version will be used for the Y axis. This does not always work perfectly. READING THE GRAPH
The general outline of a package's graph is typically a series of peaks, starting at 1, going up to n, and then returning abruptly to 1. The higher the peaks, the more releases the maintainer made between new upstream versions of the package. If a package is debian-only, it's graph will just grow upwards without ever falling (although a bug in this program may cause it to fall sometimes, if the version number goes from say, 0.9 to say, 0.10 - this is interpreted wrong..) If the graph dips below 1, someone made a NMU of the package and upgraded it to a new upstream version, thus setting the debian version to 0. NMU's in general appear as fractional points like 1.1, 2.1, etc. A NMU can also be easily detected by looking at the points that repre- sent which maintainer uploaded the package -- a solitary point of a different type than the points before and after it is typically a NMU. It's also easy to tell by looking at the points when a package changes maintainers. OPTIONS
-l, --linecount Instead of using the debian version number as the Y axis, use the number of lines in the changelog entry for each version. Cannot be used together with --bugcount. -b, --bugcount Instead of using the debian version number as the Y axis, use the number of bugs that were closed by each changelog entry. Note that this number is obtained by searching for "#dddd" in the changelog, and so it may be inaccurate. Cannot be used together with --linecount. -c, --cumulative When used together with either --bugcount or --linecount, graphs the cumulative count rather than the count in each individual changelog entry. -v, --no-version Do not show upstream version labels. Useful if the graph gets too crowded. -m, --no-maint Do not differentiate between different maintainers of the package. -s file, --save=file Save the graph to file in postscript format instead of immediately displaying it. -u, --urgency Use larger points when displaying higher-urgency package uploads. --verbose Output the gnuplot script that is fed into gnuplot (for debugging purposes). -gcommands, --gnuplot=commands This allows you to insert gnuplot(1) commands into the gnuplot script that is used to generate the graph. The commands are placed after all initialization but before the final plot command. This can be used to override the default look provided by this program in arbitrary ways. You can also use things like "set terminal png color" to change the output file type, which is useful in conjunc- tion with the -s option. --help Show a usage summary. --version Display version, author and copyright information. --noconf, --no-conf Do not read any configuration files (see below). changelog ... The changelog files to graph. If multiple files are specified they will all be display on the same graph. The files may be com- pressed with gzip. Any text in them that is not in Debian changelog format will be ignored. CONFIGURATION VARIABLES
The two configuration files /etc/devscripts.conf and ~/.devscripts are sourced by a shell in that order to set configuration variables. The --no-conf option can be used to prevent reading these files. Environment variable settings are ignored when these configuration files are read. The currently recognised variables are: PLOTCHANGELOG_OPTIONS This is a space-separated list of options to always use, for example -l -b. Do not include -g or --gnuplot among this list as it may be ignored; see the next variable instead. PLOTCHANGELOG_GNUPLOT These are gnuplot commands which will be prepended to any such commands given on the command line. SEE ALSO
devscripts.conf(5). AUTHOR
Joey Hess <joey@kitenet.net> DEBIAN
Debian Utilities PLOTCHANGELOG(1)