| | <<<Back 1 day (to 2022/07/08) | Fwd 1 day (to 2022/07/10) >>> | 20220709 |
| artifexirc-bot | <xx> which means I have one last mystery to the difference between how ghostscript does it and how imagemagick does it | 00:11.56 |
| | <xx> the above command produces a file, where the `file` utility outputs "JPEG image data, JFIF standard 1.01, resolution (DPI), density 1200x1200, segment length 16, baseline, precision 8, 2480x3507, components 1" | 00:12.10 |
| | <xx> why is the density 1200x1200 instead of 300x300? | 00:12.23 |
| | <xx> feels like ghostscript emits the density field into the jpeg headers based on what's supplied to the -r option instead of calculating what the actual density ends up being when dDownScaleFactor is in use | 00:13.24 |
| | <KenSharp> It's obviously using the original resolution rather than the downscaled resolution. However resolution is more oress irrelevant in an image format anyway, it has no real meaning. | 07:15.57 |
| | <xx> yeah resolution is irrelevant, but sadly it gets recorded into the JPG file, which makes the output of `file output.jpg` different between imagemagick and ghostscript. I want to remove the use of imagemagick and use just ghostscript, but I also want the output files to be similar to what they were before | 10:12.48 |
| | <xx> I now know exactly how imagemagick calls ghostscript and so can completely replace imagemagick for converting PDF->PNG/JPG. Thanks for all the help. | 22:26.57 |
| | <xx> last thing I'm wondering for now is if I should be using -dGridFitTT=2 by default for these conversions, it's what imagemagick uses | 22:27.34 |
| | <<<Back 1 day (to 2022/07/08) | Forward 1 day (to 2022/07/10)>>> | |
Log of #ghostscript at irc.freenode.net.