Last post by Florestan - March 01, 2024, 03:11:37 PM
Merci beaucoup, it seems to have actually worked!
I think I'm now one step further. Now the editor reports that it has successfully compiled my input. Still, Scribus doesn't show the result, just the name of the pdf in the temp folder: scribus_temp_render_cHeyTr.pdf in my case.
And again I seem to have to learn something new...
please learn how to use the help in scribus (F1!) or the website with the API documentation, i previously linked: all three commands above are the literal translation in code of your question and are easy to discover! (yes, i also had to look them up in the API documentation!)
Last post by a.l.e - February 29, 2024, 09:47:54 PM
@Nermander : in that case i would suggest to create a pdf and extract the images from there : - )
@AdmFubar : yes, i thought that it might be missing. but rather than fighting the xml, the better solution is to create the commands for exporting the images and submit a patch (or ask the community to create the commands). then the problem is not only solved for the one user, but for everybody (creating a command for the scripter is a bit more tedious than necessary, but to 90% copy paste work)
Last post by AdmFubar - February 29, 2024, 09:35:02 PM
thought i might have a solution, and tried "collect for output" option .. alas embedded images stay firmly planted in the .sla and not exported into a sub-directory as i had hoped.
From what i can gather by looking over the available commands in python, there seems to be no option to allow exporting embedded images via a script. I checked even for a command to remove the embedding, nothing available to implement that idea.
Look like the only recourse is to parse the .sla , find the point(s) where the embedded image(s) and decode,extract and save them.