public inbox for kawa@sourceware.org
 help / color / mirror / Atom feed
From: Per Bothner <per@bothner.com>
To: Sudarshan S Chawathe <chaw@eip10.org>
Cc: kawa <kawa@sourceware.org>
Subject: Re: Building documentation, chunkfast.xsl URL in doc/style/kawa.xsl
Date: Sun, 30 Apr 2017 18:54:00 -0000	[thread overview]
Message-ID: <b70fb911-f9f5-25b5-c0c8-41b91e3e8ae7@bothner.com> (raw)
In-Reply-To: <1488.1493577512@vereq.eip10.org>

On 04/30/2017 11:38 AM, Sudarshan S Chawathe wrote:

>> There should be a file $DPATH/html/chunkfast.xsl
> 
> Yes, there is
> 
>    /usr/share/xml/docbook/stylesheet/docbook-xsl/html/chunkfast.xsl
> 
> so that seems like the right thing.
> 
> 
> So, bottom line, the configure option should do the trick (although the
> canonical names thing is interesting).

Be aware that there are two sets of stylesheets: the newer DocBook 5 are
namespace-aware, and the olrder ones aren't.
Kawa requires the former.

On Fedora there is both:

lrwxrwxrwx.  1 root root   25 Jul  8  2016 xsl-ns-stylesheets -> xsl-ns-stylesheets-1.79.1
drwxr-xr-x. 28 root root 4096 Nov 16 15:23 xsl-ns-stylesheets-1.79.1
lrwxrwxrwx.  1 root root   22 Jul  8  2016 xsl-stylesheets -> xsl-stylesheets-1.79.1
drwxr-xr-x. 20 root root 4096 Nov 16 14:49 xsl-stylesheets-1.79.1

Kawa needs the xsl-ns-stylesheets ones.

Medium-term I'm hoping we can improve texinfo's makeinfo so we don't need DocBook.
There is a Google Summer of Code will should move us forwards in that respect.
-- 
	--Per Bothner
per@bothner.com   http://per.bothner.com/

  reply	other threads:[~2017-04-30 18:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-30 17:26 Sudarshan S Chawathe
2017-04-30 17:56 ` Per Bothner
2017-04-30 18:38   ` Sudarshan S Chawathe
2017-04-30 18:54     ` Per Bothner [this message]
2017-04-30 20:25       ` Sudarshan S Chawathe
2017-04-30 22:46         ` Per Bothner
2017-04-30 23:21           ` Sudarshan S Chawathe

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=b70fb911-f9f5-25b5-c0c8-41b91e3e8ae7@bothner.com \
    --to=per@bothner.com \
    --cc=chaw@eip10.org \
    --cc=kawa@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).