LibreOffice and Apache OpenOffice at the command line
Beyond the Editing Window
Officially, the developers of LibreOffice and Apache OpenOffice vastly prefer that users do everything from the editing window. There is a sound reason for this preference – from the editing window, users are less likely to run into difficulties such as corrupting files.
Still, most of the potential problems can be avoided if you work from copies. And, there's no denying that using ooo_cat
, for example, is a far faster way to combine files than copying and pasting.
At other times, just dealing directly with LibreOffice or OpenOffice files lets you do things that are impossible from the editing window. For example, you can check Tools | Options | LibreOffice | Paths to find your local configuration. Here, a little exploration will reveal the location of templates and features, such as custom gradients in Draw, so that you can back them up (Figure 2).
More ambitiously, if you change the extension of a file to .zip
, you will find that it is actually a zipped collection of XML documents (Figure 3). To understand these XML documents fully, you can consult the specifications for the Open Document Format, the default format for LibreOffice or OpenOffice [5], but you need no special knowledge to extract the unformatted text from content.xml
if a file is corrupt or to attempt repairs by pasting the XML documents to or from working documents.
By the time you've tried some of these simple operations, you should rightly conclude that, for desktop apps, LibreOffice and OpenOffice can have a surprisingly lively life at the command line.
Infos
- OOoPy: http://ooopy.sourceforge.net/
- ElementTree library: http://effbot.org/downloads/#elementtree
- Writer2LaTeX: http://writer2latex.sourceforge.net/index.html
- Writer2LaTeX manual: http://writer2latex.sourceforge.net/index14.html
- OASIS Open Document Format for Office Applications: https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=office
« Previous 1 2
Buy this article as PDF
(incl. VAT)