Bug 473662 - SVG import ignoring DPI
Summary: SVG import ignoring DPI
Status: CONFIRMED
Alias: None
Product: krita
Classification: Applications
Component: Layers/Vector (other bugs)
Version First Reported In: 5.1.5
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-08-23 01:00 UTC by Rafael Linux User
Modified: 2023-08-23 19:56 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rafael Linux User 2023-08-23 01:00:31 UTC
SUMMARY
***
When it comes to importing any simple SVG file, after entering the DPI requested by Krita from the user, the import is always performed at a resolution of just a few pixels. I have tried with different very simple SVG files and with DPIs from 72 to 1200, and all the times the result is a layer with a very low resolution image composed by very few pixels.
***

STEPS TO REPRODUCE
1. Open a image (HD, FHD ... 72 or 300 dpi)
2. Drag a SVG simple to Krita (as KDE or Plasma logo in SVG)
3. Enter 300 when asked for DPI for the rendered image

OBSERVED RESULT
Always get a new layer with a really low DPI, about 10x10 pixels

EXPECTED RESULT
To get a layer with the SVG rendered to user specified DPI

SOFTWARE/OS VERSIONS
Krita

 Version: 5.1.5
 Hidpi: false

Qt

  Version (compiled): 5.15.10
  Version (loaded): 5.15.10

OS Information

  Build ABI: x86_64-little_endian-lp64
  Build CPU: x86_64
  CPU: x86_64
  Kernel Type: linux
  Kernel Version: 6.4.9-1-default
  Pretty Productname: openSUSE Tumbleweed
  Product Type: opensuse-tumbleweed
  Product Version: 20230818
  Desktop: KDE

Locale

  Languages: es, es, es
  C locale: es_ES.UTF-8
  QLocale current: es
  QLocale system: es
  QTextCodec for locale: UTF-8

ADDITIONAL INFORMATION
Comment 1 Rafael Linux User 2023-08-23 19:56:01 UTC
I would like to suggest that it would be more interesting to ask for the size (width or height) than the density, since the user will always have an idea of how much he wants his imported image to occupy, instead of trying to import with different densities.