X-Spam-Check-By: sourceware.org Message-ID: Date: Thu, 12 Jan 2006 19:59:26 -0800 From: Joshua Daniel Franklin To: cygwin AT cygwin DOT com Subject: Re: Errors building the FAQ/User's Guide (Attn: xmlto maintainer)? In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: inline References: X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id k0D3xY4N016820 On 1/12/06, Igor Peshansky wrote: > On Thu, 12 Jan 2006, Joshua Daniel Franklin wrote: > > I build everything but the PDFs on Cygwin. Is your issue related to > > http://www.cygwin.com/ml/cygwin-apps/2005-10/msg00065.html > > I.e., you have docbook-xml42 installed? It might help to send info as at > > http://www.cygwin.com/problems.html > > And indeed it was. Installing the various docbook-xml* packages let me > build off the net without hacking xmlto. Thanks. I could've sworn I took > care of it back in October, but looks like it slipped through the cracks. > > There might still be utility in controlling whether or not the build is > network-aware via xmlto parameters (at the moment, there is no way to turn > off the --nonet option). I should submit a feature request at some point. Might be an upstream issue, too. I haven't looked at the Cygwin-specific xmlto patches if there are any. > Did you happen to take a look at the FAQ rewording I proposed > ()? Was > cygwin-patches the correct list for it, or should it have been sent here? That was the right place, I'm just a little behind. I've applied it. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/