osx James Clark Ian Castle
ian.castle@openjade.org
2002 OpenJade Project
Reference osx November 2002 OpenJade osx 1 osx An SGML to XML converter osx Description osx converts SGML to XML. osx parses and validates the SGML document contained in and writes an equivalent XML document to the standard output. osx will warn about SGML constructs which have no XML equivalent. Part of an SGML System Conforming to International Standard ISO 8879 -- Standard Generalized Markup Language. An SGML Extended Facilities system conforming to Annex A of International Standard ISO/IEC 10744 -- Hypermedia/Time-based Structuring Language. Options The following options are available: Make doctype or linkname name active. Parse with respect to architecture name. Use the BCTF encoding for output. By default osx uses UTF-8. Map public identifiers and entity names to system identifiers using the catalog entry file whose system identifier is sysid. This has the same effect as in onsgmls(1). Place output files in directory. Search directory for files specified in system identifiers. This has the same effect as in onsgmls(1). Describe open entities in error messages. Give up after max_errors errors. Redirect errors to file. This is useful mainly with shells that do not support redirection of stderr. Describe open elements in error messages. Display a help text and exit. This has the same effect as in onsgmls(1). Specify that the resulting XML file should conform to the DTD in dtd-file. Show error numbers in error messages. Show references in error messages. This has the same effect as in onsgmls(1). Print the version number and exit. Control warnings and errors according to type. This has the same effect as in onsgmls(1). Control the XML output according to the value of xml_output_option as follows: Don't use newlines inside start-tags. Usually osx uses newlines inside start-tags so as to reduce the probability of excessively long lines. Output attribute declarations for ID attributes. Output declarations for notations. Output declarations for external data entities. XML requires these to be NDATA. osx will warn about CDATA and SDATA external data entities and output them as NDATA entities. Use XML CDATA sections for CDATA marked sections and for elements with a declared content of CDATA. Output comment declarations. Comment declarations in the DTD will not be output. Prefer lower case. Names that were subjected to upper-case substitution by SGML will be folded to lower case. This does not include reserved names; XML requires these to be in upper-case. Escape &<> in the contents of processing instructions using the amp, lt and gt entities. This allows processing instructions to contain the string >?, but requires that applications handle the escapes. Use the <e/> syntax for element types e declared as EMPTY. Output an ATTLIST declaration for every element specifying the type of all attributes. The default will always be #IMPLIED. Output a processing instruction to report when an input source other than the main file is opened or closed in the instance. Do not report any input source changes in the DTD. Output a processing instruction to report when an external entity reference has been resolved in the instance. Do not report any entity resolutions in the DTD. Preserve external entities, write a declaration driver file named "extEntities.dtf", and include that file in the instance's internal subset. Preserve internal entities, write a declaration driver file named "intEntities.dtf", and include that file in the instance's internal subset. Do not include the external entities declaration driver file in the instance's internal subset. Do not include the internal entities declaration driver file in the instance's internal subset. When preserving external entities, do not write output files outside the specified output directory ("." by default). In other words, if an external entity's system identifier includes enough instances of ".." to cause osx to write a file outside (above) the output directory, exit (by default osx will issue a warning but will write the file and continue. When preserving internal or external entities, multiple output files will be written. If this option is specified, do not overwrite existing files; instead, attempt to append a number to the end of the original filename to create a unique filename. Exit with an error if too many (100) such files already exist. Preserve casing as specified in the DTD for element names; attribute names; attribute values which are token lists. When translating SDATA entities (whether expanding them or providing a definition for them in the output's internal subset), express them as processing instructions instead of as general internal entities. Multiple options are allowed. See Also onsgmls(1), ospam(1), onsgmlnorm(1), ospent(1)