1.1.13 fall down, go boom

[David A. Desrosiers]

        Can someone verify this for me:

        plucker-build -H "http://home.pacbell.net/bullnose/pyth.gif"; \
        -f /tmp/Pythagorean --zlib-compression --no-urlinfo --bpp=8  \
        --launchable --maxwidth=740 --maxheight=820

        When I specify both height and width, the parser scales it to
370x410, and when launched, I get:

        Plucker (1.1.13) called SysFatalAlert with the message:
        "DataMgr.c, Line:7025, DmWrite: DmWriteCheck failed".

        Removing maxwidth, but leaving maxheight, the parser scales the
image down to 150x166, and it seems to work ok. Ideally, I'd like an image
2x the size of the original. I scaled it locally with gimp, and pointed it
to file:/tmp/pyth-LG.gif, which was detected as a 740x820 image. It crashes
with the same exact error.

        What's also weird is that if I leave the --maxheight=820 value, and
omit the --maxwidth=740 value, the file is scaled to 150x166.

        If I leave the --maxwidth=740 and omit the --maxheight=820, I get an
image which is scaled to 226x250.

        If the image is being detected as the same, but one is defined by
height (and no statically defined width), and the other is defined by width
(no statically defined height), shouldn't they scale to be the same physical
size?

        Using both height and width together crashes the Palm, hard.

        The reason I bring this up is because I was working with a guy in
irc in another window who is trying to convert a bunch of his blueprints,
diagrams, etc. over from FireViewer (non-free) to something better. He tried
the Acrobat reader, but it munches the fonts to death. I suggested Plucker,
and we went down this path. We managed to get one working, but it's not 2x,
and it's not quite 1x, but the fonts went from sharp to blurry in the
conversion process.



/d