Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 48283 invoked from network); 29 Jun 2005 07:44:06 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 29 Jun 2005 07:44:06 -0000 Received: (qmail 36271 invoked by uid 500); 29 Jun 2005 07:44:04 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 36231 invoked by uid 500); 29 Jun 2005 07:44:03 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Development" Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 36093 invoked by uid 99); 29 Jun 2005 07:44:02 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [192.87.106.226] (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Jun 2005 00:44:01 -0700 Received: from ajax.apache.org (ajax.apache.org [127.0.0.1]) by ajax.apache.org (Postfix) with ESMTP id A7AF113 for ; Wed, 29 Jun 2005 09:43:58 +0200 (CEST) Message-ID: <760219839.1120031038685.JavaMail.jira@ajax.apache.org> Date: Wed, 29 Jun 2005 09:43:58 +0200 (CEST) From: "Jeff Levitt (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Updated: (DERBY-379) Doc review (CLOSED TO FURTHER COMMENTS): Getting Started with Derby In-Reply-To: <1692017180.1119310278962.JavaMail.jira@ajax.apache.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/DERBY-379?page=all ] Jeff Levitt updated DERBY-379: ------------------------------ Attachment: derby379.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/getstart/ PDF: http://derby.mylevita.com/getstart/getstartderby.pdf A couple of items to note: 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. I also made some changes to the trademarks page (The last section in the manual). This page listed trademarks for other companies. While the Microsoft, Sun, and Open Group trademarks appeared normal, the IBM tradmarks were in a table that was not appearing. It didn't make sense to be placing the IBM trademarks in a table while the other companies were not, so I deleted the table and rewrote the IBM trademarks in a sentence just like the others. Please see: http://derby.mylevita.com/getstart/rgstrademderby.html (you can compare it to our existing page: http://incubator.apache.org/derby/docs/getstart/rgstrademderby.html While the table currently shows up fine in that HTML link, it does not appear in the current PDF's) This page appears the same in all 6 books, so I would also apply this change to the docs in each of their respective doc review patches. I think this section needs to be carefully reviewed with the rest of the changes made in this patch, as this is legal information concerning multiple companies and should not be taken lightly. > Doc review (CLOSED TO FURTHER COMMENTS): Getting Started with Derby > -------------------------------------------------------------------- > > Key: DERBY-379 > URL: http://issues.apache.org/jira/browse/DERBY-379 > Project: Derby > Type: Improvement > Components: Documentation > Environment: all > Reporter: Jeff Levitt > Priority: Minor > Fix For: 10.1.1.0 > Attachments: derby379.diff > > This issue tracks comments for the Getting Started with Derby manual. 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 to " 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