1 files changed, 101 insertions, 0 deletions
diff --git a/upstream/fedora-rawhide/man1/pamtosrf.1 b/upstream/fedora-rawhide/man1/pamtosrf.1
new file mode 100644
index 00000000..c2449343
--- /dev/null
+++ b/upstream/fedora-rawhide/man1/pamtosrf.1
@@ -0,0 +1,101 @@
+\
+.\" This man page was generated by the Netpbm tool 'makeman' from HTML source.
+.\" Do not hand-hack it!  If you have bug fixes or improvements, please find
+.\" the corresponding HTML page on the Netpbm website, generate a patch
+.\" against that, and send it to the Netpbm maintainer.
+.TH "Pamtosrf User Manual" 0 "27 May 2011" "netpbm documentation"
+
+.SH NAME
+pamtosrf - convert a sequence of Netpbm images to a SRF image file
+
+
+.UN synopsis
+.SH SYNOPSIS
+.PP
+\fBpamtosrf\fP
+[\fB-verbose\fP]
+[\fInetpbmfile\fP]
+
+
+.UN description
+.SH DESCRIPTION
+.PP
+This program is part of
+.BR "Netpbm" (1)\c
+\&.
+.PP
+\fBpamtosrf\fP reads a Netpbm image stream as input and produces a
+an SRF image file as output.  I don't know exactly what SRF is, but on popular
+use of it is in Garmin vehicle information files, which tell a GPS receiver
+how to depict a vehicle on its display.
+.PP
+An SRF file can contain multiple images; each image in a multi-image
+Netpbm input stream becomes one image in the SRF.
+.PP
+\fBpamtosrf\fP does not care how many images there are or what their
+dimensions or content are.  However, a Garmin vehicle information file has
+specific requirements, so if you don't make your Netpbm input conform, neither
+will your SRF output.  For such a file, you should have two image: the first
+for 3D oblique views of the vehicle and the second for overhead views.  Each
+image is a horizontal concatenation of 36 square images, each rotated 10
+degrees from the previous, thereby covering the full 360 degree circle.
+You could create this concatenation with \fBpnmcat -lr\fP and you could
+create the invidual views with \fBpnmrotate\fP.
+.PP
+One way to use \fBpamtosrf\fP is to get an SRF file, convert it to PAM
+with \fBsrftopam\fP, manipulate it, then convert it back with
+\fBpamtosrf\fP.
+.PP
+\fInetpbmfile\fP is the input stream, which defaults to Standard Input.
+Output is always on Standard Output.
+
+
+.UN options
+.SH OPTIONS
+.PP
+In addition to the options common to all programs based on libnetpbm
+(most notably \fB-quiet\fP, see 
+.UR index.html#commonoptions
+ Common Options
+.UE
+\&), \fBpamtosrf\fP recognizes the following
+command line option:
+
+
+.TP
+\fB-verbose\fP
+Issue informational messages about the input and the conversion process.
+
+
+
+
+.UN seealso
+.SH SEE ALSO
+
+
+.IP \(bu
+
+.BR "srftopam" (1)\c
+\&
+.IP \(bu
+
+.BR "pnmcat" (1)\c
+\&
+.IP \(bu
+
+.BR "pam" (1)\c
+\&
+  
+
+.UN history
+.SH HISTORY
+.PP
+\fBsrftopam\fP was new in Netpbm 10.55 (June 2011).
+.PP
+It was contributed by Mike Frysinger.
+.SH DOCUMENT SOURCE
+This manual page was generated by the Netpbm tool 'makeman' from HTML
+source.  The master documentation is at
+.IP
+.B http://netpbm.sourceforge.net/doc/pamtosrf.html
+.PP
+\ No newline at end of file