From: "Gregory W. Bond" <bond@research.att.com>
To: "Larry Hall (RFK Partners, Inc)" <lhall@rfk.com>
Cc: cygwin@cygwin.com
Subject: Re: ghostscript binmode weirdness
Date: Fri, 07 Dec 2001 07:55:00 -0000 [thread overview]
Message-ID: <3C10E38F.4879178D@research.att.com> (raw)
In-Reply-To: <4.3.1.2.20011207092543.02363bd0@pop.ma.ultranet.com>
thanks for the reply larry - i realize that fixing the ghostscript port would
be a solution, but my impression from reading the cygwin user manual is that
setting CYGWIN to binmode could serve as a workaround - in my case it didn't
and i don't understand why - i'm beginning to suspect that cygwin is ignoring
that i've set CYGWIN to binmode which would be a cygwin bug
"Larry Hall (RFK Partners, Inc)" wrote:
> 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@rfk.com
> RFK Partners, Inc. http://www.rfk.com
> 838 Washington Street (508) 893-9779 - RFK Office
> Holliston, MA 01746 (508) 893-9889 - FAX
--
Gregory W. Bond
AT&T Labs - Research
180 Park Avenue, Rm. D273, Bldg. 103
P.O. Box 971, Florham Park, NJ, 07932-0971, USA
tel: (973) 360 7216 fax: (973) 360 8187
--
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/
next prev parent reply other threads:[~2001-12-07 15:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-06 21:06 Gregory W. Bond
2001-12-07 6:31 ` Larry Hall (RFK Partners, Inc)
2001-12-07 7:55 ` Gregory W. Bond [this message]
2001-12-07 8:14 ` Corinna Vinschen
2001-12-09 13:40 Gregory W. Bond
2001-12-09 13:45 ` Robert Collins
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3C10E38F.4879178D@research.att.com \
--to=bond@research.att.com \
--cc=cygwin@cygwin.com \
--cc=lhall@rfk.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).