Is there a bug in file-5.05?

arubin · 05-25-2011, 01:21 PM

I have just found a solution to a problem with a Brother printer. It seems that file 5.05 was not recognising the postscript produced by the filters and was sending the postscript to the printer as text. This was solved by downgrading file to 5.04

Of course the bug could be in the Brother drivers rather than file. Has anyone else had any problems with file?

business_kid · 05-27-2011, 04:16 AM

Check the first few characters. If you print to file with open office, you should see

Quote:

%!PS-Adobe-3.0
%%BoundingBox: (atend)
%%Creator: (OpenOffice.org 3.2)

and file-5.05 in slackware reports

Quote:

test.ps: PostScript document text conforming DSC level 3.0, Level 3

arubin · 05-27-2011, 05:25 AM

I found this in an Arch forum

Quote:

For what it's worth, I've been having the same problem on my gentoo box.* It seems that one of the CUPS filters (pstops) appends 0x0a04 to postscript files; this causes file to break, and thus the Brother filters think they're getting raw text that should be printed.