Used save as pdf function many times before, but now there seems some problem with it.
It happens that now the pdf save function uses the complete svg standard, and saves totally different things as displayed in inkscape.
The attached file shows the original svg, and two pdf-s -one with 1.4, one with 1.5 pdf version save function.
The original rectangle was scaled, and the line width got scaled too -so now it's different along x and y axis.
Ran into something different as well, that when the save as pdf produced rotated rectangles instead of the svg's non-rotatedly displayed ones.
Is there a way to correct this "error"? This makes drawing blindfolded.

I'm running an Inkscape 0.48.4 r9939 version.

Anyone noticed the same thing happen?

Lazur URH wrote:Used save as pdf function many times before, but now there seems some problem with it.

Did you recently change the preferences how Inkscape stores transformations (default: optimized)?

Workaround in 0.48: revert the Inkscape preferences for how transformations (of paths, and rects) are stored to the default (optimized), select all objects and nudge them with the cursor keys (e.g. a tick to the left and back to the right). This will trigger a rewrite of the path data, as well as of the parameters of the rects in your SVG file, and the stroked paths and rects will no longer appear non-uniformly scaled in PDF exports, as well as when displaying the SVG file in other SVG viewers.

[ The PDF export correctly interprets the SVG file according to the SVG specification - it's inkscape's old renderer (used in current stable versions) who gets it wrong - you can e.g. view your SVG file in the web browser of your choice, and it will render the stroked rectangles like the result you see in the PDF file exported by inkscape.

Note: The next major version of Inkscape (with its new renderer) will display the SVG according to the spec too. ]