X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Date: Fri, 20 Aug 2010 11:43:37 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: Cygwin: texi2dvi stumbles over texinfo.tex Message-ID: <20100820154337.GB844@ednor.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Fri, Aug 20, 2010 at 08:00:14AM -0400, Steve Holden wrote: >On 8/20/2010 7:53 AM, Steve Holden wrote: >> On 8/20/2010 5:29 AM, Reuben Thomas wrote: >>> On Thu 25 May 2006, Karl Berry wrote: >>> >>>> This line in fmtutil.cnf indicates the problem: >>>> >>>> etex pdfetex language.def -translate-file=cp227.tcx *etex.ini >>>> >>>> Either (1) the second word should be changed to "etex", or >>>> (2) it should be arranged for "etex" in invoke pdfetex instead of etex. >>>> E.g., make "etex" a link to pdfetex, instead of its own binary. >>>> >>>> We do (2) for TeX Live. >>> >>> Please could this fix be applied? I just ran into the same problem, >>> four years later, and I'm not the only one since then (I notice >>> another thread from 2007). >>> >> We don't need no stinkin' issue tracker. >> >It struck me that this remark might be ambiguous, or even be regarded as >offensive by some. I found it tedious actually, and wondered if you were going to now start jumping up and down in every message where it seems remotely possible that an "issue tracker" was the "solution" to a problem. cgf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple