Rescently I needed to automate export of ods files to csv. I started searching for macro help since I thought that was only way to batch convert ods to csv. By accident I found out libreoffice supports CLI!!! But problem is, there is almost no documentation on it. I had to lure openoffice.org forums, ask.libreoffice.org and other websites to find clues on how to make command that would convert ods file into csv (with semicolon separator instead of default comma). This is very powerful automation tool for which almost noone knows it exists. New option which will not be documented: https://bugs.documentfoundation.org/show_bug.cgi?id=36313 People filling bug for things that can already be done, but there is no documentation: https://bugs.documentfoundation.org/show_bug.cgi?id=68786 I for one, want to export certain sheet to CSV (not first default one in spreadsheet file), but don't even know if that's possible of not. And lots and lots of others... Experienced developer with access to code should write all available option in CLI, and then linguist should make wiki help out of that for everyone to understand and use. This is part of CLI on openoffice.org, but very small and insuficient. https://wiki.openoffice.org/wiki/Documentation/DevGuide/Spreadsheets/Filter_Options
Looking at https://wiki.documentfoundation.org/FindTheExpert, I also add David who might be interested in this bugtracker.
Yup, the CLI is not very completely documented. Presently have to poke around in the filters for the correct names. Specific syntax as with delimiters has been very hard to track down. Setting NEW. =-additional refs-= http://cgit.freedesktop.org/libreoffice/core/tree/filter/source/config/fragments/filters https://help.libreoffice.org/Common/Starting_the_Software_With_Parameters http://ask.libreoffice.org/en/question/2641/convert-to-command-line-parameter/ http://ask.libreoffice.org/en/question/2082/libreoffice-command-line-infilter-options/
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.0.5 or 5.1.2 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT - Update the version field - Reply via email (please reply directly on the bug tracker) - Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2016-04-16
I'm closing the bug as fixed. wikihelp has been phased out in release 6.0. The page with CLI commands is this one now: https://help.libreoffice.org/6.1/en-US/text/shared/guide/start_parameters.html You can reach it typing "command line" in the index search on the left. If you disagree with the current help page contents please reopen and indicate what is wrong. Cheers.