Motive for this report is a possible situation where we have a large presentation document (imagine dozens of slides) that stucks on unknown slide. How to find it fast? I propose adding command line option for export-to of selected slides. Then we can script finding a troubled slide. Recently in bug 69192 command line switch was added to start at arbitrary slide number. Not sure if something can combined like: soffice --show=3 --convert-to svg file.odp.
WF IMO. Exporting presentation is not a simple task with easy way to limit to some slides. One example: what to do with custom presentations (that may refer to the unexported slides)? IMO, the idea to introduce functionality specific for testing of bugreports is not a good direction. These would themselves create new bugs; and testing with these would not necessarily use the same code as the problem happening when using normal ways. The "stucks on unknown slide" problem is an example of the problem that will most of the time *not* be solved by the proposal, because the problem would happen on *import*, which would be required anyway, not on export.
Custom presentations have GUI bug 33944 and bug 143283, and that is not a primary usage, I'd consider that a future issue. Any command line option that does what GUI can is welcome (not all are the same priority). So not WF for me of course. We need others to opine.
(In reply to Timur from comment #2) > Any command line option that does what GUI can is welcome Note that for --convert-to, this is not true. The fundamental concept of --convert-to is to do as close to complete conversion as possible. We do not do any editing in that command at all, like page reformatting, content editing, ... - we take as much information from the source format as possible, and put as much information into the destination as possible. For anything like "what GUI can", there are macros.
(In reply to Timur from comment #0) > Recently command line switch was added to start at arbitrary slide number. Not likely much help here. That just tweaked existing functionality (which itself already was very long and convoluted). > Not sure if something can combined like: soffice --show=3 > --convert-to svg file.odp. Definitely combining will not (and should not) work. --show is considered a "mode" and --convert-to is another "mode". Each new mode stops the previous mode. The use-case for adding such a feature would be way too limited to justify the effort (which would be significant). WONTFIX
As Miklos said in 146695 comment 3: > I think it makes sense to expose filter parameters which are already > available for the UI and for extensions to the cmdline users, sure. But I think this should follow the same syntax of (existing) property mapping as for PDF in 0c3b8792b712e939d2ad524d554f96616b4844be, and be requested for a specific filter. In the current state of this report, I agree with "won't fix".
Export to PDF is fine and would fulfill the purpose of the request.
(In reply to Timur from comment #6) > Export to PDF is fine and would fulfill the purpose of the request. This currently works for Impress documents: libreoffice24.2 --headless --convert-to 'pdf:impress_pdf_Export:{"PageRange":{"type":"string","value":"2-3"}}' sample.odp Does that cover it?
Thanks Stéphane for that, it works. I made an omission here, namely primary focus was convert to svg not pdf. So if svg is possible that would be great. If not, pdf will be used.
OK, I missed that. I clarified the summary. With 3× "won't fix", let's close, at least for now. It's very much possible that in the future, we end up with a proper SVG export dialog with options like slide range, see bug 66870 and bug 117708. At that stage, we could reconsider adding the same kind of command line syntax as for the PDF filter, so there is a clean 1-to-1 property mapping as suggested by Miklos.