You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@xalan.apache.org by dl...@locus.apache.org on 2000/01/21 22:19:15 UTC
cvs commit: xml-xalan STATUS DONE BUGS
dleslie 00/01/21 13:19:15
Modified: . STATUS DONE BUGS
Log:
Removed files no longer needed and revised xml source files so
they can use StyleBook.
Revision Changes Path
1.7 +10 -10 xml-xalan/STATUS
Index: STATUS
===================================================================
RCS file: /home/cvs/xml-xalan/STATUS,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -r1.6 -r1.7
--- STATUS 2000/01/11 22:55:06 1.6
+++ STATUS 2000/01/21 21:19:15 1.7
@@ -1,15 +1,15 @@
<s3 title="Things still to be done">
<p>We still need to do the following:</p>
<ul>
- <li><p>Switch from Makefile et.al. to an Ant-based system (contact: shane_curcur@lotus.com working on).</p></li>
- <li><p>Create a simple 'minitest' so anyone can verify very basic
- functionality of Xalan. (shane_curcuru@lotus.com working on).</p></li>
- <li><p>Have more regular builds, synched with Xerces builds.</p></li>
- <li><p>attribute:: and child:: (ChildOrAttributeAxisSpecifier) in patterns are not
- yet implemented.</p></li>
- <li><p>The main focus for the next release (0.19.2, and upcoming 0.19.3) will be performance.</p></li>
- <li><p>Extensions need further work to become more robust and less confusing.</p></li>
- <li><p>Beyond this, and a few other minor conformance issues, the goal is to
- reach a level of stability that can be tagged as a 1.0.0 release.</p></li>
+ <li>Switch from Makefile et.al. to an Ant-based system (contact: shane_curcur@lotus.com working on).<br/><br/></li>
+ <li>Create a simple 'minitest' so anyone can verify very basic
+ functionality of Xalan. (shane_curcuru@lotus.com working on).<br/><br/></li>
+ <li>Have more regular builds, synched with Xerces builds.<br/><br/></li>
+ <li>attribute:: and child:: (ChildOrAttributeAxisSpecifier) in patterns are not
+ yet implemented.<br/><br/></li>
+ <li>The main focus for the next release (0.19.2, and upcoming 0.19.3) will be performance.<br/><br/></li>
+ <li>Extensions need further work to become more robust and less confusing.<br/><br/></li>
+ <li>Beyond this, and a few other minor conformance issues, the goal is to
+ reach a level of stability that can be tagged as a 1.0.0 release.<br/><br/></li>
</ul>
</s3>
1.8 +9 -9 xml-xalan/DONE
Index: DONE
===================================================================
RCS file: /home/cvs/xml-xalan/DONE,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- DONE 2000/01/11 22:52:27 1.7
+++ DONE 2000/01/21 21:19:15 1.8
@@ -1,14 +1,14 @@
<s3 title="Bug fixes since the last version">
<p>Bugs (SPR ID and Description) fixed since version 0.19.1:</p>
<ul>
-<li><p>MMIY4ELLNZ Error reporting mechanism needs major improvements.</p></li>
-<li><p>PDIK4ELNRC Outp tests 19,20,21,22,23 now failing to output xml headers w/ different encodings.</p></li>
-<li><p>PDIK4ELPBD Document()'s error resources should be in XSLT not XPATH.</p></li>
-<li><p>PDIK4ELSE3 Entref01: value-of is not passing "&" thru to result output file.</p></li>
-<li><p>SCUU4ELPRP TestThreads: running processors on multiple threads throws exceptions.</p></li>
-<li><p>SCUU4ELPWT Samples do not compile from LotusXSL distribution.</p></li>
-<li><p>SCUU4ELRSG Xalan's samples\pipe does not appear to work from end-user perspective.</p></li>
-<li><p>PDIK4ESQA5 LRE attribute creation will include nodes with names in the XSLT namespace.</p></li>
-<li><p>PDIK4ESQEF Both forms of exclude-result-prefixes fail to suppress the default namespace - #default.</p></li>
+<li>MMIY4ELLNZ Error reporting mechanism needs major improvements.<br/><br/></li>
+<li>PDIK4ELNRC Outp tests 19,20,21,22,23 now failing to output xml headers w/ different encodings.<br/><br/></li>
+<li>PDIK4ELPBD Document()'s error resources should be in XSLT not XPATH.<br/><br/></li>
+<li>PDIK4ELSE3 Entref01: value-of is not passing "&" thru to result output file.<br/><br/></li>
+<li>SCUU4ELPRP TestThreads: running processors on multiple threads throws exceptions.<br/><br/></li>
+<li>SCUU4ELPWT Samples do not compile from LotusXSL distribution.<br/><br/></li>
+<li>SCUU4ELRSG Xalan's samples\pipe does not appear to work from end-user perspective.<br/><br/></li>
+<li>PDIK4ESQA5 LRE attribute creation will include nodes with names in the XSLT namespace.<br/><br/></li>
+<li>PDIK4ESQEF Both forms of exclude-result-prefixes fail to suppress the default namespace - #default.<br/><br/></li>
</ul>
</s3>
1.6 +23 -23 xml-xalan/BUGS
Index: BUGS
===================================================================
RCS file: /home/cvs/xml-xalan/BUGS,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -r1.5 -r1.6
--- BUGS 2000/01/12 13:21:53 1.5
+++ BUGS 2000/01/21 21:19:15 1.6
@@ -1,29 +1,29 @@
<s3 title="Known bugs">
<p>We are aware of the following bugs (SPR ID# and description):</p>
<ul>
-<li><p>SCUU4EMMUC ValidateXPath sample throws exception with illegal xpath</p></li>
-<li><p>PDIK4ERNDJ Errors messages are overly verbose, can they be simplified.</p></li>
-<li><p>PDIK4ERPLJ $x="foo" does not mean the same as not($x!="foo")</p></li>
-<li><p>DMAN4ESS98 Sort with data-type="number" should only rearrange numbers.</p></li>
-<li><p>PDIK4ESTEB exclude-result-prefixes, should not apply to any included/imported stylesheets</p></li>
-<li><p>DMAN4ETPTK case-order attribute apparently ignored in xsl:sort</p></li>
-<li><p>PDIK4ETKTJ Attribute value template does not parse.</p></li>
-<li><p>PDIK4ETPCT xsl:element name attribute should generate error if result from the AVT is not a QName.</p></li>
-<li><p>PDIK4EUNA6 "xsl:element" created element does not acquire namespace prefixes from stylesheet.</p></li>
-<li><p>PDIK4EUQN6 LRE with namespace prefixed QName attribute(ped:attr) does not pass attribute to result tree.</p></li>
-<li><p>PDIK4EYP2U Parameters are not evaluated by XPATH expressions correctly.</p></li>
-<li><p>PDIK4F7PZC Should we generate namespaces if it's set to ""</p></li>
-<li><p>PDIK4F7QUC attribute name is accepting an invalid QName and "xmlns" as valid names.</p></li>
-<li><p>PDIK4F7TP5 Using sort with position() fails.</p></li>
-<li><p>PDIK4F8N4Y "xsl:elements" elements are not getting copy of namespace nodes from element node.</p></li>
-<li><p>PDIK4F9L5Q Problems with whitespace stripping in stylesheet.</p></li>
-<li><p>PDIK4F9PTP Customer problem. Attempt to create DOM output w/o creating root node first, crashes.</p></li>
-<li><p>PDIK4F9QVX URL encoding should escape the space character as '%20'.</p></li>
-<li><p>PDIK4FBMT8 document not extracting a document with different encoding.</p></li>
-<li><p>DMAN4FEPC5 Some xsl:sort attributes must reject bad keyword values</p></li>
-<li><p>DMAN4FERJ3 Number format patterns should act the same whether 1 or 2 patterns</p></li>
-<li><p>DMAN4FFQBJ Need correct URL in system-property</p></li>
-<li><p>SCUU4ELPVP Performance: XT is often faster than LotusXSL</p></li>
+<li>SCUU4EMMUC ValidateXPath sample throws exception with illegal xpath<br/><br/></li>
+<li>PDIK4ERNDJ Errors messages are overly verbose, can they be simplified.<br/><br/></li>
+<li>PDIK4ERPLJ $x="foo" does not mean the same as not($x!="foo")<br/><br/></li>
+<li>DMAN4ESS98 Sort with data-type="number" should only rearrange numbers.<br/><br/></li>
+<li>PDIK4ESTEB exclude-result-prefixes, should not apply to any included/imported stylesheets<br/><br/></li>
+<li>DMAN4ETPTK case-order attribute apparently ignored in xsl:sort<br/><br/></li>
+<li>PDIK4ETKTJ Attribute value template does not parse.<br/><br/></li>
+<li>PDIK4ETPCT xsl:element name attribute should generate error if result from the AVT is not a QName.<br/><br/></li>
+<li>PDIK4EUNA6 "xsl:element" created element does not acquire namespace prefixes from stylesheet.<br/><br/></li>
+<li>PDIK4EUQN6 LRE with namespace prefixed QName attribute(ped:attr) does not pass attribute to result tree.<br/><br/></li>
+<li>PDIK4EYP2U Parameters are not evaluated by XPATH expressions correctly.<br/><br/></li>
+<li>PDIK4F7PZC Should we generate namespaces if it's set to ""<br/><br/></li>
+<li>PDIK4F7QUC attribute name is accepting an invalid QName and "xmlns" as valid names.<br/><br/></li>
+<li>PDIK4F7TP5 Using sort with position() fails.<br/><br/></li>
+<li>PDIK4F8N4Y "xsl:elements" elements are not getting copy of namespace nodes from element node.<br/><br/></li>
+<li>PDIK4F9L5Q Problems with whitespace stripping in stylesheet.<br/><br/></li>
+<li>PDIK4F9PTP Customer problem. Attempt to create DOM output w/o creating root node first, crashes.<br/><br/></li>
+<li>PDIK4F9QVX URL encoding should escape the space character as '%20'.<br/><br/></li>
+<li>PDIK4FBMT8 document not extracting a document with different encoding.<br/><br/></li>
+<li>DMAN4FEPC5 Some xsl:sort attributes must reject bad keyword values<br/><br/></li>
+<li>DMAN4FERJ3 Number format patterns should act the same whether 1 or 2 patterns<br/><br/></li>
+<li>DMAN4FFQBJ Need correct URL in system-property<br/><br/></li>
+<li>SCUU4ELPVP Performance: XT is often faster than LotusXSL<br/><br/></li>
</ul>
<p>The format-number function sometimes behaves incorrectly when the second argument (pattern-string) has two sub-patterns for positive and negative numbers. You may find that you do not get a minus sign on negative numbers. You can either avoid using the second pattern or insert a literal minus sign at the front of the second pattern. If you choose the latter, you will have to re-edit the pattern when we fix the problem. There may also be incorrect behavior if you set the zer0-digit to a different character.</p>
</s3>