From: Chris Johnsen Date: Fri, 08 Jan 2010 21:14:31 GMT Subject: Re: Trouble with 'make prefix=/usr info' Message-ID: In-Reply-To: On 2010 Jan 6, at 06:32, Craig Moore wrote: > I've isolated the problem, and its coming from this command: > > ================================ > $ docbook2x-texi user-manual.xml --encoding=UTF-8 --to-stdout >> user-manual.texi++ > Usage: jw [] > where are: > -f|--frontend : Specify the frontend (source format) > (default is docbook) > -b|--backend : Specify the backend (destination > format) > (default is html) > -c|--cat : Specify an extra SGML open catalog > -n|--nostd: Do not use the standard SGML open > catalogs > -d|--dsl |default|none: Specify an alternate style sheet > (default is to use the default > stylesheet) > -l|--dcl : Specify an alternate SGML declaration > (usual ones like xml.dcl get detected > automatically) > -s|--sgmlbase : Change base directory for SGML > distribution > (usually /usr/share/sgml) > -p|--parser : Specify the parser if several are > installed > (jade or openjade) > -o|--output : Set output directory > -u|--nochunks: Output only one big file > (overrides the stylesheet settings) > -i|--include
: Specify a SGML marked section to > include > (should be marked as "ignore" in > the SGML text) > -w|--warning |list: Control warnings or display the > allowed warning types > -e|--errors |list: Control errors or display the allowed > error types > -h|--help: Print this help message and exit > -V : Set a variable > -v|--version: Print the version and exit > > $ docbook2x-texi --version > DocBook-utils version 0.6.14 (jw version 1.1) > ================================ > > As you can see, I'm using DocBook-utils version 0.6.14 (jw version > 1.1), and it doesn't list '--encoding=UTF-8 --to-stdout' in its > options list. I'm guessing I've got the wrong version or type > installed? Is there another which I should be using? > > Thanks for your help, > Craig > I have previously used docbook2texi from docbook2X 0.8.8 by setting DOCBOOK2X_TEXI for 'make info'. It needed a non-released patch to understand the combination of "--to- stdout" and "--encoding=", though: Alternatively, it is possible to work-around the failure of --stdout with a wrapper script, but the patch is easy enough to apply. -- Chris