in reply to Re: Corrupted data problem in copyResampled using GD.pm
in thread Corrupted data problem in copyResampled using GD.pm

Better yet, just binmode THUMB; anyways, don't bother with the check. It only affects those operating systems it matters on.
  • Comment on Re: Re: Corrupted data problem in copyResampled using GD.pm

Replies are listed 'Best First'.
Corrupted data problem in copyResampled using GD.pm
by brianviehland (Initiate) on Feb 10, 2004 at 21:23 UTC
    I know that $opsys is setting correctly. I use it instead of $^O because it sets some other variables in the script as well as this.

    The amount of corruption does vary from image to image and from browser to browser. I'm not sure what the reason is behind it. I wrote this script for a church and it's photos vary in corruption. You can see the images at http://mtziontrenton.com/cgi-bin/ezwebalbum.cgi With some images it was fine, with others it is a few lines, and others had major corruption.

    If you have any idea about why this is happening, please let me know!
[reply]
      Have you tried just always calling binmode on whatever file handle you're using to output the image?
[reply]

In Section Seekers of Perl Wisdom