public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: AGottinger@t-online.de (Achim Gottinger)
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Gentoo Linux documentation
Date: Sat Mar 17 11:31:02 2001	[thread overview]
Message-ID: <3AB3A707.47576446@gottinger.de> (raw)
In-Reply-To: 20010316144831.B3538@cvs.gentoo.org

drobbins@gentoo.org wrote:
> 
> Hi All,
> 
> In a few days, we're going to start an official documentation rampage, lasting
> about a week.  Hopefully, in that time, we can get a whole bunch of
> documentation done and on the website.  Fortunately, I'm writing an article for
> IBM on the website redesign, so I can devote some time to documentation.
> However, this does mean that our doc solution will be scrutinized by the world,
> but I figured we're up to the task.
> 
> For a refresher, this is what everybody seems to be in agreement upon:
> 
> 1. The documentation should be composed in XML.
> 2. We should use XSLT to translate the XML documentation into web-ready HTML.
> 
> However, we still haven't decided which XML approach to use:
> 
> a. Use our own custom "guide" format designed for our needs
> b. Use the already complete docbook format for our XML
> 
> In my eyes, the advantage of a custom guide format is that it is much easier to
> change/upgrade if we need new features, and is definitely going to have a
> simpler, more HTML-like syntax.
> 
> The advantage of the docbook format is that it's a standard (for technical
> documentation), and has a lot of features.  The downside of this is that we are
> less in control of the format and we will need to learn the "docbook way" of
> doing things.  Another concern about docbook -- since it has a lot more tags
> than our lightweight guide format, writing docbook --> HTML XSL transforms could
> be *very* cumbersome, since we will have to support all docbook tags :(  This
> appears to be the major drawback to docbook -- its DTD is *huge*.

There is a lite version of docbook which is not that huge.
I'm currently making packages for the docbook-xml-dtd's and
docbook(-lite) xsl's.
You should be able to test them in a few hours.

It's true docbook transformation need much time with these xsl's. But
since we do not use dynamic XML generation time should not be the
problem.

Another thing. I want to make two new categories:

- app-spell: (for i/a/pspell, their backendsand the dictionaries.
- app-ml: for all the xml/sgml/html whatever ml stuff.

Or should ml be a new major categorie with ml-apps and ml-libs
subcategories?
Then we can put stuff like libwww, libxslt, libxml in ml-libs. And
things like
jade, sablotron, and all the sgml-tools to ml-apps.

achim~



> 
> example docbook XML:
> 
> /usr/portage/app-doc/gentoo-doc/files/install.docbook
> 
> example guide (beta) XML:
> 
> /usr/portage/app-doc/gentoo-web/files/xml/install.xml
> 
> --
> Daniel Robbins                                  <drobbins@gentoo.org>
> President/CEO                                   http://www.gentoo.org
> Gentoo Technologies, Inc.
> 
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://www.gentoo.org/mailman/listinfo/gentoo-dev



  parent reply	other threads:[~2001-03-17 18:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-16 14:49 [gentoo-dev] Gentoo Linux documentation drobbins
2001-03-16 15:35 ` S. Murthy Kambhampaty
2001-03-16 17:36   ` drobbins
2001-03-17 11:31 ` Achim Gottinger [this message]
2001-03-17 13:06   ` Achim Gottinger
2001-03-17 15:50     ` Achim Gottinger
2001-03-17 17:13   ` drobbins
2001-03-17 17:30     ` Achim Gottinger
2001-03-17 20:08   ` drobbins
2001-03-19 15:16     ` Achim Gottinger
2001-03-20  0:14       ` Achim Gottinger
2001-03-20  3:16         ` Achim Gottinger
2001-03-20 21:19           ` Achim Gottinger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3AB3A707.47576446@gottinger.de \
    --to=agottinger@t-online.de \
    --cc=gentoo-dev@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox