Convert-to command line parameter

[the_code]

for me --headless worked only when given after --convert-to.

soffice --convert-to pdf filename.doc  --headless

works while

soffice  --headless --convert-to pdf filename.doc

does not.

[GreyGnome]

Running on CentOS 6.5 with LibreOffice 4.0.4 and logging in only via ssh onto a server with no display whatsoever (ie, serial console), I get an error X11 error: Can't open display: which is what I would expect --headless to prevent. I needed to prefix the command with /usr/bin/xvfb-run. It doesn’t matter where in the command string I put --headless.

[Dor1]

How do you set the range of pages?

[mikekaganski]

Since long time, under Windows correct syntax is also --convert-to (with two dashes).
Headless is now implied for --convert-to, and it’s completely not necessary to use it explicitly here.

[Vikash]

Im getting error while executing command soffice

---

LibreOffice 5.2 - Fatal Error

The application cannot be started.
[context=“user”] caught unexpected com.sun.star.ucb.ContentCreationException: Cannot create folder (invalid path): C:

[cben]

--headless is not strictly mandatory, but you want it.
Without it, the document is still converted (note “convert /…/filename.doc → /…/filename.txt using text” message on stdout) but an empty GUI is also started (and the command blocks until you close the GUI).

More importantly, headless conversion silently does nothing if any LO is already open; see How to NOT connect to a running instance for a solution.

[bosyber]

Thanks, that is a useful caveat about headless conversion only working when no other LOis open, by default. Sure explains why I had trouble before; now I am using the -env trick.

[mikekaganski]

Headless is now implied for --convert-to, and it’s completely not necessary to use it explicitly here.

[tympan]

Having another instance open in a minimized window on another desktop had me baffled for an hour
It really ought to issue a warning to stderr about this.

[vmiklos]

Probably --convert-to should imply --headless, but if you want this, please open a bugreport.

Regarding the filters available, you can poke around at http://cgit.freedesktop.org/libreoffice/core/tree/filter/source/config/fragments/filters (sure, a more user-friendly wiki page would be better), for example if you want to convert to odt, try ‘–convert-to odt:writer8’.

[w_whalley]

This syntax worked for LO 3.4.6

soffice --headless --convert-to txt:text file_to_convert.doc

But only if no other instances of LO are open.

[rafik]

On win7, using LO 4.1 I had to do the following (from command line, you probably need to change %f to %%f if running in a cmd script):

set path=%path%;C:\Program Files (x86)\LibreOffice 4\program
for %f in (*.odg) do (
    soffice.exe --headless --convert-to pdf --outdir "C:\tmp" %f
)

Notes:

• it will NOT work if any instance of LO is open!
• outdir IS required
• wildcards for input files are NOT supported (hence the for loop)

[mike_a]

Thank you very much.

Just a few notes for WIN7 x64 LO 4.1.1.2 build ID 7e4286b58adc75a14f6d83f53a03b6c11fa2903

• outdir IS NOT reqired (strange?)
• NOT AT ALL instances of LO are opend, even LO Quick Start

Bear in mind to disable loading LO quick start on operating system startup. Otherwise it will be loaded on first convert and nothing will be coverted after it.

[Kardrik]

Couple of noob questions incoming.

1. that is two separate commands?
2. the first command, that looks like it is telling windows where to look for soffice.exe, or is it also looking for the files you want to convert?
3. Do I need to have command prompt open to the directory the files are in for this to work, I am guessing so.
4. If this is all entered in at the same time, do I need to separate the commands in any way?

[RobertN1]

FWIW:

1. Yes.
2. IMO, setting the path concerns executable files only (but I am not an guru for MS-DOS/Windows shell)
3. Yes (as an implication of 2.)
4. Very probably yes but I can’t tell you how - MS-DOS shell manual should say more. But executing at first the set command and afterwards the for command solves the situation in any case (the path you set is definitely valid at least until the command prompt session terminates). Or you can create a .bat file and separate commands by newline.

[RobertN1]

P.S. In a .bat file (script) you need to change %f to %%f.

[PrgWiz]

For windows machines, I have found that on some files the conversion needs a start /wait. Example

start /wait soffice --headless --convert-to txt file_to_convert.doc

It seems the shell collapses before soffice can complete the conversion is some cases.

[NickP]

Thank you for this - on Windows 7 I was getting unhelpful crash dialogs until I added the “start /wait” to the command. As a note the first quoted parameter for ‘start’ is the window name, so if you try to call the above from a script with a space in the path you may need to do it like: start /wait “” “C:\program files\libreoffice 4\program\soffice”

[RobertN1]

One more addendum:
It is possible to read - for example here: http://www.computerhope.com/starthlp.htm, www.microsoft.com is silent about that - that “When executing an application that is a 32-bit GUI application, CMD.EXE does not wait for the application to terminate before returning to the command prompt. This new behavior does NOT occur if executing within a command script.”; so it should imply that when executing soffice.exe from a batch script,

[RobertN1]

[continued] it is not necessary to call it via start /wait command. Unfortunately, it is NOT true. At least on Windows Vista (I know, horrible OS - but it was not on my computer) it is necessary to use start /wait even in a batch, otherwise the conversion collapses. Update: Primary source for the incorrect information about the start command (Microsoft’s site). LO version: 4.3.6.