From: Randy Dunlap <rdunlap@xenotime.net>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] docbook: use ID as filename
Date: Wed, 30 Jun 2010 15:58:12 -0700 [thread overview]
Message-ID: <20100630155812.ff25e97a.rdunlap@xenotime.net> (raw)
In-Reply-To: <1277920855.7823.12.camel@jlt3.sipsolutions.net>
On Wed, 30 Jun 2010 20:00:55 +0200 Johannes Berg wrote:
> From: Johannes Berg <johannes.berg@intel.com>
>
> I'm trying to generate a <set> of <book>s in
> docbook for wireless to link together all the
> cfg80211 and mac80211 documentation.
>
> However, docbook will generate "re01.html"
> anew for each book for the first <refentry>,
> presumably due to a bug in the stylesheets.
>
> An effective workaround is to use IDs for the
> filenames, which makes them more descriptive
> as well, e.g. API-enum-ieee80211-band.html.
>
> Cc: Randy Dunlap <rdunlap@xenotime.com>
> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
> ---
> Documentation/DocBook/stylesheet.xsl | 1 +
> 1 file changed, 1 insertion(+)
>
> --- wireless-testing.orig/Documentation/DocBook/stylesheet.xsl 2010-06-30 19:57:19.000000000 +0200
> +++ wireless-testing/Documentation/DocBook/stylesheet.xsl 2010-06-30 19:57:23.000000000 +0200
> @@ -6,4 +6,5 @@
> <param name="callout.graphics">0</param>
> <!-- <param name="paper.type">A4</param> -->
> <param name="generate.section.toc.level">2</param>
> +<param name="use.id.as.filename">1</param>
> </stylesheet>
>
>
> --
Applied to my patch queue. We'll see if it trips up anything.
Thanks.
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
prev parent reply other threads:[~2010-06-30 22:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-30 18:00 Johannes Berg
2010-06-30 22:58 ` Randy Dunlap [this message]
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=20100630155812.ff25e97a.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®