Converting Adobe PDF to Plucker format
I've just spent a couple of hours working on a perl script that will convert any Adobe PDF document to Plucker format. You can find it on the top article of the Plucker website now. Right now, it's web-based popup gadget (yes, a Javascript popup, ugh), until I can stick it on a better version of a tools page on the site (I have a few other perl scripts here which allows picking from linuxdoc, ibiblio, the RFC archives, etc. and convert those to Plucker also, but I want to aggregate all these tools onto one page at some point). Test it out and let me know what you think. If it breaks, give me the error messages (if any) or email me the pdb directly, so I can take a look at what may have failed. I did my best to try to validate urls against bad strings and other file formats being put in there. There's no actual header logic being parsed at this point, so if you name an mp3 as a .pdf, expect weird stuff to happen. As I add these tools and begin the transition of these sites (and servers supporting it) to a larger pipe, the response time will increase considerably. Right now, we're getting hit pretty hard with cvs checkouts and people downloading Plucker and pilot-link from the same box at the rate of about 100/hour. This script, even though it launches perl server-side, should present no problems. /d
Re: --no-urlinfo doesn't work?
Michael Nordström <[EMAIL PROTECTED]> wrote: > On Thu, May 17, 2001, Darryl Okahata wrote: > > Am I missing something, or does --no-urlinfo not work (when viewing > > a page's details via Options/Details)? > > Maybe you could tell us what you expect to get and what kind of problem > you run into? As I said: when viewing a page's details via the viewer menu pick "Options/Details", the URL information is always shown, regardless of whether or not --no-urlinfo is given on the parser command line. If --no-urlinfo is given, I'd expect all URL information, whereever it exists, to be completely and utterly suppressed (not stored in the database). The patch I gave fixes it, but I'm not sure that my patch is the correct/best way. -- Darryl Okahata [EMAIL PROTECTED] DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day.
Re: How do big images get parsed?
Unfortunately I can't take credit for making the images look good. I use Quicktime to do the image scaling and conversion. Actually, I've spent some more time sampling different pages and things, and the image quality is about the same for most. Quicktime has a good range of settings for dithering and so forth that I haven't looked into yet. You could probably get the code I wrote in TbmpLib to work pretty easily in Windows as well using Quicktime for Windows... Ben Dirk Heiser wrote: > > "Ben" == Ben Chess <[EMAIL PROTECTED]> writes: > > Ben> The Macintosh port is coming along nicely. The images look *very* > Ben> good on the Palm; better than what I've seen come from Windows or > > Could you tell me what's the difference on this pictures that's make > them look better (other color mapping maybe?)? I know that the > pictures converted on Windows looks a little bit bad (in bpp=8) but i > do not know why, i never found out were the difference. > > cu, > Dirk > > -- > Permanent URLs to the latest Version () of the Plucker Windows installer > - For the Webpage: http://www.dirk-heiser.de/plucker > - Direct Download: http://www.dirk-heiser.de/plucker/plucker.exe [2.79MB]
Re: [Windows] Request for Testing - new Windows Image parser
>Attached also the description for the new ini keys, it would be nice >if someone check this for spelling errors please. Here are my suggestions by line. I've attached the amended file. 5: Pluckers -> Plucker's 10: Pluckers -> Plucker's 13: OS do -> OS does 14: and do not -> and will not 16: excites -> exceeds 16: try_reduce_bpp are -> try_reduce_bpp is 17: to use reduce -> to reduce 17: the size are OK, -> the size is OK. 17: if it -> If 18: with bpp=1 still to big -> bpp=1 is still too big 18: dimension -> dimensions 18: pitmap -> bitmap 19: stepps -> steps 22: compression, to -> compression. To 23: highes -> highest 23: size) -> size), 24: false, in -> false. In 25: size, this could be need -> size. This could need clone Get 250 color business cards for FREE! http://businesscards.lycos.com/vp/fastpath/ ;; ;; These keys control the way the images are converted to the palm Tbmp ;; format. ;; ;; The maximum size of an Tbmp bitmap could be 6bytes (before Plucker's ;; database compression), you could set the max_tbmp_size key to an lower ;; value to save memory on your device. ;; ;; The tbmp_compression key control the internal Tbmp compression (not ;; related to Plucker's databse compression), if set to true the Tbmp are ;; smaller and you could use pictures that normally exceed the maximum size ;; (as set by max_tbmp_size). But this will not work on all OS versions; ;; if your OS does not support this, the viewer will display a warning message ;; and will not show the pictures. ;; ;; If a bitmap exceeds the maximum size, and try_reduce_bpp is set to ;; true, the parser try to reduce the bpp until the size are OK. If it ;; bpp=1 is still to big, the dimension of the bitmap will be reduced in ;; 10% steps if the try_reduce_dimension key is set. ;; ;; How big a Tbmp will be after a bpp or dimensions reduce are calculated, ;; but this won't work if you use tbmp compression. To still get the ;; maximum quality (highest possible bpp and size), set the guess_tbmp_size ;; to false. In this case the bitmap will be converted in every step to get ;; the resulting size. This could need some more time. ;; ;;max_tbmp_size= 6 ;;tbmp_compression = no ;;try_reduce_bpp = true ;;try_reduce_dimension = true ;;guess_tbmp_size = true ;;
Re: From comp.sys.palmtops.pilot
Nick Vargish <[EMAIL PROTECTED]> writes: > It's deprecated, not removed. Plenty of documents exist that use and > were fully conformant with the standard of the day. Are we going to throw > out backward compatability and thus loose the ability to accurately > portray these documents? No, but the correct translation should be selected by the DOCTYPE of the source document. I've not looked to see what plucker's basic format is like, but wouldn't it be good to build up modular stylesheets and load in the right ones depending on the source document? Sort of XSLT-like, but that won't work as HTML isn't XML. Conformant and compatible, though. > I think that would be a big mistake, and one made based on a > misunderstanding of the intent of deprecating features. The concept is > there to steer page authors, not browser developers. Awww, what's the use of having standards if you can't grumble about them not being followed? > I haven't seen any actual "argument", though maybe that's happening at a > level that's not visible to me... http://www.dictionary.com/cgi-bin/dict.pl?term=argument WordNet entry, sense 3. -- MJR
Re: From comp.sys.palmtops.pilot
On 5 Jun 2001, MJ Ray wrote:
> So I saw. It's started some argument over whether this is a good
> thing, as strike-through is deprecated.
It's deprecated, not removed. Plenty of documents exist that use and
were fully conformant with the standard of the day. Are we going to throw
out backward compatability and thus loose the ability to accurately
portray these documents?
I think that would be a big mistake, and one made based on a
misunderstanding of the intent of deprecating features. The concept is
there to steer page authors, not browser developers.
I haven't seen any actual "argument", though maybe that's happening at a
level that's not visible to me...
Nick
--
#include /* SigMask 0.3 (sig.c) 19990429 PUBLIC DOMAIN "Compile Me" */
int main(c,v)char *v;{return !c?putchar(*v-1)&&main(0,v+ /* Tweaks welcomed. */
1):main(0,"Ojdl!Wbshjti!=obwAqbusjpu/ofu?\v\1");} /* build: cc -o sig sig.c */
Re: From comp.sys.palmtops.pilot
"David A. Desrosiers" <[EMAIL PROTECTED]> writes: > Mike fixed strikeout and put a package on the ftp site: So I saw. It's started some argument over whether this is a good thing, as strike-through is deprecated. -- MJR
Re: How do big images get parsed?
"Ben" == Ben Chess <[EMAIL PROTECTED]> writes: Ben> The Macintosh port is coming along nicely. The images look *very* Ben> good on the Palm; better than what I've seen come from Windows or Could you tell me what's the difference on this pictures that's make them look better (other color mapping maybe?)? I know that the pictures converted on Windows looks a little bit bad (in bpp=8) but i do not know why, i never found out were the difference. cu, Dirk -- Permanent URLs to the latest Version () of the Plucker Windows installer - For the Webpage: http://www.dirk-heiser.de/plucker - Direct Download: http://www.dirk-heiser.de/plucker/plucker.exe [2.79MB]
[Windows] Request for Testing - new Windows Image parser
Hi! Attached a new Windows Image Parser. Simple extract the file ImageParser.py from the Zip file and copy it in the PyPlucker directory (overwrite the one already there). The new one take care that no longer invalid bitmaps (>6 bytes) are included in the database, and there are also a few ini options to control the way how really big images should be handled. It's not fully tested for all cases yet (i still testing) but i wan't know how this work for all others. And i wan't to know if this new options are useful or if there are changes needed. Attached also the description for the new ini keys, it would be nice if someone check this for spelling errors please. cu, Dirk -- Permanent URLs to the latest Version () of the Plucker Windows installer - For the Webpage: http://www.dirk-heiser.de/plucker - Direct Download: http://www.dirk-heiser.de/plucker/plucker.exe [2.79MB] ;; ;; These keys control the way the images are converted to the palm Tbmp ;; format. ;; ;; The maximum size of an Tbmp bitmap could be 6bytes (before Pluckers ;; database compression), you could set the max_tbmp_size key to an lower ;; value to save memory on your device. ;; ;; The tbmp_compression key control the internal Tbmp compression (not ;; related to Pluckers databse compression), if set to true the Tbmp are ;; smaller and you could use pictures that normally exceed the maximum size ;; (as set by max_tbmp_size). But this will not work on all OS versions, ;; if your OS do not support this the viewer will display a warning message ;; and do not show the pictures. ;; ;; If a bitmap excites the maximum size, and try_reduce_bpp are set to ;; true, the parser try to use reduce the bpp until the size are OK, if it ;; with bpp=1 still to big, the dimension of the pitmap will be reduced in ;; 10% stepps if the try_reduce_dimension key is set. ;; ;; How big a Tbmp will be after a bpp or dimensions reduce are calculated, ;; but this won't work if you use tbmp compression, to still get the ;; maximum quality (highes possible bpp and size) set the guess_tbmp_size ;; to false, in this case the bitmap will be converted in every step to get ;; the resulting size, this could be need some more time. ;; ;;max_tbmp_size= 6 ;;tbmp_compression = no ;;try_reduce_bpp = true ;;try_reduce_dimension = true ;;guess_tbmp_size = true ;; ImageParser.zip
