[Scribus] Memory Consumption on Image Frames

Nicolás Carranza nicarran
Sun Feb 4 23:02:36 CET 2007

Craig Bradney wrote:
> On Sunday 04 February 2007 21:09:59 Gregory Pittman wrote:
>> Nicol?s Carranza wrote:
>>> I saw that it depends on how you tried to import/open the PDF. Using
>>> "File->Import->Import EPS/PS..." scribus imports the PDF not only as
>>> images but also as poligons and many other objects, this also uses a lot
>>> of memory but I think that this is another problem.
>>> I don't need all those objects ("PDF components") imported, I only need
>>> to annotate over the images; so, I used a script to export each PDF page
>>> as a good quality image and then import them to a scribus doc (using
>>> something like this script
>>> http://wiki.scribus.net/index.php/Automatic_import_of_images_from_a_direc
>>> tory_using_a_script; I can send you my script if you want). This makes
>>> things a lot easier for scribus (it does not construct all of those
>>> objects), but the memory problem because of cached images arises.
>> BTW, that's my script on the Wiki. You can use it to import PDFs,
>> realizing that what you are doing is importing into image frames, and
>> therefore rasterizing them to bitmaps.
> Image handling optimisation is scheduled for 1.3.5 or higher.
> Regards
> Craig
> _______________________________________________
> Scribus mailing list
> Scribus at nashi.altmuehlnet.de
> http://nashi.altmuehlnet.de/mailman/listinfo/scribus

Hi Greg, I didn't noticed it was your script, thanks for it!

Hi Craig. I'll be watching the upcoming 1.3.5 o higher for these 
optimizations. With optimized image handling, I think that scribus can 
be used as nice and powerful PDF documents annotation tool. Thanks!

More information about the scribus mailing list