You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-commits@db.apache.org by Apache Wiki <wi...@apache.org> on 2006/04/17 23:07:46 UTC

[Db-derby Wiki] Trivial Update of "DocFixes" by JeffLevitt

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Db-derby Wiki" for change notification.

The following page has been changed by JeffLevitt:
http://wiki.apache.org/db-derby/DocFixes

------------------------------------------------------------------------------
- Documentation is easy enough to work on, but there exists aneed for improvement to the PDF generation and the overall presentation of our documentation in general. It seems to me that a useful project would be for a student to examine the stylesheets, transforms, and css files that govern these items in the ASL version of the Open DITA Toolkit that we use for docs and work on the backend to improve them. Number one on that list would be to implement indexes in our PDF's. Number 2 might be a master index, either in PDF or html. Number three might be the overall presentation of the html documentation, as well as the single-file html transform that we currently use. It would be ideal to have a student here that could work on this because the people who actualy work on the documentation do not have any programming backgrounds, even if its just XSL.
+ Documentation is easy enough to work on, but there exists a need for improvement to the PDF generation and the overall presentation of our documentation in general. It seems to me that a useful project would be for a student to examine the stylesheets, transforms, and css files that govern these items in the ASL version of the Open DITA Toolkit that we use for docs and work on the backend to improve them. Number one on that list would be to implement indexes in our PDF's. Number 2 might be a master index, either in PDF or html. Number three might be the overall presentation of the html documentation, as well as the single-file html transform that we currently use. It would be ideal to have a student here that could work on this because the people who actualy work on the documentation do not have any programming backgrounds, even if its just XSL.