pnmtoddif(1) [redhat man page]
pnmtoddif(1) General Commands Manual pnmtoddif(1) Name pnmtoddif - Convert a portable anymap to DDIF format Syntax pnmtoddif pnmtoddif [-resolution x y] [pnmfile [ddiffile]] OPTIONS
resolution x y The horizontal and vertical resolution of the output image in dots per inch. Defaults to 78 dpi. pnmfile The filename for the image file in pnm format. If this argument is omitted, input is read from stdin. ddiffile The filename for the image file to be created in DDIF format. If this argument is omitted, the ddiffile is written to stan- dard output. It can only specified if a pnmfile is also specified. DESCRIPTION
pnmtoddif takes a portable anymap from standard input and converts it into a DDIF image file on standard output or the specified DDIF file. pbm format (bitmap) data is written as 1 bit DDIF, pgm format data (greyscale) as 8 bit greyscale DDIF, and ppm format data is written as 8,8,8 bit color DDIF. All DDIF image files are written as uncompressed. The data plane organization is interleaved by pixel. In addition to the number of pixels in the width and height dimension, DDIF images also carry information about the size that the image should have, that is, the physical space that a pixel occupies. PBMPLUS images do not carry this information, hence it has to be externally supplied. The default of 78 dpi has the beneficial property of not causing a resize on most Digital Equipment Corporation color monitors. AUTHOR
Burkhard Neidecker-Lutz Digital Equipment Corporation, CEC Karlsruhe neideck@nestvx.enet.dec.com pnmtoddif(1)
Check Out this Related Man Page
capsar(1) General Commands Manual capsar(1) Name capsar - prepares documents not in ASCII format for transport in the mail system Syntax capsar [-c] [-t] [-x[hTD]] [file] Description The utility allows ULTRIX mail to support documents containing non-ASCII data, such as DDIF. Only the DDIF and DOTS data types are cur- rently supported. DDIF is Digital's standard format for document interchange. DOTS is an encapsulation of the encoded interchange form of a number of related data objects into a single composite object. For more information, see and The utility prepares a DOTS file or a DDIF document for transport in the mail system by performing the following steps: 1) The DDIF document is converted to DOTS format. As a DDIF document may contain more than one file, all files within the DDIF document are incorporated into one DOTS file which can be sent as one mail message. 2) Each DOTS file is then compressed and encoded using only printing ASCII characters. This is because ULTRIX mail software only sup- ports 7 bit mail. 3) The routine encapsulates coded documents by adding leading and trailing lines, each surrounded by a <CR>. The lines should begin with 2 or more dashes (-) and some text that indicates the nature of the encapsulated message. The following is a typical encapsu- lated mail message: To: anybody@anynode Cc: Subject: Another DDIF document -----------motd.ddif : DOTS.ctod.compress.uuencode message begin 0 motd.ddif M__]@*" ,(" !BO.#P$# 8$* &UO=&0N9&1I9H0$)%546 "A@"B !@8K MS@ P$''T1$248M96YC;V1E9"!R979I<V%B;&4@9&]C=6UE;G2@@/__?X"@ M@( ! 8$! ((/1$1)1B1?4D5!1%]415A4HX#)% !$1$E&(%1E>'0@1G)O;G0@ end -----------End of motd.ddif : DOTS.ctod.compress.uuencode message The command can also extract different parts of a mail message, namely, the header information, the text part of the message, and the DOTS file that was encapsulated as described above. Extracting the DOTS file is done by parsing the mail message and detecting the leading and trailing encapsulation boundaries. Decoding and uncompressing the data results in the original DOTS file. The utility is built into Rand MH to provide DDIF mail support. It can, however, be used with mail. Options -c Causes to create an encapsulated DOTS bodypart from file. The file must be a DOTS/DDIF type document. -t Causes to write to the standard output the message type of file. Message type can be either text or DOTS. -xh Extracts the mail header lines from file. The header line must be at the beginning of the file and separated from the remaining text by a <CR> or <CRLF>. Each header line is a string containing a header field name (for example, Subject), a colon (:), one or more spaces, and a field value. Each header line may have embedded continuation sequences it it (for example, LF followed by spaces or tabs). -xT Extracts all the text parts of the mail message in file to the standard output. -xD Extracts any DOTS bodyparts in file. The DOTS document is sent to the standard output. This is the reverse of the -c option above. The file must be specified for the -c option. If file is not specified with the -x or -t option then the standard input is used. Examples The following are examples of how to use the command: Encapsulates a DDIF document capsar -c file.ddif | more Lists the header line from the mail message capsar -xh file.mail Extracts the encapsulated DOTS file from the file capsar -xD file > file.dots or capsar -xD file | dtoc In order to mail a DDIF/DOTS document you can use one of the following: capsar -c file.ddif | mail -s "subject" address capsar -c file.ddif | mhmail -subject "subject" address Use the second command if you are using RAND mh. A DOTS file is extracted from dxmail first extracting the message into a file. The dxmail utility has an extract feature built in so isn't needed. See Also compress(1), ctod(1), dtoc(1), mail(1), mh(1mh), mhmail(1mh), uuencode(1), vdoc(1), prompter(1mh), DDIF(5), DOTS(5) capsar(1)