From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] manpages for everything
Date: Sat, 9 Feb 2008 17:00:05 +0100 [thread overview]
Message-ID: <20080209160005.GA19212@thorin> (raw)
In-Reply-To: <20080209131610.GA26503@nubol.oskuro.net>
On Sat, Feb 09, 2008 at 02:16:10PM +0100, Jordi Mallach wrote:
> On Sat, Feb 09, 2008 at 11:30:42AM +0100, Robert Millan wrote:
> > > desc=`$prefix/bin/$program --help | sed -n '2s/.*-- //p'`
> > > $help2man -N -i debian/mangen.inc -s 1 -S FSF -n "$desc" $prefix/bin/$program >$program.1
> > Do we need $desc/-n ? It looks like a workaround for a limitation in help2man
> > (or for some oddness in mailutils output).
>
> If I remember correctly, the default description in help2man manpages is
> a generic one, not useful at all.
>
> readmsg --help gives me:
> jordi@nubol:~$ readmsg --help
> Forma d'ús: readmsg [OPCIÓ...]
> GNU readmsg -- mostra missatges
>
> I extract the "show messages part" from this and use it as the
> description.
>
> I now found a bug report: #368628. In short, I think we need this here
> too.
I see. Well, I didn't do the $dest part this time since I'm short in time atm.
:-/
> Not for now. When we do have utils translations, the tricky part will be
> assuring the --help output is translated, or it'll be of little use, or
> will be half in English, half translated, etc. So we'd have to make some
> kind of rule, like "only generate l10n'd manpages if the po is up to
> date and 100% translated".
Ok.
--
Robert Millan
<GPLv2> I know my rights; I want my phone call!
<DRM> What use is a phone call… if you are unable to speak?
(as seen on /.)
next prev parent reply other threads:[~2008-02-09 16:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-08 21:29 [PATCH] manpages for everything Robert Millan
2008-02-09 0:17 ` Robert Millan
2008-02-09 3:02 ` Jordi Mallach
2008-02-09 10:30 ` Robert Millan
2008-02-09 13:16 ` Jordi Mallach
2008-02-09 16:00 ` Robert Millan [this message]
2008-02-09 12:30 ` Robert Millan
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=20080209160005.GA19212@thorin \
--to=rmh@aybabtu.com \
--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.