[ http://issues.apache.org/jira/browse/DERBY-384?page=all ]
Jeff Levitt updated DERBY-384:
------------------------------
Attachment: derby384.diff
The attached patch makes the changes requested in this doc review. I have
created sample output on my own site:
HTML files: http://derby.mylevita.com/tuning/
PDF: http://derby.mylevita.com/tuning/tuningderby.pdf
The patch affects EVERY dita file, but not the content for each file. This is
because I modified the year in the dita source file copyrights for each file
from "2004" to "2005". So while every file is listed in the patch, the only
changes that will appear in the PDF and HTML files are those requested in this
doc review.
For references to ToursDB, I have replaced them with sample, but I doubt the
examples would work against the samples database. Since I didn't have examples
to replace all of the toursDB examples, my main concern was making sure the
code would work; not necessarily whether they would work in a specific db. It
would be nice later on to get some examples for many of these sections that
would work in the sample db.
Also, note that I have made the change to the trademarks page in the same way
that I did to the Getting Started guide patch in
http://issues.apache.org/jira/browse/DERBY-379.
> Doc Review (CLOSED TO FURTHER COMMENTS): Tuning Derby
> -----------------------------------------------------
>
> Key: DERBY-384
> URL: http://issues.apache.org/jira/browse/DERBY-384
> Project: Derby
> Type: Improvement
> Components: Documentation
> Environment: all
> Reporter: Jeff Levitt
> Priority: Minor
> Fix For: 10.1.1.0
> Attachments: derby384.diff
>
> This issue tracks comments for the manual known as Tuning Derby. The deadline
> for posting comments was Tuesday, June 28, noon Pacific time.
> PLEASE DO NOT POST ADDITIONAL COMMENTS TO THIS JIRA ISSUE. If you have
> additional comments, please open a JIRA issue for a fixin in a future
> release, as there is not enough time to incorporate additional comments.
> Some guidelines to follow when posting comments to this issue are:
> - Try to make clear and concise comments about what you want changed whenever
> possible. Provide concrete comments that say "Please change <original> to
> <modified>" instead of generic comments like "This section needs to be
> rewritten."
> - If you're reviewing the HTML Files copy, include the URL for the page in
> the review comment. Obtain the URL like this:
> * highlight the topic in the left frame
> * right click
> * choose "Properties"
> * copy and paste the address in the pop up box.
> - If you're reviewing the PDF copy, in the review comment:
> * Include the page number for the PDF, and indicate whether the number is
> the PDF sheet number or the printed page number.
> * Include the title of the section that the problem occurs in. If it's in
> a subsection, try to include the hierarchy of titles.
> - Please don't review the HTML Book copy -- it'll be time consuming to match
> up that copy with the underlying DITA source.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
