> My company does too. I use a section in .pluckerrc and a couple of >scripts (run by before_command and after_command) to do the translation >with wv and the cleanup. *snip* > Maybe we should just provide the scripting.
The limitation with this is that the user has to plan for this and setup the scripts for each pdb that may have a word doc. Also, last I knew, the perl scripts didn't work under windows, where Word docs are most likely to be. If scripts need to be made/altered anyway, why not include it in the python parser? The wv support can be an optional download and there are the added benefits of (1) easier usage for the windows dummies and (2) mixed content pages will be parsed without any prior setup. Of course, I'd like to see more document types supported. I use plucker more as a document reader than a content grabber. A lot of periodic corporate data is distributed as Word documents or PDFs though, so supporting these formats in the parser (even as a wrapper to another tool like wv) could accomplish both. _______________________________________________ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
