On Thu, Aug 03, 2006 at 10:21:33AM +0200, Ulf Erikson wrote:
MenTaLguY wrote:
Incidentally, it's the newer transparency-enabled PDF export used with the commandline export if I understand correctly? We should note that in the release notes...
Hmm.. It looks like the first extension found with mime-type "application/pdf" will be used. In stable that's only the native exporter, but for trunk the cairo-based pdf exporter uses the same mime-type. I don't know how to tell which exporter will be used then.
What about, instead of all the --export-pdf/ps/eps/png, a single --export-file=FILENAME.EXT and pick an internal or external extension based on .EXT if it is unique or list the Id's of available extensions for .EXT otherwise. Also, add an --export-through=EXTENSION-ID for the case that .EXT is not unique or the user wishes to use a filename without the regular .EXT. Does this sound reasonable as an RFE for trunk or plain nonsense? (I rarely use the commandline interface of Inkscape myself)
I use the commandline export capability quite often, and actually find the --export-pdf/ps/eps/etc. to be not that big of a deal. In fact, I'd sort of like even finer grained control - being able to select exactly *which* pdf exporter to use. As mentioned, there are multiple ways to get pdf's, and depending on the file, one converter may work better than another.
So... maybe --export-with=CONVERTER would be the proper approach, and then we could have 'pdf-cairo', 'pdf-ps2pdf', 'pdf-scribus', ... as options, with plain 'pdf' pointing to whichever converter the inkscape team feels to be the ideal default pdf converter.
I imagine this would also enable more dynamic addition of conversion filetypes. Presently, even though you can easily add a new inkscape extension via the .inx files, you can't use it from inkscape's commandline interface without adding a new cmdline option to main.cpp.
Bryce