It's "numericprecision" attribute in preferences.xml. See: http://kaioa.com/node/25

Soda wrote:Thank you for you answer. It seems to be a bug and no good solution appear

It's not a bug - it's a shortcoming of the current implementation, which was optimized for speed instead of quality.

By the way the proper term for this kind of artifact is banding.

Pretty weird. Inkscape finds your inx, but fails to find the py. Interestingly it also fails to find inkex.py.

Hum. Do other extensions work?

For the mime stuff... see:
How to Configure Apache to Serve SVG/SVGZ the Right Way

Made it point to the sf.net project page. Thanks for pointing this out.

Try being more specific.

OS, error messages, anything that could be of any use...

>[...]maximum contrast which accentuates the flaws. Well said. Just take the small 110x110 image and zoom in to 800%. The "stroke" of the "fine print" don't even cover a whole pixel. Well, if you replace "www" with "WWW" and "com" with "COM"...

Ehm... the DPI of a PNG don't change anything on screen. Each pixel is one pixel and that's it.

Show us the SVG and the PNG.

It's a lot easier and faster this way.

>I just seen a Samsung 1080p monitor that's 22". I thought 1080p would start at 26" or more. I would be keen see what a desktop looks like at that res.

The DPI are similar to a 19" CRT @ 1152x864. It's comfy.

I guess the required trailing empty line was missing. That was some bug in Gimp's original parser, which survived the transition. It got fixed in Gimp first and then in Inkscape.

Also if you use any special characters be sure to save as UTF-8.

a) Not enough free space

Make some.

b) Installer broken

Download it again.

>All widescreen monitors are the same ratio[...]

There is 16:9, 16:10, 5:3, and a few bastardizations thereof.

In this context "babelfish" refers to machine translation. And yes, this issue is specific to Inkscape's renderer. Firefox, Opera, Batik, and everything else I tried is able to render patterns without visible seams. Basically they all render to texture first and then handle it like a usual...

00Inkscape wrote:same problem
https://bugs.launchpad.net/inkscape/+bug/314672

WTF? Babelfish? Well, if it's about those seams... that bug report is a duplicate.

>Solution?

Use a different SVG renderer. E.g. Batik.

I gave all guides a matching ID. E.g. the one at 190px got the ID "x_190px". This makes it easier to reposition accidentally dragged guides (in case you can't just undo it... since you didn't notice it right away).

#1 Don't use outlines.

It's RGB. CMYK isn't supported yet, but it's already on its way.

MMB=middle mouse button (this is usually the mouse wheel)

Just hold MMB and drag the canvas around.

Panning the canvas around with MMB-drag is a lot nicer than using the scrollbars though.

a) Use the grid.
b) Use the align/distribute dialog.

I made some templates for the 960 Grid System.

Give it a whirl if you got some spare time. I think I got everything covered. Any suggestions for improvements are welcome.

>And aho, do you know if that issue is going to be fixed in version .47?

Unfortunately I don't know if anyone is working on this. But I'm pretty sure it's going to be addressed at some point (at least for PNG export).