This answer passes all tests, but the flow chart one in your test document.
sudo apt-get install unoconv
Why is this better than other methods suggest thus far?
I have tested the other methods suggested so far (especially
ebook-convert), but they pass less tests than this method. The
ebook-convert method strips the margins and a part of the texts out of the document.
This method even yields better results than a professional converter as rainbowpdf.
I also tried converting it to html, but the drawing with the square in the circle and the flow chart are incorrect.
Why does the flow chart test fail?
It seems that libreoffice and unoconv have some problems with correctly rendering the flow chart that is in the .docx file. This is probably because it was made using smart art in Microsoft Office. That is the problem. That is a bug also discussed on this thread. The textual and visual information is present in the pdf resulting from the above method as you can see (I had to select the text, though).
The font color, for instance, is not properly read and some lines are too long. I am not aware of any linux solution that is able to display smart art correctly. :(
This is also the reason why all the
print solutions posted on this page will not satisfy you.
In short, what you are doing is really hard and there are at present no solutions that will fully satisfy you. The achilles' heel of docx2pdf conversions is the smart art. If you can live without that or if you can find a way to spot smart art and convert it somehow into an image, you can reach your goal.
Option 1. Force your users to deal with the problem
This is a very inelegant solution. Your content creators could save their smart art as jpg as described in the office help pages and hence the conversion would be possible on your server.
Option 2. Hack your way around the problem
If the flow charts are often very similar and depending on how good a developper you are, you could try and convert the smart art separately. You could, extract the drawing1.xml file from the .docx cluster of documents and then use natural language processing and some crazy hacks to rebuild a the smart art. For instance, you'd have to mess with this type of xml:
<a:bodyPr spcFirstLastPara="0" vert="horz" wrap="square" lIns="8255" tIns="8255" rIns="8255" bIns="8255" numCol="1" spcCol="1270" anchor="ctr" anchorCtr="0">
<a:pPr lvl="0" algn="ctr" defTabSz="577850">
<a:rPr lang="en-US" sz="1300" b="1" kern="1200"/>
<a:t>All three sides are different lengths
Or as a minimal solution you at least extract the text (
<a:t>?) from the file and save it in an easier way. Or if the flow-charts of your pdfs are all the same, you could write a script to change the text color and the line length in the xml itself. Then you could run
doc2pdf and you'd have a file that essentially has all the right info, but maybe not the formatting. In the case of flow charts you'd probably also want to include some of the formatting, because the formatting is part of the info.
Option 3. Use a third party service
I have done some more research the past few days and I have found a service that does the conversion perfectly: zamzar. Zamzar allows you to upload a docx file and then emails you a link. They also have a (paying?) service where you can send any file to firstname.lastname@example.org and then get the converted file back in your inbox. You could easily build a system around this where you automatically send the file and parse it from the email. This is not so much work and it the end result is the best.
- If anyone has other services that do the same, please feel free to edit them in.
- I have mailed the zamzar support to ask whether they have an api. That would be even easier.
- Maybe apose for .NET and Java could also help out? Or docx4java as in this very related SO post.
- Another option is to look into the the odf-converter which seems dated and is dependent on openoffice rather than libreoffice.
- I can now confirm that the java jodconverter also suffers fails the flow chart conversion.
I have actually taken the time to test the different methods proposed on this page. Please back any comments up with actual tests.