Menu
▾
▴
[perl-xml-cvs] CVS: sax-perl-org changes-2.1.html,1.4,1.5 changes-2.1.xml,1.4,1.5 changes.css,1.3,1.4 changes.xsl,1.2,1.3 sax-2.1-adv.html,1.5,1.6 sax-2.1-idx.html,1.6,1.7 sax-2.1.html,1.5,1.6
|
From: Petr C. <pci...@us...> - 2005-02-11 09:05:35
|
Update of /cvsroot/perl-xml/sax-perl-org In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv1161 Modified Files: changes-2.1.html changes-2.1.xml changes.css changes.xsl sax-2.1-adv.html sax-2.1-idx.html sax-2.1.html Log Message: Index: changes-2.1.html =================================================================== RCS file: /cvsroot/perl-xml/sax-perl-org/changes-2.1.html,v retrieving revision 1.4 retrieving revision 1.5 diff -u -d -r1.4 -r1.5 --- changes-2.1.html 11 Jan 2005 14:34:29 -0000 1.4 +++ changes-2.1.html 11 Feb 2005 09:05:24 -0000 1.5 @@ -12,6 +12,7 @@ API is in progress. Comments should be sent to Perl-XML mailing list (per...@li...). </p> + <b>Open issues</b>: <a href="#I9">I9</a>, <a href="#I10">I10</a>, <a href="#I14">I14</a> <h2>Changes from Perl SAX 2.0</h2> <p class="change"> <b>Change <a name="C1">C1</a> @@ -53,10 +54,9 @@ <b>Change <a name="C5">C5</a> </b> <i> [resolves issue <a href="#I11">I11</a>]</i> - <br />Hash values are Unicode strings (scalars with - UTF-8 flag on) The spec defines that a stream argument that can be provided - to parse_file() method can be either a file handle, a glob reference, - or a IO::Handle sub-class. + <br /> + The spec defines that a stream argument that can be provided to parse_file() + method can be either a file handle, a glob reference, or a IO::Handle sub-classe. </p> <p class="change"> <b>Change <a name="C6">C6</a> @@ -79,11 +79,38 @@ The spec defines explicitly that values of callback argument hashrefs are Unicode strings (scalars with UTF-8 flag on). </p> - <h2>Summary of Issues</h2> - <p class="open"> + <p class="change"> + <b>Change <a name="C8">C8</a> + </b> + <i> [resolves issue <a href="#I1">I1</a>]</i> + <br /> + The section "Features" defines a read-only 'http://xmlns.perl.org/sax/version' + feature which returns a version of Perl SAX supported by a driver. + </p> + <p class="change"> + <b>Change <a name="C9">C9</a> + </b> + <i> [resolves issue <a href="#I2">I2</a>]</i> + <br /> + LexicalHandler and DeclHandler are set using the + parser options with the same name. The two read-only features, + (http://xmlns.perl.org/sax/LexicalHandler, DeclHandler) return + 0 or 1 to indicate whether the parser supports these two interfaces. + ???XML:::SAX::Base + </p> + <p class="change"> + <b>Change <a name="C10">C10</a> + </b> + <i> [resolves issue <a href="#I13">I13</a>]</i> + <br /> + The spec states explicitly that the value of input source Encoding property + has a higher priority than encoding specified in an XML declaration. + </p> + <h2>Issues</h2> + <p class="applied"> <b>Issue <a name="I1">I1</a> </b> - <i> status: open, resolution: none</i> + <i> status: closed, resolution: applied [resolved as change <a href="#C8">C8</a>]</i> <br /> A parser should advertise SAX version it supports. There can be a new method ($parser->get_sax_version()) or a read-only feature @@ -94,10 +121,10 @@ Suggestion: the read-only feature. <br /> </p> - <p class="open"> + <p class="applied"> <b>Issue <a name="I2">I2</a> </b> - <i> status: open, resolution: none</i> + <i> status: closed, resolution: applied [resolved as change <a href="#C9">C9</a>]</i> <br /> "http://xml.org/sax/handlers/LexicalHandler" feature on the parser needs to be set to the object to receive lexical events currently. If @@ -117,15 +144,15 @@ o not (http://xmlns.perl.org/sax/LexicalHandler, DeclHandler). <br /> Suggestion: LexicalHandler and DeclHandler are set using the - parser properties with the same name. The two read-only features, + parser options with the same name. The two read-only features, (http://xmlns.perl.org/sax/LexicalHandler, DeclHandler) return 0 or 1 to indicate whether the parser support these two interfaces. <br /> </p> - <p class="open"> + <p class="denied"> <b>Issue <a name="I3">I3</a> </b> - <i> status: open, resolution: none</i> + <i> status: closed, resolution: denied</i> <br /> SAX 2.0 Ext. 1.1 has a new Attributes2 interface which extends attributes with new properties (Declared, Specified) to distinguish @@ -136,10 +163,10 @@ Suggestion: not to apply. <br /> </p> - <p class="decided"> + <p class="applied"> <b>Issue <a name="I4">I4</a> </b> - <i> status: decided, resolution: applied [resolved as change <a href="#C2">C2</a>]</i> + <i> status: closed, resolution: applied [resolved as change <a href="#C2">C2</a>]</i> <br /> The parse() method is defined in different ways in the Basic and Advanced documents. @@ -148,10 +175,10 @@ based on InputSource. <br /> </p> - <p class="open"> + <p class="denied"> <b>Issue <a name="I5">I5</a> </b> - <i> status: open, resolution: none</i> + <i> status: closed, resolution: denied</i> <br /> All hash references could be replaced with blessed classes. Need to clarify what would be benefits of such change. @@ -159,19 +186,19 @@ Suggestion: not to apply. <br /> </p> - <p class="decided"> + <p class="applied"> <b>Issue <a name="I6">I6</a> </b> - <i> status: decided, resolution: applied [resolved as change <a href="#C3">C3</a>]</i> + <i> status: closed, resolution: applied [resolved as change <a href="#C3">C3</a>]</i> <br /> Changes in attribute_decl eName, aName, Type, Mode (was ValueDefault), Value <br /> </p> - <p class="decided"> + <p class="applied"> <b>Issue <a name="I7">I7</a> </b> - <i> status: decided, resolution: applied [resolved as change <a href="#C6">C6</a>]</i> + <i> status: closed, resolution: applied [resolved as change <a href="#C6">C6</a>]</i> <br /> The effect of turning off namespace processing is unclear in Perl SAX. The spec should state that all namespace-related processing is skipped, @@ -182,16 +209,16 @@ {}pfx:lname). NS declarations are treated as common attributes. <br /> </p> - <p class="decided"> + <p class="applied"> <b>Issue <a name="I8">I8</a> </b> - <i> status: decided, resolution: applied [resolved as change <a href="#C7">C7</a>]</i> + <i> status: closed, resolution: applied [resolved as change <a href="#C7">C7</a>]</i> <br /> Perl SAX should require explicitly all event data to be Unicode strings (to have the UTF-8 flag on). <br /> </p> - <p class="open"> + <p class="none"> <b>Issue <a name="I9">I9</a> </b> <i> status: open, resolution: none</i> @@ -213,7 +240,7 @@ The order of properties to be checked has to be determined. <br /> </p> - <p class="open"> + <p class="none"> <b>Issue <a name="I10">I10</a> </b> <i> status: open, resolution: none</i> @@ -227,10 +254,10 @@ currently supported types. <br /> </p> - <p class="decided"> + <p class="applied"> <b>Issue <a name="I11">I11</a> </b> - <i> status: decided, resolution: applied [resolved as change <a href="#C5">C5</a>]</i> + <i> status: closed, resolution: applied [resolved as change <a href="#C5">C5</a>]</i> <br /> The specification should state explicitly what is meant be "streams", what are supported types for parse_file(): file handles, @@ -240,10 +267,10 @@ To support all of the above mentioned types. <br /> </p> - <p class="decided"> + <p class="applied"> <b>Issue <a name="I12">I12</a> </b> - <i> status: decided, resolution: applied [resolved as change <a href="#C4">C4</a>]</i> + <i> status: closed, resolution: applied [resolved as change <a href="#C4">C4</a>]</i> <br /> The spec should be more explicit about what a document locator is supposed to return. It could for example read: @@ -253,10 +280,10 @@ The first line is line 1; the first column in each line is column 1. <br /> </p> - <p class="open"> + <p class="applied"> <b>Issue <a name="I13">I13</a> </b> - <i> status: open, resolution: none</i> + <i> status: closed, resolution: applied [resolved as change <a href="#C10">C10</a>]</i> <br /> The value of the Encoding property of Input Sources should be able to override the encoding value specified in the xml declaration. The spec should state this @@ -265,7 +292,18 @@ Suggestion: to add the following text: If available, the value of Encoding property has a higher priority than encoding specified in an XML declaration. - + <br /> + </p> + <p class="none"> + <b>Issue <a name="I14">I14</a> + </b> + <i> status: open, resolution: none</i> + <br /> + Parsers report an error when the parse() method is called and no input + source (Source option) is provided, regardless on the method's argument. + <br /> + Suggestion: Parsers should try to call the parse_uri() with the provided + argument. Only if there is no argument available the error is issued. <br /> </p> </body> Index: changes-2.1.xml =================================================================== RCS file: /cvsroot/perl-xml/sax-perl-org/changes-2.1.xml,v retrieving revision 1.4 retrieving revision 1.5 diff -u -d -r1.4 -r1.5 --- changes-2.1.xml 11 Jan 2005 14:34:29 -0000 1.4 +++ changes-2.1.xml 11 Feb 2005 09:05:25 -0000 1.5 @@ -33,10 +33,9 @@ line is column 1." </change> - <change id="C5" issue-ref="I11">Hash values are Unicode strings (scalars with - UTF-8 flag on) The spec defines that a stream argument that can be provided - to parse_file() method can be either a file handle, a glob reference, - or a IO::Handle sub-class. + <change id="C5" issue-ref="I11"> + The spec defines that a stream argument that can be provided to parse_file() + method can be either a file handle, a glob reference, or a IO::Handle sub-classe. </change> <change id="C6" issue-ref="I7"> @@ -54,11 +53,29 @@ Unicode strings (scalars with UTF-8 flag on). </change> + <change id="C8" issue-ref="I1"> + The section "Features" defines a read-only 'http://xmlns.perl.org/sax/version' + feature which returns a version of Perl SAX supported by a driver. + </change> + + <change id="C9" issue-ref="I2"> + LexicalHandler and DeclHandler are set using the + parser options with the same name. The two read-only features, + (http://xmlns.perl.org/sax/LexicalHandler, DeclHandler) return + 0 or 1 to indicate whether the parser supports these two interfaces. + ???XML:::SAX::Base + </change> + + <change id="C10" issue-ref="I13"> + The spec states explicitly that the value of input source Encoding property + has a higher priority than encoding specified in an XML declaration. + </change> + </change-list> <issue-list> - <issue id="I1" status="open" resolution="none" change-ref=""> + <issue id="I1" status="closed" resolution="applied" change-ref="C8"> <para> A parser should advertise SAX version it supports. There can be a new method ($parser->get_sax_version()) or a read-only feature @@ -71,7 +88,7 @@ </para> </issue> - <issue id="I2" status="open" resolution="none" change-ref=""> + <issue id="I2" status="closed" resolution="applied" change-ref="C9"> <para> "http://xml.org/sax/handlers/LexicalHandler" feature on the parser needs to be set to the object to receive lexical events currently. If @@ -93,13 +110,13 @@ </para> <para> Suggestion: LexicalHandler and DeclHandler are set using the - parser properties with the same name. The two read-only features, + parser options with the same name. The two read-only features, (http://xmlns.perl.org/sax/LexicalHandler, DeclHandler) return 0 or 1 to indicate whether the parser support these two interfaces. </para> </issue> - <issue id="I3" status="open" resolution="none" change-ref=""> + <issue id="I3" status="closed" resolution="denied" change-ref=""> <para> SAX 2.0 Ext. 1.1 has a new Attributes2 interface which extends attributes with new properties (Declared, Specified) to distinguish @@ -112,7 +129,7 @@ </para> </issue> - <issue id="I4" status="decided" resolution="applied" change-ref="C2"> + <issue id="I4" status="closed" resolution="applied" change-ref="C2"> <para> The parse() method is defined in different ways in the Basic and Advanced documents. @@ -122,7 +139,7 @@ </para> </issue> - <issue id="I5" status="open" resolution="none" change-ref=""> + <issue id="I5" status="closed" resolution="denied" change-ref=""> <para> All hash references could be replaced with blessed classes. Need to clarify what would be benefits of such change. @@ -132,14 +149,14 @@ </para> </issue> - <issue id="I6" status="decided" resolution="applied" change-ref="C3"> + <issue id="I6" status="closed" resolution="applied" change-ref="C3"> <para> Changes in attribute_decl eName, aName, Type, Mode (was ValueDefault), Value </para> </issue> - <issue id="I7" status="decided" resolution="applied" change-ref="C6"> + <issue id="I7" status="closed" resolution="applied" change-ref="C6"> <para> The effect of turning off namespace processing is unclear in Perl SAX. The spec should state that all namespace-related processing is skipped, @@ -152,7 +169,7 @@ </para> </issue> - <issue id="I8" status="decided" resolution="applied" change-ref="C7"> + <issue id="I8" status="closed" resolution="applied" change-ref="C7"> <para> Perl SAX should require explicitly all event data to be Unicode strings (to have the UTF-8 flag on). @@ -195,7 +212,7 @@ </para> </issue> - <issue id="I11" status="decided" resolution="applied" change-ref="C5"> + <issue id="I11" status="closed" resolution="applied" change-ref="C5"> <para> The specification should state explicitly what is meant be "streams", what are supported types for parse_file(): file handles, @@ -207,7 +224,7 @@ </para> </issue> - <issue id="I12" status="decided" resolution="applied" change-ref="C4"> + <issue id="I12" status="closed" resolution="applied" change-ref="C4"> <para> The spec should be more explicit about what a document locator is supposed to return. It could for example read: @@ -219,7 +236,7 @@ </para> </issue> - <issue id="I13" status="open" resolution="none" change-ref=""> + <issue id="I13" status="closed" resolution="applied" change-ref="C10"> <para> The value of the Encoding property of Input Sources should be able to override the encoding value specified in the xml declaration. The spec should state this @@ -229,7 +246,17 @@ Suggestion: to add the following text: If available, the value of Encoding property has a higher priority than encoding specified in an XML declaration. - + </para> + </issue> + + <issue id="I14" status="open" resolution="none" change-ref=""> + <para> + Parsers report an error when the parse() method is called and no input + source (Source option) is provided, regardless on the method's argument. + </para> + <para> + Suggestion: Parsers should try to call the parse_uri() with the provided + argument. Only if there is no argument available the error is issued. </para> </issue> Index: changes.css =================================================================== RCS file: /cvsroot/perl-xml/sax-perl-org/changes.css,v retrieving revision 1.3 retrieving revision 1.4 diff -u -d -r1.3 -r1.4 --- changes.css 11 Jan 2005 14:34:29 -0000 1.3 +++ changes.css 11 Feb 2005 09:05:25 -0000 1.4 @@ -7,17 +7,17 @@ background-color: #bbeeff; } -.open { +.none { border: solid 1px #999999; background-color: #ffbbbb; } -.decided { +.applied { border: solid 1px #999999; background-color: #bbffbb; } -.closed { +.denied { border: solid 1px #999999; - background-color: #bbbbff; + background-color: #bbbbbb; } Index: changes.xsl =================================================================== RCS file: /cvsroot/perl-xml/sax-perl-org/changes.xsl,v retrieving revision 1.2 retrieving revision 1.3 diff -u -d -r1.2 -r1.3 --- changes.xsl 11 Jan 2005 14:34:29 -0000 1.2 +++ changes.xsl 11 Feb 2005 09:05:25 -0000 1.3 @@ -23,14 +23,29 @@ API is in progress. Comments should be sent to Perl-XML mailing list (per...@li...). </p> + <b>Open issues</b> + <xsl:apply-templates select="chg:issue-list"/> <h2>Changes from Perl SAX 2.0</h2> <xsl:apply-templates select="chg:change-list/chg:change"/> - <h2>Summary of Issues</h2> + <h2>Issues</h2> <xsl:apply-templates select="chg:issue-list/chg:issue"/> </body> </html> </xsl:template> + <xsl:template match="chg:issue-list"> + <xsl:text>: </xsl:text> + <xsl:for-each select="chg:issue[@status='open']"> + <a href="#{@id}"> + <xsl:value-of select="@id"/> + </a> + <xsl:if test="position() != last()"> + <xsl:text>, </xsl:text> + </xsl:if> + </xsl:for-each> + <xsl:if test="not(chg:issue[@status='open'])">none</xsl:if> + </xsl:template> + <xsl:template match="chg:change"> <p class="change"> <b> @@ -54,7 +69,7 @@ </xsl:template> <xsl:template match="chg:issue"> - <p class="{@status}"> + <p class="{@resolution}"> <b> <xsl:text>Issue </xsl:text> <a name="{@id}"> Index: sax-2.1-adv.html =================================================================== RCS file: /cvsroot/perl-xml/sax-perl-org/sax-2.1-adv.html,v retrieving revision 1.5 retrieving revision 1.6 diff -u -d -r1.5 -r1.6 --- sax-2.1-adv.html 11 Jan 2005 14:34:29 -0000 1.5 +++ sax-2.1-adv.html 11 Feb 2005 09:05:25 -0000 1.6 @@ -168,19 +168,19 @@ </p> <p> - Also, Features are things that are supposed to be <strong>turned - on</strong>, and thus should normally be off by default, especially if - the parser doesn't support turning them off. Due to backward - compatibility problems, the one exception to this rule is the - "<tt>http://xml.org/sax/features/namespaces</tt>" Feature which is on by - default and which a number of parsers may not be able to turn off. Thus, - a parser claiming to support this Feature (and all SAX2 parsers must - support it) may in fact only support turning it on. See <a - href="sax-2.1.html#nsProcessing">Namespace Processing</a> for - more details. + Also, Features are things that are supposed to be <strong>turned + on</strong>, and thus should normally be off by default, especially if + the parser doesn't support turning them off. Due to backward + compatibility problems, the one exception to this rule is the + "<tt>http://xml.org/sax/features/namespaces</tt>" Feature which is on by + default and which a number of parsers may not be able to turn off. Thus, + a parser claiming to support this Feature (and all SAX2 parsers must + support it) may in fact only support turning it on. See <a + href="sax-2.1.html#nsProcessing">Namespace Processing</a> for + more details. </p> -<p> +<p>??? In addition to the Features described in the SAX spec itself, a number of new ones may be defined for Perl. An example of this would be http://xmlns.perl.org/sax/node-factory which @@ -192,7 +192,23 @@ </p> <p> - The following methods are used to get and set features: + The read-only <tt>http://xmlns.perl.org/sax/version</tt> feature is + used to advertise a version of Perl SAX supported by a driver. For + drivers supporting the version of Perl SAX described in this document, + <tt>$parser->get_feature('http://xmlns.perl.org/sax/version')</tt> must + return <tt>2.1</tt>. Drivers supporting earlier versions of Perl SAX + can return <tt>1.0</tt> or <tt>2.0</tt>. +</p> + +<p> + The features <tt>http://xml.org/sax/handlers/LexicalHandler</tt> and + <tt>http://xml.org/sax/handlers/DeclHandler</tt> advertise if a + driver supports optional lexical and declaration handlers. Their + values are either 1 or 0. +</p> + +<p> + The following methods are used to get and set features: </p> <p><a name="getFeature"/> @@ -237,8 +253,8 @@ feature name but cannot set the requested value. <p> - This method is also the standard mechanism for setting extended handlers, - such as "<code>http://xml.org/sax/handlers/DeclHandler</code>". +This method is also the standard mechanism for setting extended handlers, +such as "<code>http://xml.org/sax/handlers/DeclHandler</code>". </p> </dd></dl></p> @@ -276,7 +292,8 @@ <p>The public identifier is always optional: if the application writer includes one, it will be provided as part of the location -information.</p></dd> +information.</p> +</dd> <dt class="prop">SystemId</dt> <dd>The system identifier (URI) of this input source. @@ -288,9 +305,10 @@ connection to the URI only if there is no byte stream or character stream specified).</p> -If the application knows the character encoding of the object +<p>If the application knows the character encoding of the object pointed to by the system identifier, it can register the encoding -using the <tt>Encoding</tt> property.</dd> +using the <tt>Encoding</tt> property.</p> +</dd> <dt class="prop">ByteStream</dt> <dd>The byte stream for this input source. @@ -299,8 +317,9 @@ specified, but it will use a byte stream in preference to opening a URI connection itself.</p> -If the application knows the character encoding of the byte stream, it -should set the <tt>Encoding</tt> property.</dd> +<p>If the application knows the character encoding of the byte stream, it +should set the <tt>Encoding</tt> property.</p> +</dd> <dt class="prop">CharacterStream</dt> <dd>The character stream for this input source. @@ -315,17 +334,19 @@ character, or number of characters from it, use the perl core read() function. To get a single byte from it (or number of bytes), you can use sysread().</p> - </dd> <dt class="prop">Encoding</dt> <dd>The character encoding, if known. <p>The encoding must be a string acceptable for an XML encoding -declaration (see section 4.3.3 of the XML 1.0 recommendation).</p> +declaration (see section 4.3.3 of the XML 1.0 recommendation). +If provided, the value of Encoding property has a higher priority +than encoding specified in the XML declaration.</p> -This property has no effect when the application provides a character -stream.</dd> +<p>This property has no effect when the application provides a character +stream.</p> +</dd> </dl> <h2><a name="Handlers">SAX Handlers</a></h2> @@ -513,7 +534,10 @@ <p>This is an optional extension handler for SAX2 to provide information about DTD declarations in an XML document. XML readers are -not required to support this handler.</p> +not required to support this handler. +Readers supporting this handler have the +<tt>http://xml.org/sax/handlers/DeclHandler</tt> feature set to 1. +Otherwise, this feature has value 0.</p> <p>Note that data-related DTD declarations (unparsed entities and notations) are already reported through the DTDHandler interface.</p> @@ -522,14 +546,10 @@ handler, all of the events will occur between the <tt>start_dtd</tt> and the <tt>end_dtd</tt> events.</p> -<p>To set a separate DeclHandler for an XML reader, set the -"<tt>http://xml.org/sax/handlers/DeclHandler</tt>" Feature with the -object to received declaration events. If the reader does not support -declaration events, it will throw a <tt>XML::SAX::Exception::NotRecognized</tt> -or a <tt>XML::SAX::Exception::NotSupported</tt> when you attempt to register -the handler. Declaration event handlers on the default handler are -automatically recognized and used.</p> - +<p>To set a DeclHandler for an XML reader, use the DeclHandler +option of the reader constructor or parse()/parse_x() method. If the +reader does not support declaration events, it ignores the DeclHandler +option.</p> <p><a name="elementDecl"/> <dl><dt><b><tt class='function'>element_decl</tt></b>(<var>element</var>)</dt> @@ -827,19 +847,20 @@ <p>This is an optional extension handler for SAX2 to provide lexical information about an XML document, such as comments and CDATA section -boundaries; XML readers are not required to support this handler.</p> +boundaries; XML readers are not required to support this handler. +Readers supporting this handler have the +<tt>http://xml.org/sax/handlers/LexicalHandler</tt> feature set to 1. +Otherwise, this feature has value 0.</p> <p>The events in the lexical handler apply to the entire document, not just to the document element, and all lexical handler events must appear between the content handler's <tt>start_document()</tt> and <tt>end_document()</tt> events.</p> -<p>To set the LexicalHandler for an XML reader, set the Feature -"<tt>http://xml.org/sax/handlers/LexicalHandler</tt>" on the parser to -the object to receive lexical events. If the reader does not support -lexical events, it will throw a <tt>XML::SAX::Exception::NotRecognized</tt> or -a <tt>XML::SAX::Exception::NotSupported</tt> when you attempt to register the -handler.</p> +<p>To set a LexicalHandler for an XML reader, use the LexicalHandler +option of the reader constructor or parse()/parse_x() method. If the +reader does not support lexical events, it ignores the LexicalHandler +option.</p> <p><a name="startDTD"/> <dl><dt><b><tt class='function'>start_dtd</tt></b>(<var>dtd</var>)</dt> @@ -1021,8 +1042,5 @@ a Filter will be available from CPAN in the not distant future. </p> - -<div>$Revision$</div> -<div>$Date$</div> </body> </html> Index: sax-2.1-idx.html =================================================================== RCS file: /cvsroot/perl-xml/sax-perl-org/sax-2.1-idx.html,v retrieving revision 1.6 retrieving revision 1.7 diff -u -d -r1.6 -r1.7 --- sax-2.1-idx.html 11 Jan 2005 14:34:29 -0000 1.6 +++ sax-2.1-idx.html 11 Feb 2005 09:05:25 -0000 1.7 @@ -88,7 +88,7 @@ </div> <div class="item"> <a href="sax-2.1-adv.html?#getFeatures" target="cnt">get_features()</a> - </div>sax-2.1.html + </div> </div> <div class="box"> @@ -219,8 +219,7 @@ </div> </div> -<div>$Revision$</div> -<div>$Date$</div> +<div>Revision: 05-02-11</div> </body> </html> Index: sax-2.1.html =================================================================== RCS file: /cvsroot/perl-xml/sax-perl-org/sax-2.1.html,v retrieving revision 1.5 retrieving revision 1.6 diff -u -d -r1.5 -r1.6 --- sax-2.1.html 11 Jan 2005 14:34:29 -0000 1.5 +++ sax-2.1.html 11 Feb 2005 09:05:25 -0000 1.6 @@ -399,7 +399,5 @@ </ul> -<div>$Revision$</div> -<div>$Date$</div> </body> </html> |
