I really like the "tyrannomas". Did you use Tweak tool for it?

Nightly builds export to PDF just fine. Transparency is preserved and filters are rasterized, and the PDF is well compressed and small enough. WIthout a specific file to look at, we can't help you. Please make sure you really run a latest build (open Help > About, report what you see in the top righ...

Please use 0.47 prerelease, it has this problem solved

Inkscape does not require Gnome, only GTK.

No, Inkscape SVG is standard SVG, and any glows and filters are standard SVG feature.

We can only help you if you give us the details - which version of Inkscape, which fonts are not visible, which platform. If you can attach the bad fonts to your report it would be very helpful.

That's a known problem. Inkscape uses 90 dpi to convert from px to abs units. This is a murky area, the standard is not entirely clear on this. It is recommended to not mix px and abs units in the same document.

This is by its nature a manual, freehand operation, a drag. It cannot be absolutely precise. Perhaps what you need is a path effect - we do have such an "envelope" effect with several control points, but currently it is disabled in svn, hopefully will be back for 0.47.

Just combine all the dots into a single path, and in Node tool, select all nodes and Alt+drag the middle one. If you have tablet, you can vary pen pressure to get different profiles of "sphericity".

Adobe Illustrator imports PDF and SVG just fine. These two formats are recommended.

Don't pay attention to what Windows reports - it's very unreliable Of course Inkscape does not rely on any Windows programs, it is a cross-platform and quite self-contained application. We did have some freeze on ungroup bugs, hopefully they are all fixed now.

Thanks, we really take usability seriously. You can start a new thread here, I think others will be interested to read your impressions too.

As a primary author of the engraving features in calligraphic pen, I would appreciate if you try to work with it and report your experience. Please try to use a recent SVN build, it has some improvements in this regard compared to 0.46.

Inkscape has a completely different UI layer and completely different internal data structures. So the only thing that would make sense to borrow is graphic algorithms. But here, Xara has little to offer except its fast renderer, which is not open sourced. For the rest, Inkscape has a lot more power...

I remember we had several requests, mostly from corel users, to make right-click on palette set stroke. Myself, I'm not for nor against this, and if someone codes this I will not object

this was recently fixed in svn

> I realize that this has been done via a new cross box on the left of the palette itself....But I think it is a shame that this new icon necessitates the use of the keyboard [Shift] key to remove stroke properties... No, you can right-click and choose Set stroke, or just drag it to object's stroke ...

> Then this object’s fill detail will be taken directly from the underlying objects and can then serve as a transparent blur object. I don't understand what is "transparent blur" and how it can "take" fill from background. Can you just draw an example image that would illustrate ...

Yes it is autoscroll. Drag on canvas in Selector and go up to the edge - it will scroll. Did you scroll it? No. It autoscrolled to help you do what you're doing.

Inkscape autoscrolls when you are dragging or drawing something, and therefore cannot use normal scrolling methods. But in Pen, even when you are looking for place for the next node, all the normal scrolling methods work (middle button, ctrl+arrows, scrollbars) so there's no need to autoscroll.

SVG supports filters, while XAML does not?

Different builds - stripped or unstripped? Different methods of looking up memory usage (I use System Monitor)? May be also you have hugely more fonts than I, and the font previews take that many memory... but that is very unlikely.

file a bug at bugs.launchpad.org/inkscape, there you can (and should) also attach the problem file

But as for improved memory usage, it doesn't look that much better. Right now after opening and closing lots of documents (some simple, some with lots of objects/data), it's at 136MB with one document open. When I first loaded that document (it happens to be the first I loaded) Inkscape was using 3...

Exactly this has been fixed in SVN version. Now memory is freed immediately after you close last window with the document. Given your interest in this problem (to put it mildly), I think it would be fair to ask you to download and test an SVN build, and report here a comparison. As for comparing to ...