Re: Debian SGML/XML packages (was Package wanted: libxml-grove-perl)
As a Debian user who toys with notions of someday maintaining packages,
I think this is a great idea. I'd find it immensely useful. Especially
if the collection of information included:
1. all the various packages that can do something useful with the SGML
source (like Jade)
2. pointers to "howto" style documentation for the whole Debian SGML
experience. By that I mean -- don't limit the scope to SGML authoring
or data storage. Anything relating to translation of SGML to anything
else should be fair game.
It seems like Debian has a lot to offer in this area, but I think a
centralized information repository would help someone like me a lot,
having no SGML/XML experience at all.
Jesse
On 06/14/99 at 18:53:09, Ardo van Rangelrooij wrote concerning "Debian SGML/XML packages (was Package wanted: libxml-grove-perl)":
> All this made me think about putting together a web page listing all
> the current XML Perl modules, whether they are debianized and by who,
> which are their dependencies, etc. This makes it easier to track what
> needs to be done, etc.
>
> We could even extend this into a set of web pages listing all the SGML
> and XML packages (and even those that are not yet) available in Debian,
> links to other SGML/XML sites, etc. In other words, continueing where
> the announcement from Adam Di Carlo titled "Debian Touts Integrated
> SGML Environment" on debian-announce on March 30 "left off".
>
> Further, we could even setup a debian-sgml-xml mailing list to discuss
> related issues. Adam also has been thinking about a "Debian/SGML(/XML?)
> Tutorial", but he's (too? ;-) busy. Maybe we can help out here. Again
> in other words, we could make Debian really become _the_ SGML and XML
> platform of choice. Of course, this takes time, but we at least could
> give it a start.
>
> Thanks,
> Ardo
--
Jesse Jacobsen, Pastor jjacobsen@jvlnet.com
Grace Lutheran Church (ELS) http://www.jvlnet.com/~jjacobsen/
Madison, Wisconsin GnuPG public key ID: 2E3EBF13
"These words are my own, and do not necessarily represent my employer."
Reply to: