public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sven Vermeulen <swift@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] Gentoo Documentation Project Status Update
Date: Thu, 13 Nov 2003 14:17:31 +0100	[thread overview]
Message-ID: <20031113131731.GA1530@gentoo.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2895 bytes --]

[ Sorry for the crosspost, I should've sent this to -dev immediately ]

This is the status of the Gentoo Documentation Project. It will be posted
regularly, but not with a static frequency. All questions can be posted to
gentoo-doc@gentoo.org or to me personally.

The Gentoo Documentation Project, from now on abbreviated to GDP, has its own
project page (just like almost all other Gentoo projects). You can find it at
http://www.gentoo.org/proj/en/gdp. 

This status mail will briefly discuss the following tasks, objectives and/or
projects related to the GDP:
  - Gentoo Handbook
  - PDF documentation
  - Non-gdp documentation
  - Packaged documentation
  - New supported languages

** Gentoo Handbook

  The first part of the Gentoo Handbook (Installing Gentoo) is finished and
  should be production ready. It is available online [1] and contains the
  installation instructions for almost all supported architectures (x86, ppc,
  sparc, hppa, alpha). I hope to extend it with the other architectures that are
  lurking (amd64, ia64, mips) when I receive more information about those.

  I will start with designing the second part pretty soon now. This part should
  contain the Gentoo-specific items for administering your system (Portage,
  initscripts, conf.d/env.d)

** PDF documentation

  Using FOP gives us the best results and can be perfectly integrated with our
  current GuideXML format (as it uses an XML format itself, XML-FO). The
  resulting transformation of our x86 installation guide can be found at my
  dev-page [2]. 

  I am now working on a script to have the transformation (GuideXML -> PDF) done
  on the server-level so that everything can be automated. 

** Non-GDP documentation

  We have started with the cluster project documentation and are integrating it
  in our documentation tree. Other documentation (and projects) should follow
  soon.

** Packaged documentation

  After a discussion [3] we came to the agreement that it is not beneficial to
  provide a package for our documentation. If a user wants the Gentoo
  documentation somewhere on his disk, (s)he should use wget, like this:
    wget --recursive --level=1 1 --no-parent --page-requisites --convert-link \
      --no-host-directories --html-extension \
      http://www.gentoo.org/doc/en/index.xml

** New supported languages

  The Danish language is now an officially supported language, and the Greek
  language volunteers have stepped up and are "in training".


[1] http://www.gentoo.org/doc/en/handbook/handbook.xml
[2] http://emu.gentoo.org/~swift/gentoo-x86-install.pdf
[3] http://article.gmane.org/gmane.linux.gentoo.documentation/619


-- 
 ^__^   And Larry saw that it was Good.
 (oo)                                      Sven Vermeulen
 (__)   http://www.gentoo.org              Gentoo Documentation Project

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2003-11-13 13:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-13 13:17 Sven Vermeulen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-11-24 14:06 [gentoo-dev] Gentoo Documentation Project Status Update Sven Vermeulen
2004-01-17 17:22 Sven Vermeulen
2004-02-19 20:05 Sven Vermeulen
2004-03-09 10:42 Sven Vermeulen
2004-05-03 13:13 Sven Vermeulen
2004-09-24 20:58 Sven Vermeulen
2004-10-21 11:28 Sven Vermeulen
2004-11-21 11:51 Sven Vermeulen

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=20031113131731.GA1530@gentoo.org \
    --to=swift@gentoo.org \
    --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