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

> 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.

That is a good catch; thanks!

> 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.

Debian too seems to have both (and both are installed on my system, not
sure if that's the default): packages are docbook-xsl and
docbook-xsl-ns.

So based on the above, the correct path to give to configure's
--with-docbook-stylesheets option on Debian would be

  /usr/share/xml/docbook/stylesheet/docbook-xsl-ns

To test it all, I just did a fresh build starting from git pull and
everything worked great, except for building kawa.pdf.

The 'make' also built kawa-manual.epub by default, which I'm guessing is
a side effect of using the --with-docbook-stylesheets option, as I don't
recall that happening on my earlier builds.  I was also able to build
the "fancy" and "plain" HTML docs properly.

The only minor problem seems to be building kawa.pdf, which is likely
something outdated on my system. I did use a newish version of texinfo
(6.3) since I know that's needed by Kawa.  Not sure if it's worth
chasing, but I'm including the error from 'make kawa.pdf' (in the doc
subdirectory) below for reference.

Regards,

-chaw


  [163] [164] [165]
  ../../../.././kawa.texi:8889: Argument of @parseargline has an extra }.
  <inserted text> 
                 @par 
  <to be read again> 
                     }
  @next ...required-arg}|@stxref  {guard})@sup  {*}}
                                                    @futurelet @next @smartita...
  l.1 ...s  {required-arg}|@stxref {guard})@sup {*}}
                                                    @texinfoc
  @scanmacro ...atspaces }@scantokens {#1@texinfoc }
                                                    @aftermacro 
  l.1 ...uired-arg}|@stxref {guard})@sup{*}@texinfoc
                                                    
  ...
  l.8889 ...{(@stxref{required-arg}|@stxref{guard})}
                                                     [@stxlit{#!optional} @stx...
  
  ?

  reply	other threads:[~2017-04-30 20:25 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
2017-04-30 20:25       ` Sudarshan S Chawathe [this message]
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=10604.1493583901@vereq.eip10.org \
    --to=chaw@eip10.org \
    --cc=kawa@sourceware.org \
    --cc=per@bothner.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).