checkin of last changes for 2.9, mostly docs

[TestXSLT.git] / Distribution / readme.xml

diff --git a/Distribution/readme.xml b/Distribution/readme.xml
index 3b51ece..0fceb05 100644 (file)
--- a/Distribution/readme.xml
+++ b/Distribution/readme.xml
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="ISO-8859-1"?>
 
-<!-- $id$ -->
+<!-- $Id$ -->
 
 <readme>
 <title>Readme for TestXSLT</title>
@@ -27,16 +27,20 @@
 </description>
 
 <requirements>
-Mac OS X 10.2., Safari 1.0 must be installed on your system.
+Mac OS X 10.2. and Safari 1.0 must be installed on your system.
 </requirements>
 
 <history>
 
 <entry>
        <version>2.9</version>
-       <date>xx-SEP-2003</date>
-       <item>Added a tag scanner, resulting in much smarter tag completion, and a list of the currently open tags at the top of the editor.</item>
+       <date>08-SEP-2003</date>
+       <item>The highlight of this release is a new tag scanner, resulting in much smarter tag completion, and a list of the currently open tags at the top of the editor window. Check it out...</item>
+       <item>Reworked the GUI update code, thus improving the general responsiveness and performance of the application.</item>
        <item>Major internal cleanup regarding encodings. If a dropped/opened file has an XML declaration with encoding information, that will be used, both when reading and when saving out to the file again. Make sure you activate the corresponding option in BBEdit too. If no such declaration exists, the platform default will be used (i.e. Macintosh encoding). Also, the encoding of the result of the transformation is currently assumed to be what's declared in the declaration of the XSLT code. This means you cannot use a different encoding in the xsl:output element.</item>
+       <item>The fixed encoding issues also mean that xsl:include directives referring to file names with non-ascii characters work now, e.g. &lt;xsl:include href="gähn.xsl"/&gt;.</item>
+       <item>Added a new XSLT example, the first one to produce XSL-FO. It converts the readme.xml file to XSL-FO / PDF, so there are now three output formats for the readme.xml file: HTML, XSL-FO / PDF and RTF. As always, this is intended to get you started with learning XSLT and in this case also XSL-FO. An excellent introduction to the FO part is available at <url>http://www.ibiblio.org/xml/books/bible2/chapters/ch18.html</url></item>
+       <item>Fixed a bug which would prevent XSL-FO / PDF rendering to hang the application if images were used in the document.</item>
 
 </entry>