1\ 2.\" This man page was generated by the Netpbm tool 'makeman' from HTML source. 3.\" Do not hand-hack it! If you have bug fixes or improvements, please find 4.\" the corresponding HTML page on the Netpbm website, generate a patch 5.\" against that, and send it to the Netpbm maintainer. 6.TH "Ddbugtopbm User Manual" 0 "21st August, 2002" "netpbm documentation" 7 8.SH NAME 9ddbugtopbm - convert Diddle or DiddleBug sketches to PBM files 10 11 12.UN synopsis 13.SH SYNOPSIS 14 15\fBddbugtopbm\fP 16 17.UN examples 18.SH EXAMPLES 19 20.nf 21\fBddbugtopbm </path/to/palm/backup/dir/DiddleBugDB.pdb\fP 22 23\fBddbugtopbm </path/to/palm/backup/dir/DiddleDB.pdb\fP 24 25\fBddbugtopbm </path/to/palm/backup/dir/DiddleIDB.pdb\fP 26.fi 27 28 29.UN description 30.SH DESCRIPTION 31.PP 32This program is part of 33.BR "Netpbm" (1)\c 34\&. 35.PP 36\fBddbugtopbm\fP converts all sketches present in a database used 37by the PalmOS programs \fBDiddle\fP or \fBDiddleBug\fP into 38appropriately-named PBM files. The backup copy of DiddleBug's 39database you should use as this program's input is usually called 40\fBDiddleBugDB.pdb\fP. Or if you use the original Diddle, it has two 41separate DBs - \fBDiddleDB.pdb\fP, containing unnamed `scratch' 42sketches, and \fBDiddleIDB.pdb\fP, containing the saved (and named) 43sketches which are listed by its `index' option. You can feed this 44program any of these three on standard input. 45 46.UN using 47.SH USING THE PROGRAM 48.PP 49I recommend you \fInot\fP run \fBddbugtopbm\fP from your Palm 50backup directory, i.e. don't run it from the directory the DB will 51normally be in. Instead, run it from some other directory (perhaps you 52could make a directory purely to hold the PBM files, just to keep 53things simple) and use an absolute or relative path to the DB. 54.PP 55The filenames used for the output PBMs are based on the names given 56to each sketch; if you have an unnamed sketch, it's given a name along 57the lines of \fBsketch-0123.pbm\fP. 58.PP 59While the named sketches will overwrite any existing PBM file with 60the same name, the unnamed ones won't - they'll just try using another 61filename. (I think this is probably the right approach, as you can't 62really tell the unnamed sketches apart.) 63 64 65 66.UN limitations 67.SH LIMITATIONS 68.PP 69The DiddleBug DB reader is only known to work with DBs from 70DiddleBug version 2.50. But it should probably work on later versions, 71and I think it'll work on DBs from version 2.15 as well. 72.PP 73It might fall over if fed an empty database, and doesn't do much 74(if any) checking of the input. 75 76 77.UN author 78.SH AUTHOR 79 80Russell Marks (\fIrus@svgalib.org\fP). 81.PP 82Mitch Blevins's decompression code is directly from DiddleBug 83itself, which like ddbugtopbm is distributed under the terms of the 84GNU GPL. 85 86.UN seealos 87.SH SEE ALSO 88.PP 89.BR "palmtopnm" (1)\c 90\&, 91.BR "pbm" (5)\c 92\& 93.PP 94Jens-Chr. Heyer's `didcon' script does something similar. 95 96.UN history 97.SH HISTORY 98.PP 99\fBddbugtopbm\fP was new in Netpbm 10.18 (August 2003). It was written 100and independently distributed in August 2002. 101.SH DOCUMENT SOURCE 102This manual page was generated by the Netpbm tool 'makeman' from HTML 103source. The master documentation is at 104.IP 105.B http://netpbm.sourceforge.net/doc/ddbugtopbm.html 106.PP