ddifanls man page on Ultrix

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

ddifanls(1)							   ddifanls(1)

Name
       ddifanls - convert DDIF formatted files to CDA analysis formatted files

Syntax
       ddifanls	  [-m	message_log]   [-O  optionfile]	 [-o  outputfile]  [-p
       options_line]... [-d extension] [inputfile [outputfile [logfile]]]

Description
       The ddifanls command reads a DDIF formatted  file  from	inputfile  and
       writes a CDA analysis file to outputfile.  To convert from file.ddif to
       file.cda_analysis, type:

	      ddifanls file.ddif file.cda_analysis.

       If you do not supply an input file, or if you use a minus sign  (-)  as
       an argument, ddifanls reads the DDIF file from the standard input file.
       If you do not supply an output file, or if you use a minus sign (-)  as
       an  argument, ddifanls writes the CDA analysis file to standard output.
       If you specify a log file, ddifanls redirects standard error to the log
       file.  The ddifanls conversion is also invoked by the cdoc command when
       you use that command and specify the option -d analysis or -d anls.

       If the DDIF input file is a newer version of the DDIF grammar than that
       understood  by  the converter, data represented by the new grammar ele‐
       ments is lost.

       A document syntax error in the DDIF input file  causes  a  fatal	 input
       processing  error. The conversion stops and no further input processing
       occurs.

       Application end users use an analysis output file to determine  whether
       an input file contains references of links to multiple "subfiles."  You
       must copy each subfile separately across a network because subfiles are
       not  automatically  included when an input file is transferred across a
       network, unless the input file is transferred using  DOTS.  Search  the
       analysis	 output	 file  for  all occurrences of the string "ERF_LABEL,"
       followed by the subfile name in double quotes ("), to determine whether
       a document has links to other files.

Options
       -m message_log
	    Enables  enhanced  messaging  and logs all messages to message_log
	    or, if '-' is specified, to standard error in place	 of  the  mes‐
	    sage_log.	If you do not specify this option, only serious errors
	    are reported.

       -O optionfile
	    Specifies the name of the options file containing options for this
	    converter.

		 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 second
		 word  is a valid option preceded by one or more spaces, tabs,
		 or a slash (/) and can contain uppercase and  lowercase  let‐
		 ters, numbers, dollar signs, and underlines. The case of let‐
		 ters is not significant. If an option requires a value,  then
		 spaces,  tabs,	 or an equal sign can separate the option from
		 the value.

		 You can precede any line by spaces and tabs.  To terminate  a
		 line,	use any character other than those 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	speci‐
		 fied format.

		 To  specify several options for the same input or output for‐
		 mat, 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 for‐
		 mats required when specifying options.

		 By  default, any messages that occur during processing of the
		 options file are written to standard error.  For those	 input
		 and output formats that support a LOG option, messages can be
		 directed to a log file or to a common message log.

       -o outputfile
		 Specifies the name of the output file. Included in  the  com‐
		 mand syntax for compatibility with the cdoc command.

       -p options_line
		 Allows	 options  to  be specified on the command line and has
		 the same effect as specifying an options file for  this  con‐
		 verter.   You can specify up to 100 options, each preceded by
		 -p.

       -d extension
		 Allows the specification of a default output  file  extension
		 for compatibility with other operating systems.

Converter Processing Options
       When  using  the	 ddifanls converter you can produce an analysis of the
       CDA in-memory structure in the form of text output  showing  the	 named
       objects and values stored in the document. This is useful for debugging
       DDIF application programs. You  can  specify  the  following  converter
       options:

       o INHERITANCE
	    Specifies  that  the  analysis is shown with attribute inheritance
	    enabled.  Inherited attributes are marked by  "[inherited  value]"
	    in the output.

       o TRANSLATE_BYTE_STRINGS
	    Overrides  the default. For data of type BYTE STRING, the Analysis
	    output does not display the hexadecimal  translation  if  all  the
	    characters in the byte string are printable characters (hex values
	    20 through 7E).   To  override  this  option,  supply  the	TRANS‐
	    LATE_BYTE_STRINGS option.

       o IMAGE_DATA
	    Overrides  the  default.  For the special case of byte string data
	    for item DDIF_IDU_PLANE_DATA (a bitmapped  image),	the  following
	    comment appears on the display:

       ! *** Bit-mapped data not displayed here ***

       To retain the hexadecimal display, supply the IMAGE_DATA option.	 There
       is no translation into ASCII.

See Also
       cdoc(1), ctod(1), dtifanls(1), dtoc(1),	CDA(5),	 cda_msg(5),  DDIF(5),
       DOTS(5), DTIF(5)

								   ddifanls(1)
[top]

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]
Tweet
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