On 22.12.2006 13:29:19 Simon Pepping wrote: > I edited the release notes, made some changes to the upgrading and > changes documents. > > I position this new release as the stable release. Version 0.20.5 is > now advertised the previous release. This is apparent in various > texts, esp. in the release notes and in 0.93/index.html, and in the > redirects in .htaccess. > > Specifically, I made the following changes: > > Added to the changes: > <action context="Code" dev="BD" type="add"> > Added support for the use of Open Type fonts > </action> > <action contect="Code" dev="JM" type="update"> > Enabled Copy/Paste from PDF content in Acrobat Reader for text using > embedded TrueType fonts. > </action>
Wasn't me. I've corrected the entry. > Removed from the known issues in release notes: > <li> > Copy/Paste from PDF content in Acrobat Reader is not supported for > text using embedded TrueType fonts. > </li> > <li> > Block-level content in fo:inlines may produce unwelcome results. > </li> > <li> > White space on direct inline-level children of a marker is not > handled correctly. > </li> > compare with the change entry: > <action context="Code" dev="AD" type="fix"> > Deferred property resolution for markers until they are actually > retrieved, > which leads to percentages and relative font-sizes now getting the > correct > values. Also deferred white-space-handling for markers. > </action> > > Uncertain status. The linked bug is resolved, but the description does > not match the description of the bug: > <li> > Omitting fo:table-column or having fo:table-column without a > column-width > and attempting to create columns implicitly from the first > table row is not implemented, yet (<a > href="http://issues.apache.org/bugzilla/show_bug.cgi?id=35656";>Bugzilla > #35656</a>). > </li> All the combinations here seem to work. > The possibility to do without font metrics files is only mentioned in > the changes file. > > Please, review. > > When I execute Ant's docs target, forrest insists on building a > linkmap.html file with 0.92 and trunk. I cannot find out where that is > derived from. Doesn't happen here. Try a clean build. > The only thing that remains is copying changes in the 0.93 directory > of the documentation to the trunk directory. And respond to your > remarks and edits, of course. Then this branch is ready for tagging > and release. I target the release to 2 January 2007. That means that > the vote will take place next week. Wonderful! Thanks so much. > Regards, Simon > > On Wed, Dec 20, 2006 at 01:13:02PM +0100, Simon Pepping wrote: > > I created the documentation for version 0.93 (see > > src/documentation/content/xdocs/0.93) and edited it for the new > > release version. Please, check it. Especial attention is needed for > > the new release notes, src/documentation/content/xdocs/relnotes.xml, > > most of which still have to be written, the FAQ, > > src/documentation/content/xdocs/faq.xml, the main page of this > > release, src/documentation/content/xdocs/0.93/index.xml, and the > > upgrading page, src/documentation/content/xdocs/0.93/upgrading.xml. > > -- > Simon Pepping > home page: http://www.leverkruid.eu Jeremias Maerki
