cdoc(1) [ultrix man page]
cdoc(1) General Commands Manual cdoc(1) Name cdoc - invokes CDA Converter Syntax cdoc [ -s format ] [ -d format ] [ -O options_file ] [ -o outputfile ] inputfile Description The command converts the revisable format file, inputfile, to another revisable format or to a final form file. If inputfile is not speci- fied, reads from standard input. Unless a destination file is specified with the -o option, the command writes files to standard output. Options -s format Specifies the format of inputfile and invokes an appropriate input converter as part of CDA. The ddif, dtif, dots (for analysis output only) and text converters are provided in the base system kit. Additional converters can be added by the CDA Converter Library and other layered products. Converter Library and other layered products. Contact your sys- tem manager for a complete list of the input formats supported on your system. The default format is ddif. -d format Specifies the format of outputfile and invokes an appropriate output converter as part of CDA. The ddif, dtif, text, analysis, and ps converters are provided in the base system kit. Additional converters can be added by the CDA Con- verter Library and other layered products. Contact your system manager for a complete list of the output formats sup- ported on your system. The default format is ddif. -O options_file Names the file passed to the input and output converters to control specific processing options for each converter. Refer to your documentation set for a description of converter options. The options file has a default file type of .cda_options. Each line of the options file specifies a format name that can optionally be followed by _input or _output to restrict the option to either an input or output converter. The sec- ond word is a valid option preceded by one or more spaces, tabs, or a slash (/) and can contain upper- and lowercase letters, numbers, dollar signs, and underlines. The case of letters is not significant. If an option requires a value, then spaces, tabs, or an equal sign can separate the option from the value. Each line can optionally be preceded by spaces and tabs and can be terminated by any character other than those that can be used to specify the format names and options. The syntax and interpretation of the text that follows the format name is specified by the supplier of the front and back end converters for the specified format. To specify several options for the same input or output format, specify one option on a line. If an invalid option for an input or output format or an invalid value for an option is specified, the option may be ignored or an error message may be returned. Each input or output format that supports processing options specifies any restrictions or special formats required when specifying options. By default, any messages that occur during processing of the options file are written to the system standard error location. For those input and output formats that support a LOG option, messages can be directed to a log file. -o outputfile Specifies the name of the output file. If not specified, writes to standard output. See Also vdoc(1), dxvdoc(1X), DDIF(5), DTIF(5), DOTS(5), CDA(5) cdoc(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)