Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-Id: <4.3.1.2.20011207092543.02363bd0@pop.ma.ultranet.com> X-Sender: lhall AT pop DOT ma DOT ultranet DOT com X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Fri, 07 Dec 2001 09:27:07 -0500 To: "Gregory W. Bond" , cygwin AT cygwin DOT com From: "Larry Hall (RFK Partners, Inc)" Subject: Re: ghostscript binmode weirdness In-Reply-To: <3C104BFB.95F270CE@research.att.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" At 11:56 PM 12/6/2001, Gregory W. Bond wrote: >i cannot get ghostscript to generate non-corrupted pdf files unless >everything is happens on binmode mounts - is there no way that i can >force binmode treatment on a text mount? i've read and re-read the >cygwin manual and experimented with a zillion variations but nothing >seems to work > >i've isolated the problem to the point when ghostscript writes the pdf >file - if it writes the file to a textmode mount it is guaranteed to be >corrupted due to the translation of LF to CRLF - i can't seem to prevent >this from occurring even when the CYGWIN var is set to binmode prior to >launching any cygwin shell - i wish i could move all my mounts to >binmode but this will screw up too many other things - anyone have any >suggestions for me? Best suggestion - port ghostscript properly so that it always writes binary files where it needs to. Everything else is just a hack to avoid this eventuality... Good luck, Larry Hall lhall AT rfk DOT com RFK Partners, Inc. http://www.rfk.com 838 Washington Street (508) 893-9779 - RFK Office Holliston, MA 01746 (508) 893-9889 - FAX -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/