my most and least favourite system that i have ever had to administer involved an embedded copy of OpenOffice.org (originally a solaris sparc binary of 3.1, later the ubuntu 10.04 package of 3.2), started from a cgi-bin perl script as needed, to convert MS Word .doc files to PDFs.
this is because MS Word .doc is such an utter shower (specification PDF, 563 pages) that it takes something approximately the size and complexity of MS Office to deal with it. and OOo is certainly that.
(we thankfully talked them out of making us install embedded MS Office instead, by offering to charge them the cost of a windows sysadmin to run it. never say no!)
the .doc files were end users’ edited versions of deeply defective source .rtf files generated from XML and XSLT by apache frontoffice, that wouldn’t open properly in anything else but MS Word. i wish i still had some, they’d be great bug fodder to submit to libreoffice.
even though this system was released in 2009, it never did manage to cope with MS Word 2007 .docx files.
it also kept said .doc files in a subversion repo. which was not operated using svn binaries, but twiddled by the relevant java libs.
the cgi-bin perl script was because the “generate PDF” functionality required a process fork, which hit a bug in solaris sparc java 5 and 6 that tried to make a copy of the entire tomcat process in physical RAM, which of course ran out of memory and failed. OOo won’t run if the user’s home directory isn’t writable, so on ubuntu this required “sudo chown www-data /var/www“. thankfully we weren’t using that as the webroot.
when i asked the (very good) senior developer about these design decisions, the pained expression on his face as he detailed why all these terrible ideas were the least-worst options was quite exquisite.
the purpose of a specification is to nail down the vague hopes and dreams of the business unit that’s just seen a fat, juicy market opportunity. in this case, they wanted a magical flying unicorn pony that ejaculated rainbows. the spec went into quite some detail about the desired properties of the wing feathers.
what they ended up with of course was a retired seaside donkey that had been tarred and feathered, a cornetto stuck on its head and fed food colouring and laxatives.
one part of the original specification of the system was to take updated versions of the source .rtf files and merge them with the user’s free-form .doc files such that the end users’ annotations would be preserved and stay correct. that is, the spec implicitly required the implementation of strong artificial intelligence. we told them that bit would have to be implemented later.
i quite delighted in deleting all traces of that system personally when, after five years’ soaking up money for two institutional customers ever, it was finally decommissioned.