[krita] [Bug 473873] SVG scaling issue, transforming when it shouldn't and The grid snapping doesn't work

2023-09-01 Thread George Hayes
https://bugs.kde.org/show_bug.cgi?id=473873

--- Comment #4 from George Hayes  ---
The problem is it doesn't look the same. Why do all the extra transforms
when they are just added work for no reason.
You simply created more work for system while getting no benefit at all
from it if anything it made it worse.

On Wed, Aug 30, 2023 at 9:12 AM Alvin Wong  wrote:

> https://bugs.kde.org/show_bug.cgi?id=473873
>
> --- Comment #3 from Alvin Wong  ---
> Again, Krita is not a general purpose vector editor. Its vector
> capabilities is
> to allow adding vector shapes to a drawing or painting primarily for raster
> output. It does not aim to preserve the original SVG markup exactly as-is.
> It
> can and will change the representation of paths and shapes and apply
> various
> transform as long as the visual output looks the same. This is not going to
> change any time soon.
>
> If the raw values of paths is important to you, I strongly recommend you
> use
> Inkscape instead of trying to get what you look for using Krita.
>
> I only marked this issue as "confirmed" for the unintuitive handling of the
> document DPI on exporting as SVG.
>
> --
> You are receiving this mail because:
> You reported the bug.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 473873] SVG scaling issue, transforming when it shouldn't and The grid snapping doesn't work

2023-08-30 Thread Alvin Wong
https://bugs.kde.org/show_bug.cgi?id=473873

--- Comment #3 from Alvin Wong  ---
Again, Krita is not a general purpose vector editor. Its vector capabilities is
to allow adding vector shapes to a drawing or painting primarily for raster
output. It does not aim to preserve the original SVG markup exactly as-is. It
can and will change the representation of paths and shapes and apply various
transform as long as the visual output looks the same. This is not going to
change any time soon.

If the raw values of paths is important to you, I strongly recommend you use
Inkscape instead of trying to get what you look for using Krita.

I only marked this issue as "confirmed" for the unintuitive handling of the
document DPI on exporting as SVG.

-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 473873] SVG scaling issue, transforming when it shouldn't and The grid snapping doesn't work

2023-08-29 Thread George Hayes
https://bugs.kde.org/show_bug.cgi?id=473873

--- Comment #2 from George Hayes  ---
I did some further testing. I imported the following svg.
http://www.w3.org/2000/svg";>


To get the correct scaling in the image it was done at 256 to get to the right
size with the default 300pixels per inch and 0.43 print under scale image. But
the positioning is off.
If I change it to 128resolution and 1in 128 with and 128 height. It scales
perfectly at and positions perfectly.
However, if I then export that very same layer. It changes it to what is below
which again is shrunk in size and transformed.
The new svg it creates can't even be properly imported back in sized and
positioned without work.
My suggest is drop the transformation let the people printing it worry about
that just focus on getting the point position and so on right.
Don't worry about the DPI that is an issue for the people print software.

http://www.w3.org/TR/2001/REC-SVG-20010904/DTD/svg10.dtd";>

http://www.w3.org/2000/svg"; 
xmlns:xlink="http://www.w3.org/1999/xlink";
xmlns:krita="http://krita.org/namespaces/svg/krita";
xmlns:sodipodi="http://sodipodi.sourceforge.net/DTD/sodipodi-0.dtd";
width="72pt"
height="72pt"
viewBox="0 0 72 72">




-- 
You are receiving this mail because:
You are watching all bug changes.

[krita] [Bug 473873] SVG scaling issue, transforming when it shouldn't and The grid snapping doesn't work

2023-08-29 Thread Alvin Wong
https://bugs.kde.org/show_bug.cgi?id=473873

Alvin Wong  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 CC||al...@alvinhc.com
 Status|REPORTED|CONFIRMED

--- Comment #1 from Alvin Wong  ---
Yes, there are some confusing aspects of how vector layers are being handled in
Krita. In particular, the current implementation of vector layers always use
"pt" (1/72 inch) as the unit and that is why it is used in the exported SVG. It
also takes into account the document resolution, and since your document is set
to 300 ppi, 1 pt = 4.166... px (document) and therefore 128 px (document) =
30.72 pt. This makes sense to match the "print size" of the document. For web
usage, since the CSS defines px to be exactly 1/96 inch, the document should be
set to 96 ppi to match that.

But also unintuitively, even if you resize the image changing only the
resolution to 96 ppi, exporting the layer immediately still gives you the same
dimensions. This is because at this point the scale is only applied to the
layer and not the shapes inside (an oddity of the implementation of "scale
image"). To fix that, you have to clone the layer and export the cloned layer,
or save then reopen the file.

Tl;dr: Don't use Krita as a general purpose vector editor; it's not. Use
Inkscape for that.

-- 
You are receiving this mail because:
You are watching all bug changes.