Problem: The Windows binaries sometimes use a forward slash instead of a back slash in the output filename, which generates an error, but pngcrush writes a very large PNG file to the output filename anyway, which is annoying behavior, because it actually makes files that are larger than the original.
Expected outcome: Pngcrush should use only backslashes in the filename on Windows platforms, and it should not write larger files than the original if a filesystem error occurs.
Terminal output: (notice the forward slash in the error message "Could not open output file")
C:\Users\admin\folder>C:\Users\admin\pngcrush.exe -d "C:\
Users\admin\folder_crush" -bit_depth 1 -plte_len 1 -brute -w 32 -
c 0 "C:\Users\admin\folder\image0009.png"
|Portions copyright (C) 2005 Greg Roelofs|
|This is a free, open-source program. Permission is irrevocably|
|granted to everyone to use this version of pngcrush without|
|payment of any fee.|
|Executable name is pngcrush|
|It was built with libpng version 1.5.2rc02, and is|
|running with libpng version 1.5.2rc02 - March 22, 2011|
| Copyright (C) 1998-2004, 2006-2011 Glenn Randers-Pehrson,
| Copyright (C) 1996, 1997 Andreas Dilger,
| Copyright (C) 1995, Guy Eric Schalnat, Group 42 Inc.,
| and zlib version 1.2.5, Copyright (C) 1995-2010 (or later),
| Jean-loup Gailly and Mark Adler.
| It was compiled with gcc version 4.5.2.
Total length of data found in IDAT chunks = 2032
Reducing truecolor image to grayscale.
IDAT length with method 11 (fm 0 zl 2 zs 2) = 86749
IDAT length with method 12 (fm 1 zl 2 zs 2) = 86856
Could not open output file C:\Users\admin\folder_crush/image000
Log in to post a comment.