dleslie 99/12/16 08:53:41
Modified: docs readme.xml
Log:
Added info about set MAKE_MODE=UNIX
Revision Changes Path
1.5 +4 -57 xml-xalan/docs/readme.xml
Index: readme.xml
===================================================================
RCS file: /home/cvs/xml-xalan/docs/readme.xml,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- readme.xml 1999/12/08 17:11:36 1.4
+++ readme.xml 1999/12/16 16:53:41 1.5
@@ -185,63 +185,10 @@
idref="RedirectDoc"/> for details.</p>
</s2>
- <s2 title="Version Notes">
- <s3 title="Not Yet Implemented">
- <p>This section will give you an idea of what has yet to be
implemented.</p>
- <ul>
- <li>For number formatting, we don't yet handle the
letter-value,
- digit-group-sep, and n-digits-per-group, and
sequence-src attributes. Also,
- internationalization support for number is not
yet all that hot.<p/> </li>
- <li> xsl:locale is not yet implemented.<p/> </li>
- </ul>
- </s3>
- <s3 title="Known Bugs">
- <ul>
- <li>Not properly implemented: "The html output method
should escape
- non-ASCII characters
in URI attribute values
- as recommended in
Section B.2.1 of the HTML
- 4.0
Recommendation."<p/></li>
- <li>Not properly implemented: "The html output method
should add a META element
- immediately after the
start-tag of the HEAD element
- specifying the
character encoding actually used."<p/></li>
- <li>-html will have problems when using the
xsl-stylesheet PI, for various reasons.<p/></li>
- <li>Specifying the encoding in &xsl:output
encoding="xxx"/> will have problems
- when using the command line, when using the
xsl-stylesheet PI instead of
- separately specifying a stylesheet.<p/></li>
- <li>The doctype declaration is not being output as the
first thing
- in the output document... comments and the like can precede
it.<p/></li>
- <li>There's a bug reported that xsl:strip-space isn't
working, but we
- haven't been able to reproduce this to
date.<p/></li>
- <li>Need to do: If a input document has multiple
xsl-stylesheet PIs, act accordingly,
- piping the output of the first stylesheet as the input of the
next.<p/></li>
- <li>Encoding using ISO-8859-8 doesn't seem to be
working properly.<p/></li>
- </ul>
- </s3>
- <s3 title="Features and Enhancements To Do">
- <p>There are lots of potential features that will be going
into the
- draft. Rather than trying to enumerate these, lets
enumerate what we plan to do
- that is not driven by the w3c draft.</p>
- <ul>
- <li> Performance is an ongoing task.... <p/></li>
- <li> Work on incremental rendering via transformations
as the
- source tree is arriving.<p/> </li>
- <li> XSL Tutorial!<p/> </li>
- <li> We want to put in an editor's interface, for use
by XML/XSL
- editors. This would (1) allow a stream
interface on the result-tree DOM, and
- (2) allow structural changes in the source tree
to be incrementally updated in
- the result tree, with proper events thrown,
etc.<p/> </li>
- <li> Directly related to the above item, a Rule
Locator (for want
- of better term). This needs to be able to
locate closest matching rules for
- actions when a given source node changes, for
editing situations. This is easy
- when only patterns are used, but harder when
selects and modes are used. May
- require some special interfacing to the output
DOM.<p/> </li>
- <li> Better internationalization.<p/> </li>
- <li> Better documentation. <p/></li>
- </ul>
- </s3>
- <s3 title="Changes Since Last Version">
- &list0_19_0;
- </s3>
+ <s2 title="Version Notes">
+ &done;
+ &status;
+ &bugs;
</s2>
<s2 title="Contact Info and Bug Reports">
