Treating it as data is fine with me -- however, when file can't figure out what it is, there is a problem, as I do check for file type with ifhp and it will refuse unrecognized file types.
As you can see from the files below, vi appears to have halved the contents of the file -- I'm assuming that the file after vi is done is no longer usable. Perhaps this question is now becoming one that is more for the "file" mailing list, but I had said that I would post the files in question regardless. The curious thing is that file, AFAIK, looks at the beginning of a file. vi would not likely be changing the beginning of the first line of the file that signals PCL data, so it doesn't make sense that it would have an effect on that (not to me, anyway). Also interesting is that this printer doesn't seem to use PJL prior to its PCL stream, which is odd from my experience. Here is the URL: http://www.umdnj.edu/~novosirj/PCL-data-problem ---- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | | Ryan Novosielski - Jr. UNIX Systems Admin |$&| |__| | | |__/ | \| _| | [EMAIL PROTECTED] - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent. | IST/ACS - NJMS Medical Science Bldg - C630 On Wed, 25 Jun 2003, Villy Kruse wrote: > On Tue, 24 Jun 2003, Ryan Novosielski wrote: > > > Date: Tue, 24 Jun 2003 18:09:24 -0400 (EDT) > > From: Ryan Novosielski <[EMAIL PROTECTED]> > > Reply-To: [EMAIL PROTECTED] > > To: [EMAIL PROTECTED] > > Subject: Re: LPRng: Problem with 'file' > > > > There is a LOT different. The most noticeable seems to be the outputs of > > cmp -l in the first column are about 2-3 times larger than the second one. > > I'm guessing maybe vi chopped some long lines, if that's what those > > numbers are? Why would ifhp care? > > > > In any case, I'm going to produce a set of small df's to post and see what > > the consensus is... this is driving me /nuts/. > > > > Standard unix vi chops all binary zeroes, and yes, you do get > problems with long lines as well. In my experience print data from > MS-Windows should be treated as binary data, and any modifications > inclusing stripping or inserting CR characters tend to produce garbage. > Postscript data, however, can normaly be treated as text files without > too much problems. > > > Villy > > > ----------------------------------------------------------------------------- > YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST > The address you post from MUST be your subscription address > > If you need help, send email to [EMAIL PROTECTED] (or lprng-requests > or lprng-digest-requests) with the word 'help' in the body. For the impatient, > to subscribe to a list with name LIST, send mail to [EMAIL PROTECTED] > with: | example: > subscribe LIST <mailaddr> | subscribe lprng-digest [EMAIL PROTECTED] > unsubscribe LIST <mailaddr> | unsubscribe lprng [EMAIL PROTECTED] > > If you have major problems, send email to [EMAIL PROTECTED] with the word > LPRNGLIST in the SUBJECT line. > ----------------------------------------------------------------------------- > ----------------------------------------------------------------------------- YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST The address you post from MUST be your subscription address If you need help, send email to [EMAIL PROTECTED] (or lprng-requests or lprng-digest-requests) with the word 'help' in the body. For the impatient, to subscribe to a list with name LIST, send mail to [EMAIL PROTECTED] with: | example: subscribe LIST <mailaddr> | subscribe lprng-digest [EMAIL PROTECTED] unsubscribe LIST <mailaddr> | unsubscribe lprng [EMAIL PROTECTED] If you have major problems, send email to [EMAIL PROTECTED] with the word LPRNGLIST in the SUBJECT line. -----------------------------------------------------------------------------
