For some reason, on my Windows PC, the "libreoffice" command is not
present. So, if you choose to use the command terminal, and
"libreoffice" is not recognized, the following command should work:
soffice --convert-to fodt path\to\file.docx
path\to\file.docx would be the path to the docx file. The path may use
/ instead of \ depending on the operating system.
The command "libreoffice" might work for you, though. I guess it
depends on the installation, operating system, PATH variable
configuration, or some other factor.
On 2/4/2014 2:22 PM, e-letter wrote:
On 04/02/2014, Peter West <email@example.com> wrote:
If you write the files out as .fodt (Flat XML) files from within LO, you
will have straight XML files to compare.
Beyond that, you could get the tika-app.jar from the Apache Tika
project, which will let you extract plain text from the .fodt files and
directly from the .odt files.
On 4/02/2014 6:36 pm, firstname.lastname@example.org wrote:
Is it possible to have a diff between 2 .docx files in libreoffice? Or
with any other tool, I do not really mind...
Similarly, you could use the command terminal:
libreoffice -convert-to fodt /path/to/m$file
Then apply your diff tool. In addition, you could then use xslt to
extract the elements/text of the fodt files.
To unsubscribe e-mail to: email@example.com
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
Impressum (Legal Info)
: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (MPLv2
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our trademark policy