Sorry I took a while to respond, I was out of town. I downloaded the file and fetched the latest CVS and I don't seem to have any problem aside from the Camel which is explainable because of transparency. Is there something I missed?
-Michael Forbes
------------------------------------------------------------ Student System Operator binx.mbhs.edu BEN Manager http://ben.mbhs.edu BNC Internet Division http://bnc.mbhs.edu MBHS Webmaster http://www.mbhs.edu BlazerNet President http://blazernet.mbhs.edu Computer Team Co-President http://computerteam.mbhs.edu MBLUG President http://mblug.mbhs.edu ------------------------------------------------------------
On Sat, 9 Apr 2005, bulia byak wrote:
I am having trouble exporting my SVG as a PostScript file. Basically, it changes some parts of the image and fills them with black.
Actually this file exhibits several problems, some of which I fixed, some are unfixable, and some may be fixable but not fixed yet.
- The black parts ARE black yet use transparency, but PS does not
support transparency, so they become opaque. Never use transparency if you are going to export to PS. It's very easy to fix this however: select one of the transparent objects on the camel; switch to the Dropper tool (F7); make sure it's in the "pick visible color without alpha" mode; click on that same object. That will pick the visible color and assign it back to the object, but this time without transparency. Repeat for all transparent objects.
- The text with gradient ("On every system...") was rendered
invisible because it used bbox gradient units (probably was created in an old version of Inkscape). I have just fixed PS rendering of such gradients so it should work now (in CVS, as 0.41 does not export gradients to PS at all).
- However 2. only works if you select "convert text to paths" when
saving as EPS. I have enabled printing gradient fill on text but it still does not work (text renders black). This may be some limitation of PS or there's a problem with our PS generation. Michael: since gradient output is your code, could you please look into it? The file is attached to bug 1179448.