[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: experimental release of linuxdoc-tools (based on sgml-tools 1.0.9)
- To: "Greg Ferguson" <[email protected]>
- Subject: Re: experimental release of linuxdoc-tools (based on sgml-tools 1.0.9)
- From: Adam Di Carlo <[email protected]>
- Date: 17 May 2000 10:43:27 -0400
- Cc: Taketoshi Sano <[email protected]>, [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
- In-reply-to: "Greg Ferguson"'s message of "Wed, 17 May 2000 09:27:48 -0400"
- References: <[email protected]> <[email protected]> <[email protected]> <[email protected]>
- Resent-date: Wed, 17 May 2000 10:44:48 -0400 (EDT)
- Resent-from: [email protected]
- Resent-message-id: <AU42ID.A.9sD.fArI5@murphy>
- Resent-sender: [email protected]
- Sender: [email protected]
- User-agent: Gnus/5.0803 (Gnus v5.8.3) Emacs/20.5
"Greg Ferguson" <[email protected]> writes:
> I'd like to see if we can get linuxdoc support into the v2
> sgml-tools packages. We'd need to provide the DTD and a
> set of DSSSL stylesheets along with perhaps a couple of
> catalog files.
Um, I don't think linuxdoc *has* a DTD or DSSSL files.
OTOH, SGMLtools Lite or whatever *could* support sgmltools v1 or
linuxdoc tools or whatever it is called. Supposing that software is
already installed, all it would have to do is provide the capability
to wrap around the linuxdoc scripts with it's own 'sgmltools' wrapper.
If anyone wants to do this, apply as a developer at sourceforge.
> Do you think we should go that route? That way we have 1
> toolset (jade/openjade), with support for both DTDs (DocBook
> and Linuxdoc).
I approve of one tool which is extensible -- it's name is sgmltools
lite, now a days. I object to the idea of merging the linuxdoc
perl/ASP or whatever it is back into the sgmltools lite package.
--
.....Adam Di [email protected].....<URL:http://www.onShore.com/>
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]