Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 82440 invoked from network); 18 Jun 2005 07:09:32 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 18 Jun 2005 07:09:32 -0000 Received: (qmail 79628 invoked by uid 500); 18 Jun 2005 07:09:31 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 79591 invoked by uid 500); 18 Jun 2005 07:09:30 -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 79578 invoked by uid 99); 18 Jun 2005 07:09:30 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 18 Jun 2005 00:09:29 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [206.190.37.123] (HELO web81606.mail.yahoo.com) (206.190.37.123) by apache.org (qpsmtpd/0.29) with SMTP; Sat, 18 Jun 2005 00:09:03 -0700 Received: (qmail 87018 invoked by uid 60001); 18 Jun 2005 07:09:07 -0000 Message-ID: <20050618070907.87016.qmail@web81606.mail.yahoo.com> Received: from [63.201.229.2] by web81606.mail.yahoo.com via HTTP; Sat, 18 Jun 2005 00:09:07 PDT Date: Sat, 18 Jun 2005 00:09:07 -0700 (PDT) From: Jeff Levitt Subject: [website] (was "Re: [jira] Commented: (DERBY-310) Document and/or change Derby client code to match behavior with Embedded driver where possible.") To: Derby Development In-Reply-To: <813364375.1119055157652.JavaMail.jira@ajax.apache.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N --- "David Van Couvering (JIRA)" wrote: > > Hm. I am uncomfortable going out with the release > when the HTML is so clunky. I don't know how hard > it is to set up a css file, but it seems like if > we're trying to get people interested in using > Derby, having docs that look funky does not send out a good message to interested but hesitant new users. > So this got me into sort of an investigative mode, and I took a look at the html that is output by the DITA toolkit transform. It seems there IS a css file that these files point to, but they cant find it since its not in the directory. The name of the file they all point to is commonltr.css. So, I searched through the DITA toolkit package, and I found the file in the DITA-OT1.0.1\resource\ directory. When I copied that file into the directory with my output html files and reloaded the output in my browser, suddenly everything changed formatting. The problem was it didn't change the one issue you pointed out, which was that the spacing around a table caption was non-existent, and the font of those table captions was normal text, so you couldnt distinguish it from the surrounding text. Well, after playing with the css file, I finally figured out how to modify it so that the captions are bold and are spaced with margins around them. It looks a lot better and I think you'll be satisfied with the results. So what I suggest is that we fix the website to place the commonltr.css file into each manual's html output directory. However, we should use my modified one so that the tables look better. I have attached it to this email. If this is something we can do, can a committer do this for us so that the nightly builds he change?