Re: on changing fop documentation sources to markdown
The Web Maestro <[email protected]>
| Newsgroups | gmane.comp.apache.commons.general,gmane.text.xml.batik.devel |
|---|---|
| Message-ID | <CANooF-jkAzOkr60=r=Zo+uv5uTCMOdzQy0yigCQ8LoxzLA39vA__13649.3617705584$1335387764$gmane$org@mail.gmail.com> |
On Sat, Apr 21, 2012 at 9:42 AM, Clay Leeds <[email protected]>wrote: > On Apr 20, 2012, at 1:36 AM, Pascal Sancho <[email protected]> > wrote: > > But there has to be a better way. Can we, as a start, change the CSS file > xmlgraphics.css so it doesn't have body {color: white;}? > > > Note that I have to be very patient when editing the (very long) > compliance page directly, since it is rendered directly in the preview > pane. Don't try it if your processor is a little out of age (;-| > > > [1] http://www.apache.org/dev/cmsref.html#markdown > > Thanks again for the assistance! > > Clay I've committed a change to the CSS, which at least makes it black text on white background (white on white is difficult to read unless you're a wizard!). We'll still need to figure out a solution for the coloring and such... We should be able to come up with some solution... If nothing else, we could always commit an HTML file, but we need to find a method to make it so the CMS doesn't replace it or something silly... Hand editing all the lines in that file just doesn't seem efficient!