> Not at all, you can make a script that just takes a path to a Word >doc as an argument and converts.
Sure, if all you want is to convert one document. My company has a home page with internal news, etc. with links to relevant Word documents. It would be nice to have the home page with news and the Word documents linked to in one pdb. >> Also, last I knew, the perl scripts didn't work under windows, where Word >> docs are most likely to be. > > Perl runs under Windows, so I don't see why this wouldn't work. >Also, under Windows, you don't need to use wv anymore, you can use the stock >OLE perl modules (Win32::OLE) and get the actual data out of the Word I was referring to the doc2pl script on the links page which says it won't work on win32 systems. Updating this script as you describe to support win32 would be cool, but it doesn't allow a Word doc file to be a plucker channel, or parsed when linked to. > Not everyone uses the Python distiller code. Agreed, but that's not a reason to _not_ include it, but rather a reason to support it in each distiller. Dave. _______________________________________________ plucker-dev mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
