Bug 91625 - Command line conversion does nothing if the file is not in same folder
Summary: Command line conversion does nothing if the file is not in same folder
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
4.4.3.2 release
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Commandline
  Show dependency treegraph
 
Reported: 2015-05-25 21:05 UTC by muso
Modified: 2017-07-12 20:35 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:
Regression By:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description muso 2015-05-25 21:05:46 UTC
I have a file called "test2.html" which is in the folder
D:\Download

I want to convert it and therefore execute this command from a command line:

C:\Program Files (x86)\LyX 2.1\bin>start "office" "C:\Program Files (x86)\LibreO
ffice 4\program\swriter.exe" -convert-to odt "D:\Download\test2.html" -headless

result: nothing happens

Now I execute exactly the same command but from a console that was stated from the same folder as the html file:

D:\Download>start "office" "C:\Program Files (x86)\LibreOffice 4\program\soffice
.exe" -convert-to odt "D:\Download\test2.html" -headless

result: I get a test2.odt file

But to be able to use the document conversion I need to execute soffice.exe from different folders. It is quite useless that one needs to call it from the same folder. I mean I have several files living in different directories and I need to convert the all.

is there at least a workaround? 
(Specifying and -outdir does not help)
Comment 1 raal 2015-05-27 16:47:06 UTC
I can confirm with Version: 5.1.0.0.alpha1+
Build ID: af75d7a4c99414fabbd31b9df590266d28574fb1
TinderBox: Win-x86@39, Branch:master, Time: 2015-05-26_00:20:30
Win7
Comment 2 QA Administrators 2016-09-20 09:46:21 UTC Comment hidden (obsolete)
Comment 3 muso 2017-02-28 22:29:06 UTC
This bug has been fixed in the meantime. Many thanks.