I have many folder like data_1,data_2, data_3 etc, that will be generated during program running. I want to copy these folders into .tar file named full_data.tar in a specified folder.
How can I insert folders named data_1,data_2, data_3 etc into full_data.tar in MATLAB by using UNIX commands?
As #kedarps already proposed I would also use the command line. The matlab command to execute command line arguments is:
status = system(command)
It is documented under this link:
system documentation
So if I take the unixcommand from #kedarps this should work:
system('tar -cvf full_tar.tar data_1 data_2 data_3')
I hope this helps
I am using JasperStarter to create pdf from several jrprint files and then print it using JasperStarter functtions.
I want to create one single pdf file with all the .jrprint files.
If I give command like:
jasperstarter pr a.jprint b.jprint -f pdf -o rep
It does not recognise the files after the first input file.
Can we create one single output file with many input jasper/jrprint files?
Please help.
Thanks,
Oshin
Looking at the documentation, this is not possible:
The command process (pr)
The command process is for processing a report.
In direct comparison to the command for compiling:
The command compile (cp)
The command compile is for compiling one report or all reports in a directory.
I'm trying to convert docx and xlsx files to pdf.
I have cgi perl script on server it worked fine but now it doesnt.
I didnt do any change.
When I try:
system("export HOME=/tmp && soffice --headless --convert-to pdf --outdir pdf/LgfpQJtC 'pdf/LgfpQJtC/example.docx'");
print"$?";
I get:
19712
The file example exist and it's in right directory.
But pdf file wont create.
When I run the same command as root in command line it works fine.
I tried set full acces to directory and file but it didnt help.
Is there any way to get more information about error?
Thanks for any help.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 1 year ago.
The community reviewed whether to reopen this question 1 year ago and left it closed:
Original close reason(s) were not resolved
Improve this question
I have to wait for long after using this LibreOffice command which is intended to convert DOCX into PDF:
libreoffice --headless --convert-to pdf test.docx --outdir /pdf
But I'm getting no response and no error. No file is converted. It looks like terminal is hanging.
So, is there is any way to track the error?
I would first of all try it with giving absolute paths to the command.
I suspect that the libreoffice binary does not work -- you have to locate the soffice binary and see if that works.
Then, your --convert-to pdf is not sufficient. It needs to be:
--convert-to pdf:writer_pdf_Export
Be sure to follow exactly this capitalization!
Next, the command will not work if there is already a LibreOffice GUI instance up and running on your system. It is caused by bug known since 2011. Add this additional parameter to your command:
"-env:UserInstallation=file:///tmp/LibreOffice_Conversion_${USER}"
This will create a new, separate environment which can be used by a second, headless LO instance without interfering with a possibly running first GUI LO instance started by the same user.
Also, make sure that the --outdir /pdf you specify does exist, and that you have write permission to it. Or, rather use a different output dir. Even if it is just for the first testing and this debugging round:
$ mkdir ${HOME}/lo_pdfs
Hence:
/path/to/soffice \
--headless \
"-env:UserInstallation=file:///tmp/LibreOffice_Conversion_${USER}" \
--convert-to pdf:writer_pdf_Export \
--outdir ${HOME}/lo_pdfs \
/path/to/test.docx
This works for me on Mac OS X Mavericks 10.9.5 with LibreOffice v4.4.3.2 (using my specific path for the binary soffice which will be different for you anyway...).
If all this doesn't work:
It may be a problem with the specific DOCX file you try the command with... So create a very simple DOCX document of your own first. Use LibreOffice itself for this. Write "Hello World!" on an otherwise empty page. Save it as DOCX.
Try again. Does it work with the simple DOCX?
If it again doesn't work, repeat step 7, but save as ODT this time.
Repeat step 8, but make sure to reference the ODT this time.
Last: Use full path to soffice, to soffice.bin and to libreoffice and run each with the -h parameter:
$ /path/to/libreoffice -h
$ /path/to/soffice -h
$ /path/to/soffice.bin -h
Do you even get an output here?
For which one of the three binaries/symlinks?
Record the outputs.
Tell us your outputs!!!
Compare them to the command line you used:
Are there any changes in parameter names, capitalizations, number of dashes used, etc.??
For comparison, my own output is here:
$ /Applications/LibreOffice.app/Contents/MacOS/soffice -h
LibreOffice 4.4.3.2 88805f81e9fe61362df02b9941de8e38a9b5fd16
Usage: soffice [options] [documents...]
Options:
--minimized keep startup bitmap minimized.
--invisible no startup screen, no default document and no UI.
--norestore suppress restart/restore after fatal errors.
--quickstart starts the quickstart service
--nologo don't show startup screen.
--nolockcheck don't check for remote instances using the installation
--nodefault don't start with an empty document
--headless like invisible but no userinteraction at all.
--help/-h/-? show this message and exit.
--version display the version information.
--writer create new text document.
--calc create new spreadsheet document.
--draw create new drawing.
--impress create new presentation.
--base create new database.
--math create new formula.
--global create new global document.
--web create new HTML document.
-o open documents regardless whether they are templates or not.
-n always open documents as new files (use as template).
--display <display>
Specify X-Display to use in Unix/X11 versions.
-p <documents...>
print the specified documents on the default printer.
--pt <printer> <documents...>
print the specified documents on the specified printer.
--view <documents...>
open the specified documents in viewer-(readonly-)mode.
--show <presentation>
open the specified presentation and start it immediately
--accept=<accept-string>
Specify an UNO connect-string to create an UNO acceptor through which
other programs can connect to access the API
--unaccept=<accept-string>
Close an acceptor that was created with --accept=<accept-string>
Use --unnaccept=all to close all open acceptors
--infilter=<filter>[:filter_options]
Force an input filter type if possible
Eg. --infilter="Calc Office Open XML"
--infilter="Text (encoded):UTF8,LF,,,"
--convert-to output_file_extension[:output_filter_name[:output_filter_options]] [--outdir output_dir] files
Batch convert files.
If --outdir is not specified then current working dir is used as output_dir.
Eg. --convert-to pdf *.doc
--convert-to pdf:writer_pdf_Export --outdir /home/user *.doc
--convert-to "html:XHTML Writer File:UTF8" *.doc
--convert-to "txt:Text (encoded):UTF8" *.doc
--print-to-file [-printer-name printer_name] [--outdir output_dir] files
Batch print files to file.
If --outdir is not specified then current working dir is used as output_dir.
Eg. --print-to-file *.doc
--print-to-file --printer-name nasty_lowres_printer --outdir /home/user *.doc
--cat files
Dump text content of the files to console
Eg. --cat *.odt
--pidfile file
Store soffice.bin pid to file.
-env:<VAR>[=<VALUE>]
Set a bootstrap variable.
Eg. -env:UserInstallation=file:///tmp/test to set a non-default user profile path.
Remaining arguments will be treated as filenames or URLs of documents to open.
Add one more argument to your command line to enforce the application of an input filter when soffice opens your DOCX file:
--infilter="Microsoft Word 2007/2010/2013 XML"
or
--infilter="Microsoft Word 2007/2010/2013 XML"
--infilter="Microsoft Word 2007-2013 XML"
--infilter="Microsoft Word 2007-2013 XML Template"
--infilter="Microsoft Word 95 Template"
--infilter="MS Word 95 Vorlage"
--infilter="Microsoft Word 97/2000/XP Template"
--infilter="MS Word 97 Vorlage"
--infilter="Microsoft Word 2003 XML"
--infilter="MS Word 2003 XML"
--infilter="Microsoft Word 2007 XML Template"
--infilter="MS Word 2007 XML Template"
--infilter="Microsoft Word 6.0"
--infilter="MS WinWord 6.0"
--infilter="Microsoft Word 95"
--infilter="MS Word 95"
--infilter="Microsoft Word 97/2000/XP"
--infilter="MS Word 97"
--infilter="Microsoft Word 2007 XML"
--infilter="MS Word 2007 XML"
--infilter="Microsoft WinWord 5"
--infilter="MS WinWord 5"
Update
LibreOffice cannot only convert DOCX to PDF on the command line:
It can process any input format which it can open and "read": DOC, XLS, XLSX, PPT, PPTX, ...
It can convert to any output format which it can "write": DOC, XLS, XLSX, PPT, PPTX, ...
Of course, results will never be perfect, and sometimes they will even be un-acceptable to you.
Re. output as PDF:
To control, which LibreOffice component generates PDF output, you can use these variants:
--convert-to pdf:writer_pdf_Export
--convert-to pdf:calc_pdf_Export
--convert-to pdf:draw_pdf_Export
--convert-to pdf:impress_pdf_Export
--convert-to pdf:writer_web_pdf_Export
Re. input which is not DOCX:
To enforce infilters for non-DOCX input formats, you could use (list is not complete):
--infilter="HTML Document" # for HTML input
--infilter="MediaWiki" # for MediaWiki input
--infilter="Text CSV" # for CSV spreadsheet input
--infilter="Microsoft PowerPoint 2007/2010 XML" # for PPTX input
--infilter="Microsoft PowerPoint 97/2000/XP" # for PPT input
--infilter="Windows Metafile" # for WMF input
--infilter="Enhanced Metafile" # for EMF input
--infilter="Scalable Vector Graphics" # for SVG input
--infilter="Microsoft Excel 2007/2010 XML" # for XLSX input
--infilter="Microsoft Excel 97/2000/XP" # for XLS input
--infilter="Microsoft Excel 95" # for some XLS input
--infilter="Microsoft Excel 5.0" # for some XLS input
Re. output which is not PDF:
To convert to specific output formats, you could use (list not complete):
--convert-to html:HTML
--convert-to html:draw_html_Export # force "Draw" to generate the HTML
--convert-to mediawiki:MediaWiki_Web # generate MediaWiki output
--convert-to csv:"Text - txt - csv (StarCalc)" # generate CSV spreadsheet output
--convert-to pptx:"Impress MS PowerPoint 2007 XML" # generate PPTX
--convert-to ppt:"MS PowerPoint 97" # generate PPT
--convert-to wmf:impress_wmf_Export # force "Impress" to generate the WMF
--convert-to wmf:draw_wmf_Export # force "Draw" to generate the WMF
--convert-to emf:impress_emf_Export # force "Impress" to generate the EMF
--convert-to emf:draw_emf_Export # force "Draw" to generate the EMF
--convert-to svg:impress_svg_Export # force "Impress" to generate the SVG
--convert-to svg:draw_svg_Export # force "Draw" to generate the SVG
--convert-to xlsx:"Calc MS Excel 2007 XML" # generate XLSX
--convert-to xls:"MS Excel 97" # generate XLS like Excel 97
--convert-to xls:"MS Excel 95" # generate XLS like Excel 95
--convert-to xls:"MS Excel 5.0/95" # generate XLS like Excel 5.0/95
Update
The current Version of libreoffice is working: v5.2.6.2 (mac)
I'm using the following command
/Applications/LibreOffice.app/Contents/MacOS/soffice --headless --convert-to pdf --outdir . the_file_to_convert
OLD
It seems that the conversion is not working in newer version (> 4.2.4.2)
I'm using libreoffice 4.2.4.2
You can download older versions from http://downloadarchive.documentfoundation.org/libreoffice/old/4.2.4.2/
linux (using the deb package):
libreoffice4.2 --headless --convert-to pdf myfile.odt
windows:
swriter.exe --headless --convert-to pdf myfile.odt
Might sound stupid but I suffered from just this: In Ubuntu 14.04 it is not enough to install only the package libreoffice-core or -common to convert to PDF, but you need to install libreoffice-writer instead/additionally. The important thing to note is that libreoffice-core|common seems to bring in some functional libreoffice base, hence the name ;-). That doesn't error out if executed to convert some file, but instead just seems to wait on some socket or such for input or whatever... After I installed libreoffice-writer, which has [...]-core|common as a dependency, converting some ODT file to PDF worked like a charm with the exact same command line like used before.
Seems a bit crazy that the application looks like it works somehow, but simply couldn't ever because of missing packages, and doesn't tell anything about it.
I'm using LibreOffice 4.2.8.2 too (on GNU/Linux) but I tried to convert a DOC file to a HTML file. I've installed libreoffice-headless, but the terminal was hanging too. I've tried each bullet of Kurt Pfeifle, but it was not working…
The solution was simple: installing libreoffice-writer (maybe libreoffice-filters is ok too, but it depends on libreoffice-writer plus the other big components of LibreOffice).
Hope this will help.
I had the same problem and got stuck for an entire day; silly me ended by figuring out that I was trying to convert from and to a network file system; even tho I have written right libreoffice seems to not support it, or at least not in my configuration.
I solved this by converting to /tmp then moving the file by hand. Hope it helps.
I encountered problems converting HTML to xlsx using libreoffice. Other convert-to options worked fine. Turns out it needed the --calc flag additionally. In case anyone else runs into the same trouble. Tested on LibreOffice-6.4.3.2.
Credits to: Libreoffice converting html to xls or xlsx
Setup:
Windows 7 Enterprise.
Matlab 7.10.0 (R2010a).
mcc compiler: Microsoft Visual C++ 2008 Express.
What's happening:
My project runs fine when running it through Matlab, but when trying to run the .exe through the command prompt after using mcc to compile, the command prompt generates an error.
The mcc command I issue is:
mcc -m -v STARTUP1.m -o EXE_REDUC
The error I receive in the command prompt is:
??? Error using ==> textscan
Invalid file identifier. Use fopen to generate a valid file identifier.
I have a file called LoadXLS.m that loads and reads a .csv file using:
fid = fopen(file,'r');
temp_data = textscan(fid,...args...);
And then I process temp_data.
The csv file I'm trying to load is called spec.csv. It is located two directories down from where I have STARTUP1.m stored. The location of STARTUP1.m is also the place that the mcc generated files are stored to. I have used the pathtool to "Add with subfolders" this location, but am aware that those locations are not transferred to mbuild when compiling.
What I've Tried:
I have gone in and added print statements to print the value of fid to make sure it is valid. When I run it in Matlab, it has a valid value, however when I run in the command prompt it always returns an invalid value of -1.
I have removed all addpath() calls, I have tried adding the STARTUP1.m directory to the mcc ctf archive using:
mcc -m -v -a 'C:\Users\...path...\STARTUP1.m_location' STARTUP1.m -o EXE_REDUC;
However when I do this, I get a different error when running in the command prompt:
Cannot open CTF archive file
'C:\...path...\AppData\Local\Temp\mathworks_tmp_7532_28296'
or
'C:\...path...\AppData\Local\Temp\mathworks_tmp_7532_28296.zip'
??? Undefined function or variable 'matlabrc'.
To fix this, I've tried adding the pragma
%#function matlabrc
to the top of STARTUP1.m to try and enforce its inclusion, but had no success.
I also copied the spec.csv file to a new directory in the ctfroot and changed
fid = fopen(...)
to:
[tempFile, message] = fopen(fullfile(ctfroot, 'Added Config Files', ad.spec_file));
The message is:
message is: No such file or directory
Objective:
Rearranging file locations is a sufficient workaround while the exectuable only runs on my computer, however the idea is to take this standalone and distribute it to multiple people on many different computers. I would like to be able to have a top folder with a startup file and within this folder, have as many subfolders as the package requires. The startup file should be able to access all subfolders and files within them as necessary.
I read something about the exectuable actually running from a "secret location" on the machine here: http://matlab.wikia.com/wiki/FAQ
I would just like to be able to group one entire folder tree with all its files into a package containing the executable and be able to run it anywhere.
More info:
When I put the spec.csv file in the same directory as STARUTP1.m, it finds it fine using mcc without the -a 'path' option and using the following in the LoadXLS.m file:
[tempFile, message] = fopen(ad.spec_file,'r');
This project contains GUIs, generates PDFs, generates plots, and also creates a zip directory.
Thank you in advance.