From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-38093-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 21340 invoked by alias); 4 Mar 2016 15:09:04 -0000
Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Workers List <zsh-workers.zsh.org>
List-Post: <mailto:zsh-workers@zsh.org>
List-Help: <mailto:zsh-workers-help@zsh.org>
X-Seq: 38093
Received: (qmail 22045 invoked from network); 4 Mar 2016 15:09:03 -0000
X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.1
X-AuditID: cbfec7f4-f79026d00000418a-12-56d9a50a8b5c
Date: Fri, 04 Mar 2016 15:08:52 +0000
From: Peter Stephenson <p.stephenson@samsung.com>
To: "zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: Re: zsh manual - missing bookmarks in pdf file?
Message-id: <20160304150852.4b4bfe08@pwslap01u.europe.root.pri>
In-reply-to: <DD8312A1-802E-40AB-BDCB-DB13CDAF2ED1@kba.biglobe.ne.jp>
References: <22229.42616.86422.222557@lwm.klanderman.net>
 <DE24867B-712C-46A4-85B4-BDD290E91154@kba.biglobe.ne.jp>
 <87vb55leop.fsf@lwm.klanderman.net>
 <194AAF32-4EB5-412D-A200-27AE7832EF86@kba.biglobe.ne.jp>
 <87egbs7usn.fsf@lwm.klanderman.net>
 <1850B214-73A8-4373-A9AE-0C533702A6CD@kba.biglobe.ne.jp>
 <87si07lj6s.fsf@lwm.klanderman.net>
 <36FD86DF-3BA9-4277-B587-38EC212BDDEB@kba.biglobe.ne.jp>
 <CAHYJk3Tp0i4xFYrM0OsTNGE8vBEbFgPAaS9J9q6EpW7obSkq-Q@mail.gmail.com>
 <DD8312A1-802E-40AB-BDCB-DB13CDAF2ED1@kba.biglobe.ne.jp>
Organization: Samsung Cambridge Solution Centre
X-Mailer: Claws Mail 3.7.9 (GTK+ 2.22.0; i386-redhat-linux-gnu)
MIME-version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7bit
X-Brightmail-Tracker:
 H4sIAAAAAAAAA+NgFrrELMWRmVeSWpSXmKPExsVy+t/xK7pcS2+GGTxfI25xsPkhkwOjx6qD
	H5gCGKO4bFJSczLLUov07RK4Mra172AqmMRSMXliJ3sD4zrmLkZODgkBE4n5C9YzQdhiEhfu
	rWfrYuTiEBJYyihx5N5TFghnBpPE12W3mSGc04wSR1d+h8qcYZS486gVrJ9FQFXiyYEXYHPZ
	BAwlpm6azQhiiwjoS1z8cwvMFhawkLjQ2wRWzytgL/Hu5l6wOKeAq8T953sYIYbOZJHo23aX
	DSTBD9R89e8nqAPtJWZeOcMI0Swo8WPyPRYQm1lAS2LztiZWCFteYvOat2BHCAmoS9y4u5t9
	AqPwLCQts5C0zELSsoCReRWjaGppckFxUnquoV5xYm5xaV66XnJ+7iZGSEh/2cG4+JjVIUYB
	DkYlHt4bDdfDhFgTy4orcw8xSnAwK4nw7pp1M0yINyWxsiq1KD++qDQntfgQozQHi5I479xd
	70OEBNITS1KzU1MLUotgskwcnFINjDnLVrSzzneZerby7o/vP9OyDXmTPtiqJ11R8ww0v8Qc
	wGb6nc1dXzJaZUvP8Z16qUmtepe/79ooOv8tn6b6sT7nqbc9K791OMkdk7SwXbx+xrFGy+u3
	1tzIsl9gtiawLvY6/59pLUenLDpyMPXbvkOrjl19+S1g/vX3Z71maAsGCvJPdX4x77YSS3FG
	oqEWc1FxIgBrUmuoZQIAAA==

On Fri, 4 Mar 2016 23:25:40 +0900
Jun T. <takimoto-j@kba.biglobe.ne.jp> wrote:
> The patch includes a possible fix for this, but is it really
> necessary to check for pdfetex? Since texi2dvi checks for
> pdfetex by itself, probably PDFTEX=$(PDFETEX) is not necessary.
> Or it may be there for a (very) old texi2dvi?

It probably was originally there for older versions of texi2dvi, but
that doesn't mean it's necessarily still needed.  We have prepackaged
documentation for systems that can't keep up with tools.

pws