custom huffman tables

[I was going to post to bugs, but it is offline... -JimC]

An inability (for a competing sw) to render the pdf at:

  http://community.haskell.org/~gwern/nuke-atmosphere.pdf (temp hosting)

led me to try it in gs and mupdf.

That pdf has jbig2 images which use custome huffman tables, which jbig2dec
does not yet support:

,----< mupdf nuke-atmosphere.pdf >
| ximage: mode 24/32 00ff0000 0000ff00 000000ff (16,8,0) lsb <swap>
| ximage: ARGB8888 to BGRA8888
| ximage: XShmPutImage
| jbig2 decoder FATAL ERROR: symbol dictionary uses custom DW huffman table (NYI) (segment 0x03)
| jbig2 decoder FATAL ERROR: symbol dictionary uses custom DW huffman table (NYI) (segment 0x0f)
| jbig2 decoder FATAL ERROR: text region uses custom DS huffman table (NYI) (segment 0x32)
| jbig2 decoder FATAL ERROR: text region uses custom DS huffman table (NYI) (segment 0x62)
| jbig2 decoder FATAL ERROR: text region uses custom DS huffman table (NYI) (segment 0x6f)
| jbig2 decoder FATAL ERROR: text region uses custom DS huffman table (NYI) (segment 0x7a)
| jbig2 decoder FATAL ERROR: text region uses custom DS huffman table (NYI) (segment 0x85)
| jbig2 decoder FATAL ERROR: text region uses custom DS huffman table (NYI) (segment 0x8e)
| jbig2 decoder FATAL ERROR: text region uses custom DS huffman table (NYI) (segment 0x9b)
| jbig2 decoder FATAL ERROR: text region uses custom DS huffman table (NYI) (segment 0xae)
| jbig2 decoder FATAL ERROR: text region uses custom DS huffman table (NYI) (segment 0xbb)
| jbig2 decoder FATAL ERROR: symbol dictionary uses custom DW huffman table (NYI) (segment 0xc3)
| jbig2 decoder FATAL ERROR: text region uses custom FS huffman table (NYI) (segment 0xd2)
| jbig2 decoder FATAL ERROR: symbol dictionary uses custom DW huffman table (NYI) (segment 0xdc)
| jbig2 decoder FATAL ERROR: symbol dictionary uses custom DW huffman table (NYI) (segment 0xe3)
`----

(Those errors come from paging all the way through the 22 page document.)

I wanted to point out an example of a real-world document which uses custom
tables in case one was needed for testing the future implementation.

-JimC
-- 
James Cloos <[email protected]>         OpenPGP: 1024D/ED7DAEA6