Re: [Tuxpaint-devel] [fwd] tuxpaint print bug on Brother HL 2700 CN
An award-winning drawing program for children of all ages
Brought to you by:
wkendrick
From: Micah J. C. <mi...@co...> - 2006-08-23 17:27:10
|
(Replying to myself) On Fri, Aug 18, 2006 at 06:40:29PM -0700, Micah J. Cowan wrote: > ...After doing some reading, AFAICT I was wrong about BoundingBox being > required: it would seem that this is probably not the cause of problems > on the user's printer. As it turns out, I was only /partially/ wrong about BoundingBox being required. It is in fact required if the document is an EPS. If we remove the EPSF bit from the first line, then it's not required. The extra six bytes for "image\n" is also a potential trouble spot, as we already discussed. And, in reading over parts of the PSRM again, I also found that it is highly recommended to include the line "%%EndProlog" in your document, even if you don't put anything in your prolog section. Actually, although the description of %%Begin(End)Prolog says you "should" include the line, section 4 says that conforming documents "must" include it (and, to be kosher, we should probably include the %%BeginProlog as well). I've posted a tarball to the Ubuntu bug description at https://launchpad.net/distros/ubuntu/+source/tuxpaint/+bug/49079 with various test files for the user to attempt printing. It includes the original, the original stripped of DSC comments, the original minus the EPSF stuff, and the original, minus the EPSF stuff and with an adjusted byte-count to include the "image\n". (I didn't consider the prolog stuff until after I'd posted the tarball.) Hopefully the user will test this out and give us some much-needed data; regardless, though, I think addressing the three areas of trouble above should probably improve the portability of tuxpaint's output. Thanks for taking the time to look into this, Albert. -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer... http://micah.cowan.name/ |