We already have a section in the Known_problems about 16bit data and rpic/wpic. Since we have no other reports from any linux systems for this problem, my guess is that it may come from a build/config problem for NetPBM in gentoo.
Maybe Ingo could update the gentoo bug ticket with the facts we've discovered. I think the debugging will involve creating known good 16bit intput and output files and then tracking down the differences. For the PDL-2.4.10 release, I think we could just add a button on our Get PDL section of the web site for gentoo and put the OS specific note there. --Chris On Thu, Jan 19, 2012 at 8:26 AM, David Mertens <[email protected]> wrote: > Should we add a tentative note to the docs? > > On Jan 19, 2012 6:10 AM, "chm" <[email protected]> wrote: >> >> On 1/19/2012 3:56 AM, Ingo Schmid wrote: >>> >>> you are right, pngtopnm has problems converting the created pngs. I >>> don't know if wpci creates some sloppy png or the problem is with >>> pngtopnm, since it can convert i.e. screenshots quite fine. But then >>> they are created via intermediate pnms (or something) in the first >>> place, no? >> >> >> The issue is only with 16bit data and whether >> that works with pnmtopng (and vice versa). As >> long as you are only using the default 8bit >> images, things should work ok. >> >> --Chris >> >>> On 01/18/2012 03:56 PM, chm wrote: >>>> >>>> The problem appears to be in the pnmtopng/pngtopnm >>>> and possibly the initial creation of the input data >>>> piped to those commands. I'll add this to the list >>>> of known problems for the 2.4.10 release. Thanks >>>> for reporting the problem. >> >> >> > _______________________________________________ Perldl mailing list [email protected] http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
