From: Sven Vermeulen <swift@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] Gentoo Documentation Project Status Update
Date: Mon, 24 Nov 2003 15:06:25 +0100 [thread overview]
Message-ID: <20031124140625.GA1681@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2652 bytes --]
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:
- Supported languages
- PDF documentation
- GuideXML Update
- Gentoo Handbook
- WYSIWYG editor
- Stylesheets
** Supported languages
The Danish translations are fully integrated in the documentation project. Their
documentation can be found at http://www.gentoo.org/doc/da/index.xml. We welcome
broeman and Aaby to our team :)
Dertobi123 has also joined our team as new lead translator for the German
language. He has taken over Pylon's position. We ofcourse also welcome
dertobi123 aboard :)
** PDF documentation
As is mentioned in previous status mails, we will create PDFs using FOP.
However, development of the script is on a hiatus until the new infrastructure
design is ready to be deployed (namely having webnodes sync from a master
webnode instead of from the gentoo cvs server).
** GuideXML Update
The GuideXML format, used to develop the documentation, has been extended with
the possibility to identify chapters or sections so that internal references are
dealt with more easily. More information on this can be found at [1]
** Gentoo Handbook
The part on "Installing Gentoo" is now the official source for installation
instructions. The "older" installation guides are still maintained though up
until the new Gentoo Linux comes out.
** WYSIWYG editor
ian@gentoo.org is working on a (GPL'd) tool that allows editors to create
documents through a webbased WYSIWYG editor. Currently it works but lacks some
necessary features, such as 100% GuideXML compliance, and the use of the Coding
Style. However, the project looks very promising. Certainly one to keep an eye
on :)
** Stylesheets
The guide-print.xsl style has been updated so that the printable versions of our
documentation is really printable. Before, a margin was left unprinted,
rendering the "printer friendly" feature useless.
[1] http://article.gmane.org/gmane.linux.gentoo.documentation/688
Wkr,
Sven Vermeulen
--
^__^ 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 --]
next reply other threads:[~2003-11-24 14:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-24 14:06 Sven Vermeulen [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-11-21 11:51 [gentoo-dev] Gentoo Documentation Project Status Update Sven Vermeulen
2004-10-21 11:28 Sven Vermeulen
2004-09-24 20:58 Sven Vermeulen
2004-05-03 13:13 Sven Vermeulen
2004-03-09 10:42 Sven Vermeulen
2004-02-19 20:05 Sven Vermeulen
2004-01-17 17:22 Sven Vermeulen
2003-11-13 13:17 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=20031124140625.GA1681@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