Log file Viewer

[19:34:07] <freyes> hey there

[19:34:30] <freyes> I was moving documentation and I've saw a reference to this document http://effbot.org/imagingbook/decoder.htm

[19:34:38] <freyes> but I didn't find it the sources

[19:35:05] <freyes> do you know if it's possible to take it and put it in Pillow?

[19:35:26] <freyes> (possible or desired) :)

[19:40:04] <wiredfool> I grabbed the imaging book a while back, but only from the website

[19:40:30] <wiredfool> I think it's totally possible to turn it back into a source, and I think that the license is permissive enough to add it

[19:44:23] <aclark> freyes: it's come up before… not sure of the status. We should open a ticket for it if there is none.

[19:44:58] <freyes> wiredfool: thnx

[19:46:39] <freyes> aclark: ok, I can do that, do I file the issue considering the whole imaging book (tutorial, concepts, Writing Your Own File Decoder, etc)?

[19:47:37] <aclark> yup

[19:59:23] <freyes> ;) done

[19:59:39] <freyes> https://github.com/python-imaging/Pillow/issues/282

[20:00:48] <freyes> aclark: thanks for reviewing my PRs so quickly :)

[20:01:44] <freyes> you're putting extra pressure on my effort of porting the documentation, a good pressure by the way :p

[20:08:40] <aclark> freyes: np :-) We love when we get a new contributor

[21:14:21] <dotpot> hello there

[21:15:19] <dotpot> any ideas why this http://bit.ly/1aWWehP could happen after processing with PIL ? possible actions done: resize/crop/rotate -> save.

[21:16:31] <dotpot> first idea in my mind is that i was not using icc_profile while saving, but I'm not sure if this is the case.

[21:17:52] <freyes> hi dotpot

[21:18:49] <freyes> dotpot: did you try writing a simple script to reproduce the problem?, so you share it

[21:20:19] <dotpot> nop, i don't have an original image atm...

[21:40:42] <wiredfool> that looks corrupted

[21:41:07] <wiredfool> or even truncated

[21:42:00] <wiredfool> since the first portion of the image has the full jpeg dct factors, but the last part only has the initial low res one, and it appears in only one or two channels.

[21:44:13] <dotpot> So original image must be corrupted in some way If I understand correctly

[21:44:28] <wiredfool> It could be.

[21:44:47] <dotpot> maybe .verify would help in this case, since it's not used atm

[21:45:51] <dotpot> ok, tomorrow I'll get original image and will try to play with it, I'll let u know if I'll find anything, or even better - reproduce the problem.

[21:46:02] <wiredfool> but I'm seeing this from imagmagick: identify: Corrupt JPEG data: premature end of data segment `6d6e4fed-f2b0-495a-9971-f36627f30b98.jpeg' @ warning/jpeg.c/EmitMessage/231.

[21:46:37] <wiredfool> so, that one appears to be a truncated image

[21:47:36] <dotpot> thanks .)