All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: Docs
Date: Thu, 31 Jan 2008 12:28:50 +0100	[thread overview]
Message-ID: <200801311228.51594.okuji@enbug.org> (raw)
In-Reply-To: <1201769188.10303.21.camel@solid.paris.klabs.be>

On Thursday 31 January 2008 09:46, Franklin PIAT wrote:
> After some thoughts, I'll release the documentation[1] I wrote, with
> copyright assignments to FSF, Dual licensed under GPL+GFDL.

Thank you very much.

> I wish I could have left it on a Wiki, then do docbook/xml export, then
> converting it to info+manpages...
>
> * But I guess it won't be possible if we need copyright assignments
>   from contributors (although I think it might be possible to make some
>   group based ACLs in Moinmoin wiki).

I (or maybe Marco as well?) can set up an ACL, if you wish.

> * What do you think about maintaining the documentation in docbook
>   then converting it to texinfo ? Would it fit FSF Coding style ?

Docbook is acceptable. In fact, it is used in some projects in GNU (such as 
GNOME, IIRC).

But I think the problem is mostly the reusability. I believe that we can reuse 
several parts of the GRUB manual (for GRUB Legacy) as they are, and this is 
in texinfo format.

>   I've had a deeper look at Texinfo : The specification are larger
>   that html (i don't have the time to learn it)... And I haven't
>   fount authoring tool, etc...

It looks big, only because the texinfo manual contains a lot of examples. In 
reality, much smaller than the Docbook spec. And, you know, HTML does not 
specify printing.

Anyway, the best way of using texinfo is to start from examples. In our case, 
you can copy the manual from GRUB Legacy, and tweak it. FYI, Emacs supports 
texinfo very well.

Okuji



  reply	other threads:[~2008-01-31 11:29 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-31  8:46 Docs Franklin PIAT
2008-01-31 11:28 ` Yoshinori K. Okuji [this message]
2008-01-31 12:50   ` Docs Robert Millan
2008-01-31 13:43     ` Docs Yoshinori K. Okuji
2008-01-31 14:34       ` Docs Robert Millan
2008-01-31 15:27         ` Docs Franklin PIAT
2008-02-11 19:34         ` Docs Franklin PIAT
2008-02-18 22:08   ` Docs Franklin PIAT
2008-02-20 21:28     ` Docs Yoshinori K. Okuji
2008-02-24 15:16       ` Docs Robert Millan
2008-02-25  7:43         ` Docs Franklin PIAT
2008-02-26 22:34           ` Docs Yoshinori K. Okuji
2008-03-01 17:33             ` Docs Yoshinori K. Okuji
2008-03-03  7:24               ` Docs Franklin PIAT
2008-02-26 22:32         ` Docs Yoshinori K. Okuji
  -- strict thread matches above, loose matches on Subject: below --
2013-03-22 12:37 docs Jerker Nyberg
2013-03-22 18:18 ` docs Dan Mick
2013-03-22 18:30   ` docs John Wilkins

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=200801311228.51594.okuji@enbug.org \
    --to=okuji@enbug.org \
    --cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.