dtoc man page on Ultrix

Man page or keyword search:  
man Server   3690 pages
apropos Keyword Search (all sections)
Output format
Ultrix logo
[printable version]

dtoc(1)								       dtoc(1)

       dtoc  -	unpacks	 a  DOTS file after transfer of DDIF or DTIF documents
       with links

       dtoc [ -f ] [ -p ] [[ object.dots ] directory ]

       The dtoc command unpacks the contents of a DOTS (Data Object  Transport
       Syntax) file or standard input after transfer of the DOTS file from one
       location to another, usually via mail. The contents of  the  DOTS  file
       typically  are  a  DDIF compound document or DTIF file and their exter‐
       nally linked subfiles.

       The object.dots input can be either a file name or a minus sign (-) for
       standard input.	If you specify a minus sign (-), or if no file name is
       present, the dtoc command reads from the standard input.	 If you	 spec‐
       ify  directory,	the content of the DOTS file is unpacked and stored in
       the specified directory.	 If you do not specify directory, the  content
       of  the DOTS file is unpacked into the current directory.  The names of
       the files created are written to standard output.

       If the dtoc command encounters duplicate file or directory names	 while
       unpacking  the DOTS file, a new output file is generated with a sequen‐
       tial number appended to its name.  For example, if one of the DOTS sub‐
       files has the same name as the existing file foo.ddif, the dtoc command
       unpacks and names the subfile foo.ddif.1.

       References to externally linked	subfiles  and  their  file  names  are
       updated	and  modified  during unpacking, particularly if the DOTS file
       originated on a non-UNIX system.

       -f   Suppresses output of unpacked file names.

       -p   Causes only the name of the primary output file to be  written  to
	    standard output.

   Standard Input
       If  a  minus  sign (-) is specified, or if no parameters are specified,
       dtoc reads from standard input until it encounters a  or	 EOF  (end  of
       file), which can be specified no more than once.	 The contents of stan‐
       dard input must conform to the syntax of a single DOTS file.

   Reconstitution of Names
       DDIF or DTIF file names and the file names of referenced	 subfiles  may
       be  modified  as objects are extracted or unpacked.  If names are modi‐
       fied, the references in the unpacked DDIF or  DTIF  are	updated.   The
       handling of files names depends in part on the name-type of the object,
       as follows:

	      UNIX file names

		     Names are unmodified, except that any path	 or  directory
		     is	 removed since the primary document and its references
		     are unpacked into the same directory. A period and unique
		     number  are applied to any file name that would duplicate
		     an existing file.

	      VMS file names

		     The set of rules is as follows:

			    Convert uppercase letters to lowercase.

			    Convert dollar signs ($) to underscores (_).

			    Ignore disk volume and  directory  specifications,
			    if	they  are present, because they are not likely
			    to be meaningful on UNIX systems.

			    Append duplicate file names with a	period	and  a
			    unique number.

			    All other characters are unmodified.

       A  DOTS	file is expected to contain only a single primary DDIF or DTIF
       object in this release.	Any subsequent objects in the  DOTS  file  are
       external references of the primary object.

       If  all	files were unpacked successfully, the exit status is 0. If any
       of the files could not be unpacked, the exit status is 1.  Consult your
       standard error location for a description of why the files could not be

       If a nonexistent	 target	 directory  is	specified,  the	 dtoc  command
       returns an error status.

See Also
       ctod(1),	 ddifanls(1),  dtifanls(1),  CDA(5), DDIF(5), DTIF(5), DOTS(5)


List of man pages available for Ultrix

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
Vote for polarhome
Free Shell Accounts :: the biggest list on the net