--- "David Van Couvering (JIRA)" wrote: <snip> > > 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. > </snip>
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?
