|
|
I've tried to open poster2.sla with 1.3.3.5 -- my system has frozen and I've had to reboot |
|
|
I got the whole tarball and experiemented a bit. Some notes: In 1336 I can exported all of the plot files from grace and import them as vector EPS perfectly via File > Import. Using this method hugely reduces the amount of memory used in the file. Opening that page background.png in GIMP consumed almost 1GB by itself. As I see it looks like pagebackground.png is from latex generated formulas, you should export EPS from latex and then import that file File > Import > EPS. These vectors can be duplicated, grouped and manipulated as you wish for the same effect. I do not have latex installed, so I could not test that, but I am sure you can export PS or EPS from Latex. One of the issues I can see importing .odg files is the way gradients are created in SVG is quite ugly and they are not true gradients, but hundreds of concentric ciricles grouped. Inkscape shows the same problem when importing the SVG exported from Draw. The work around is to use plain polygons from Draw and then apply griadent effects in Scribus or Inkscape. Note also, those SVG files have text, which for the moment is to be avoided and noted in the docs on importing. I'll upload resaved versions of the original artwork in more usable form with a resaved Scribus file. If you have issues importing EPS, then we will need to know why. The workaround of exporting extermely large bitmaps is not recommeded - only for under say B5 size objects. |
|
2006-11-14 12:30
|
wavelet-H2b.eps (25,259 bytes) |
|
2006-11-14 12:30
|
RSPRC-13AlHalfVacuum.eps (22,225 bytes) |
|
|
I noticed looking at one of the PDF files an older Ghostscript created the PDF. Versions older than 8.15 are to be avoided. If you are trying to import with GS 7.0.7 that also might cause significant EPS import problems. |
|
2006-11-14 16:04
|
test.eps (252,885 bytes) |
|
|
Hi all, Thanks for your usefull comments Plinnell. Following are a few comment and questions about this: 1)For the background figure I was needing the pavement and randomisation features of Inkscapes. It decides me in not doing direct import from Latex. For the reasons about using PNG instead of EPS/SVG see below, point 3. 2)The odg files have never been directly incorporated. I keep transiting throught PNG. I would have done the figures with scribus If they were not already at hand under Ooffice. But I keep your advice for next works. 3) ABOUT EPS: In fact, before starting the work I had a try on the capabilites of scribus. So I've use the attached file test.eps. And tryed various ways of including it. It clearly shows that there is a problem regarding eps import. It puts my little P4 on knees just for viewing. At the same time even my most bulky png are very graciously handled. This decide me for the all PNG approach. Do you think I shall make an other report about this EPS problem ? 4) I'm a bit surprised about the GS versions. When running gs I get:""" [anglade@descartes poster-inauguration]$ gs ESP Ghostscript 815.02 (2006-04-19) ... """ How do you know about gs in the pdf ? Endly, I must say that I have been able to get a print throught the PNG export feature. Because of the memory limitation of my machine I was not able to get something finer than 450DPI but it was quite enough for a simple poster (20000x14000 px, almost 1GB out of scribus put no more than 20MB after compression by gimp(BY the way is this "bug" to be reported also)). Best regards to you all. PMA |
|
|
I've used 1336cvs, but would expect 1335 would be the same for importing. Some more investigation: I can import that test.eps flawlessly via File > Open with no docs open or File > Import into a blank page. I'll attach it soon. The other .odg file wavelet basis was exported from OO 2.0.4 as EPS with the settings recommened from here: http://docs.scribus.net/index.php?lang=en&page=importhints3 The ODG importer works well, except some gradients and some line types. I will file a bug for fixing these. These EPS files import flawlessly complete with transparent background. I took all the math forumla png files and retraced them back to vector via Inkscape and its potrace plugin, then exported EPS from Inkscape. Then did file Import > EPS into a new layer I created. Before exporting from Inkscape I deleted the imported bitmaps, leaving only vectors before saving, excepting the white background as you will see they import perfectly. This strongly suggests, you need to do file open > import instead of using image frames for EPS import. I took the PDF files and then did File > Print to File in Acrobat Reader > Level 3, Preserve Memory checked and printed a PS file. Then I imported this via File > import > EPS. Just works. TM The only file I could not sucessfuly convert were the pure bitmap files and the logos which with the gradients do not trace well. I've resaved this SLA and exported a PDF from Scribus. Max memory usage: 250MB and that was after having Scribus open all afternoon working on this file. Lessons: PNG's compress well, but when opened can consume many times its size in memory. So, a 2MB PNG can consume hundreds of MB of real memory. Never convert vector to bitmap - just find the right format from the creating application. In the case of OO Draw EPS export seems more reliable. |
|
2006-11-14 18:48
|
|
|
2006-11-14 18:49
|
|
|
2006-11-14 18:50
|
scaling.eps (76,803 bytes) |
|
|
Resaved PDF: http://docs.scribus.net/temp/poster2-resave.pdf Note this will only be there a few days. To conclude: Importing EPS files to remaining in vector requires File > Import EPS. If your system is having issues then, please make a visit to IRC so we can debug this interactively. Not a single EPS failed here on Suse 10.1 with GS 8.15.2 Exporting PNG or TIFF to be printed is not really recommended. We created this exporter more for screen shots than for high grade printing. Disable the view > grid except when necessary. It slows down redraws quite a bit. I'll resolve this soon, but will leave this open for comments and until you are all set on your end. |
|
|
Hi, Thanks so much for your kind work and advices. I'm already pretty much convinced about the virtues of vector manipulation of vector type object. I must have been unclear about the eps import: It works perfect for test.eps (I indeed do file>import>eps). Yet AFTERWARDS my scribus is starting having difficulties: the memory consumption raises reasonably (500MB) but the CPU usage became very very HIGH when manipulating the eps. So I'm going to test the combination of 1) the cvs version (if I'm able to access the cvs) 2) removed grid And came back later with comments or bug report (but I may not be able to this tonight since I'm on a W$ box presently). Best, PMA |
|
|
Peter, you rock:) Just a question, before you resolve this bug: we still have the issue with scribus (and possibly not only scribus) crashing while opening or exporting this file, don't we? We also have some similar, almost duplicate issues (e.g. 0004318), the question is, which one to keep until the crashes are really gone. I would vote for letting this one open, since it's a perfectly documented test case. |
|
|
Hi, Having tested with the most recent CVS I got the following results: I import test.eps. This is short. No more than 3s. When I put the focus again on scribus window it takes no less than 22-23s of full cpu usage during which scribus can't be used. Resizing the eps with the mouse use between 13 and 17s of 100% cpu usage. Quiting without saving after the previous operations takes between 6 and 8s. Doing the same operation with a big png takes only fractions of seconds. Note: my machine is a FC6, EMT64, 3.2GHz, 2GB RAM, and scribus was compiled with gcc 3.3.3. Is this behavior of scribus normal ? Shouldn't we expect a smoother behavior with EPS and other vector format than with 1GB PNG ? Shall I submit a separate bug riport for this ? regards PMA PS: Don't know exactly what IRC is and how to connect there. |
|
|
PPS: I had removed the grid and guides. PPPS: The test4-beware.eps should triggered my problem with eps import even on powerfull computers. |
|
2006-11-15 08:36
|
|
|
2006-11-15 11:07
|
|
|
2006-11-15 11:28
|
|
|
|
confirming the crash in accordance with plinnell (plinnell experienced X freeze too). Copied test files to: http://linux.hanski.info/tmp/bug.tar.bz2 They'll stay there as long as needed |
|
|
ESP Ghostscript 815.02 (2006-04-19) is not suitable for use with Scribus. It's from ESP, you need the GPL or AFPL version from Artifex. |
|
|
Depending on how many objects are created during PS import, it is expected that Scribus reacts sluggish. A png is just one object, a group of imported PS objects may contain thousands or tens of thousands small objects (Each text char will be a single object!) |
|
|
Yes This is natural and expected somhow :-(. However sometimes, one import EPS or PS object with no other goal than just putting them here and applying global operations to them (rotations, scaling, shear...). Just like what can be done with a PNG. For instance this case may happen if one is not willing to edit points in a plots or axis legends, or latex equations within scribus. For my case this examples are almost a good description of the way I use and import vector figures in scribus. I just want them to be where I place them. That's all. And the very large ressource consumption associated with the (nice) possibility to edit them within scribus is not overly welcome. Couldn't they be kept "still" until the author tries to edit them ?? That was my question. Best regards. |
|
|
old bug closing |
- Anonymous
