is giving some great results and is a gift to script... (doesn't often like direct `piping' thus the need for tmp)Funny that you mention this. Great minds think alike. My thoughts were to create a short shell script that does something like this:
Code Sample
#!/bin/bash # # wordview Rev0 2/5/05 # originally submitted by cbagger01 from the DSL forum # antiword -p letter "$*" > /tmp/"$*".ps gvu /tmp/"$*".ps rm /tmp/"$*".ps exit
save the script as wordview and then do a "chmod 755 wordview" to make it executable.
and then associate the *.doc extension to run "wordview" in the emelfm file manager.
So then all you need to do is double-click on the Word document and up pops the nice formatted postscript conversion of your document for viewing or printing.
Give it a try. Maybe it is worth adding in a future version of DSL.FYI, around 0.9.0 build we tried to eliminate Xpdf by using a technique very similar to the above suggestion. But it was dropped because of gvu rendering ability of some postscript files.Hi Cbagger, great to be in good company.
Robert, I finally got the script to fall over (a little bit) on one document when it got confused around an included image (where upon it just produced a few blank pages before returning text) but apart from that I've not hit big trouble (with -p a4 postscript output).
Accepting it might never be clean enough for DSL: antiword + gvu is however definitely beating wvHtml + dillo, or previously, wvLaTeX + latex2rtf + Ted or any other combinations I've tried. Perhaps still worth consideration??Hi again CB, Robert, CB - I've just noticed that in the `word processor' posts from a while back you'd already mentioned antiword and (oh yep) gv in almost the same sentence.... hmmm, beginning to get the feeling I'm a few steps behind folk.... I'll try to stay a bit more up to date in future. Cheers.Next Page...
original here.