Gecko [ www.hotelharisharanam.in ]

Name	Size	Permission
images	[ DIR ]	drwxr-xr-x
COPYING	1.25 KB	-rw-r--r--
README	586 B	-rw-r--r--
README.jadetex	213 B	-rw-r--r--
VERSION	6 B	-rw-r--r--
autoconf.htm	3.58 KB	-rw-r--r--
contributors.htm	5.03 KB	-rw-r--r--
copying.txt	1.28 KB	-rw-r--r--
dsssl2.htm	23.99 KB	-rw-r--r--
index.htm	38.89 KB	-rw-r--r--
mif.htm	41.98 KB	-rw-r--r--
rtf.htm	43.85 KB	-rw-r--r--
tex.htm	23.23 KB	-rw-r--r--
transform.htm	11.38 KB	-rw-r--r--
xmlfo.htm	1.3 KB	-rw-r--r--

Code Editor : transform.htm

<html>

<head>
<meta http-equiv="Content-Type"
content="text/html; charset=iso-8859-1">
<meta name="GENERATOR" content="Microsoft FrontPage Express 2.0">
<title>The OpenJade SGML/XML backend</title>
</head>

<table border="0">
 <tr>
 <td><img
 src="images/space.gif" alt="" width="145" height="10"></td>
 <td><h1>The OpenJade SGML/XML backend</h1>
 <h3>Created by James Clark</h3>
 OpenJade does not support the
 DSSSL Transformation Language. However, it provides some
 simple, non-standardized extensions to the DSSSL Style
 Language that allow it to be used for SGML
 transformations. 
 These extensions are used
 in conjunction with the SGML backend which is selected
 with the <samp>-t sgml</samp> or <samp>-t xml</samp>
 options. Unlike other backends, the SGML backend writes
 its output to the standard output. 
 The <samp>-t xml</samp>
 option makes empty elements and processing instructions
 use the XML syntax. Note that the XML declaration is not
 automatically emitted. 
 The extensions consist of a
 collection of flow object classes that are used instead
 of the standard DSSSL-defined flow object classes:
 
 <dl>
 <dt><code>element</code>
 </dt>
 <dt><code>empty-element</code>
 </dt>
 <dd>Each of these flow
 objects results in an element in the output. The <code>element</code>
 flow object is a compound flow object (one that
 can have child flow objects). Both a start-tag
 and an end-tag are generated for this flow object.
 The <code>empty-element</code> is an atomic flow
 object (one that cannot have child flow objects).
 Only a start-tag is output for this. It should
 should be used for elements with a declared
 content of EMPTY or with a content reference
 attribute. Both of these flow objects support the
 following non-inherited characteristics: <dl>
 <dt><code>gi</code>
 </dt>
 <dd>This is a
 string-valued characteristic that
 specifies the element's generic
 identifier. It defaults to the generic
 identifier of the current node. </dd>
 <dt><code>attributes</code>
 </dt>
 <dd>This specifies
 the element's attributes as a list of
 lists each of which consists of exactly
 two strings, the first specifying the
 attribute name and the second the
 attribute value. It defaults to the empty
 list. </dd>
 </dl>
 </dd>
 <dd>&nbsp;</dd>
 <dt><code>processing-instruction</code>
 </dt>
 <dd>This is an atomic flow
 object that results in a processing instruction.
 It supports the following non-inherited
 characteristics: <dl>
 <dt><code>data</code>
 </dt>
 <dd>This is a
 string-valued characteristic that
 specifies the content of the processing
 instruction. It defaults to the empty
 string. </dd>
 </dl>
 </dd>
 <dt><code>document-type</code>
 </dt>
 <dd>This is an atomic flow
 object that results in a DOCTYPE declaration. It
 supports the following non-inherited
 characteristics: <dl>
 <dt><code>name</code>
 </dt>
 <dd>This is a
 string-valued characteristic that
 specifies the name of the document type (which
 must be the same as the name of the
 document element). It must not be omitted.
 </dd>
 <dt><code>system-id</code>
 </dt>
 <dd>This is a
 string-valued characteristic that
 specifies the system identifier of the
 document type. If non-empty, this will be
 used as the system identifier in the
 doctype declaration. The default value is
 the empty string. </dd>
 <dt><code>public-id</code>
 </dt>
 <dd>This is a
 string-valued characteristic that
 specifies the public identifier of the
 document type. If non-empty, this will be
 used as the public identifier in the
 doctype declaration. The default value is
 the empty string. </dd>
 </dl>
 </dd>
 <dt><code>entity</code>
 </dt>
 <dd>This is an compound
 flow object that stores its content in a separate
 entity. It supports the following non-inherited
 characteristic: <dl>
 <dt><code>system-id</code>
 </dt>
 <dd>The system
 identifier of the entity. For now this is
 treated as a filename not as an FSI.
 </dd>
 </dl>
 Note that no entity
 reference or declaration is emitted. 
 </dd>
 <dt><code>entity-ref</code>
 </dt>
 <dd>This is an atomic flow
 object that results in an entity reference. It
 supports the following non-inherited
 characteristic: <dl>
 <dt><code>name</code>
 </dt>
 <dd>The name of
 the entity. </dd>
 </dl>
 </dd>
 <dt><code>formatting-instruction</code>
 </dt>
 <dd>This is an atomic flow
 object that inserts characters into the output
 without change. It supports the following non-inherited
 characteristic: <dl>
 <dt><code>data</code>
 </dt>
 <dd>This is the
 string to be inserted. </dd>
 </dl>
 It differs from
 normal data characters in the <code>&amp;</code>,
 <code>&lt;</code> and <code>&gt;</code> will not
 be escaped. 
 </dd>
 </dl>
 There is also the following
 characteristic: 
 <dl>
 <dt><code>preserve-sdata?</code>
 </dt>
 <dd>This is an inherited
 boolean characteristic that applies to character
 flow objects. When true, if the current-node for
 the character flow object was an sdata node, then
 the character will be output as a reference to an
 entity with the same name. The initial value is #f.
 </dd>
 </dl>
 Each of these flow object
 classes must be declared using <code>declare-flow-object-class</code>
 in any DSSSL specification that makes use of it. A
 suitable set of declarations is: 
 <pre>
(declare-flow-object-class element
 &quot;UNREGISTERED::James Clark//Flow Object Class::element&quot;)
(declare-flow-object-class empty-element
 &quot;UNREGISTERED::James Clark//Flow Object Class::empty-element&quot;)
(declare-flow-object-class document-type
 &quot;UNREGISTERED::James Clark//Flow Object Class::document-type&quot;)
(declare-flow-object-class processing-instruction
 &quot;UNREGISTERED::James Clark//Flow Object Class::processing-instruction&quot;)
(declare-flow-object-class entity
 &quot;UNREGISTERED::James Clark//Flow Object Class::entity&quot;)
(declare-flow-object-class entity-ref
 &quot;UNREGISTERED::James Clark//Flow Object Class::entity-ref&quot;)
(declare-flow-object-class formatting-instruction
 &quot;UNREGISTERED::James Clark//Flow Object Class::formatting-instruction&quot;)
(declare-characteristic preserve-sdata?
 &quot;UNREGISTERED::James Clark//Characteristic::preserve-sdata?&quot;
 #f)
</pre>
 Here's a simple example
 that does the identity transformation: 
 <pre>
&lt;!doctype style-sheet PUBLIC &quot;-//James Clark//DTD DSSSL Style Sheet//EN&quot;&gt;

(declare-flow-object-class element
  &quot;UNREGISTERED::James Clark//Flow Object Class::element&quot;)

(define (copy-attributes #!optional (nd (current-node)))
  (let loop ((atts (named-node-list-names (attributes nd))))
    (if (null? atts)
        '()
        (let* ((name (car atts))
               (value (attribute-string name nd)))
          (if value
              (cons (list name value)
                    (loop (cdr atts)))
              (loop (cdr atts)))))))

(default (make element
 attributes: (copy-attributes)))
</pre>
 Note that this does not
 deal with empty elements nor processing instructions, nor
 does it include a doctype declaration. 
 </td>
 </tr>
</table>
</center></div>

&nbsp;
</body>
</html>

${this.title}

Code Editor : transform.htm