From: Tim Waugh <twaugh@redhat.com>
To: docbook-tools-discuss@sources.redhat.com
Subject: Re: Wishlist: docbook2man and translated manpages
Date: Sun, 28 Jul 2002 11:09:00 -0000 [thread overview]
Message-ID: <20020728190927.N28686@redhat.com> (raw)
Message-ID: <20020728110900.CXDfN6wk0GWLJATWSkZ4KmcSet2gBeYZpMXxFC59LqM@z> (raw)
In-Reply-To: <87ptxfoieg.fsf@falcon.wanadoo.fr>; from marillat.christian@wanadoo.fr on Mon, Jul 22, 2002 at 06:07:51PM +0200
[-- Attachment #1: Type: text/plain, Size: 999 bytes --]
On Mon, Jul 22, 2002 at 06:07:51PM +0200, Christian Marillat wrote:
> Hi,
>
> http://bugs.debian.org/153091
>
> With translated manpages it is not uncommon to have
> foo.sgml foo.es.sgml foo.fr.sgml foo.it.sgml ...
> in the same directory. As docbook2man generates foo.1 for all these
> files, it is not very convenient. Moreover dh_installman is able to
> handle translated manpages whose name looks like foo.<xx>.1
> So it would be nice if docbook2man did generate foo.<xx>.1 instead
> of foo.1.
Yes, that would be useful.
> A partial patch is attached to the bug report (not tested)
The problem with the patch is that it uses $LANG to determine the
language that the document is written in---unfortunately, it just
tells us the language that the current user is using, not the
languange used by the document author. For that, we must use the
current value of the 'lang' attribute. (That way a single document
could contain all of the translations.)
Tim.
*/
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2002-07-28 18:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-20 19:23 Christian Marillat
2002-07-22 9:07 ` Christian Marillat
2002-12-20 19:23 ` Tim Waugh [this message]
2002-07-28 11:09 ` Tim Waugh
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=20020728190927.N28686@redhat.com \
--to=twaugh@redhat.com \
--cc=docbook-tools-discuss@sources.redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).