discuss: stylesheets
Subject:
Re: stylesheets
From:
Poet/Joshua Drake ####@####.####
Date:
22 Mar 2001 18:07:17 -0000
Message-Id: <Pine.LNX.4.30.0103220958170.16861-100000@crazypenguins.commandprompt.com>
Hello,
We have also done our own work here at Command Prompt on the style sheets.
We have added things like underline and made our print fonts Arial etc...
J
On Thu, 22 Mar 2001, Greg Ferguson wrote:
> > -----Original Message-----
>> From: David Merrill ####@####.####
>> Sent: Thursday, March 22, 2001 8:44 AM
>> To: ldp-discuss
>> Subject: stylesheets
>>
>> Hey,
>>
>> Would it be feasible, and is everyone willing to talk to the kdp and
>> the gdp about merging our stylesheets? I took a look at what they're
>> using, and I don't see any problems but I am no expert at stylesheets.
>
>I think we can probably get to a common stylesheet *base* but we
>need still look into project-specific extensions.
>
>I believe the gdp uses a CSS1 stylesheet reference for HTML docs
>created with their DSSSL extension. We probably wouldn't want to
>use their CSS1 file without modifications.
>
>Also, we need to look at anything that might adversly effect
>the use of article v. book containers (probably a non-issue, but
>it's something to consider); since we concentrate pretty heavily
>on tailoring for article.
>
>I've looked at the gdp DSSSL extension; even borrowed from it.
>They've done a nice job. I can't speak for the others as I
>haven't seen them.
>
>(Nik's description of the freebsd extentions was interesting.)
>
>This would be a good topic for a documentation summit, or a
>working group w/reps from each project. Something like that...
>
>r,
>Ferg
>
>_________________________
>http://list.linuxdoc.org/
>
--
--
<COMPANY>CommandPrompt - http://www.commandprompt.com </COMPANY>
<PROJECT>OpenDocs, LLC. - http://www.opendocs.org </PROJECT>
<PROJECT>LinuxPorts - http://www.linuxports.com </PROJECT>
<WEBMASTER>LDP - http://www.linuxdoc.org </WEBMASTER>
--
Instead of asking why a piece of software is using "1970s technology,"
start asking why software is ignoring 30 years of accumulated wisdom.
--
