After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 574544 - Text coming out wrong size when SVG scaled to funny resolution
Text coming out wrong size when SVG scaled to funny resolution
Product: librsvg
Classification: Core
Component: general
Other All
: Normal normal
: ---
Assigned To: librsvg maintainers
librsvg maintainers
Depends on:
Reported: 2009-03-08 12:29 UTC by Rupert Millard
Modified: 2017-12-13 17:35 UTC
See Also:
GNOME target: ---
GNOME version: ---

Small test case (5.26 KB, application/x-compressed-tar)
2009-03-08 12:30 UTC, Rupert Millard

Description Rupert Millard 2009-03-08 12:29:54 UTC
Please describe the problem:
Problem first noticed on the Wikipedia. When an SVG was scaled down, the text came out disproportionately small.

Steps to reproduce:
I have created a small example, and will attach it to this report.

Render test_bad.svg at full-size and then scale it down to 50%.

	rsvg test_bad.svg test_bad_full.png
	convert test_bad_full.png -scale 50% test_bad_full.png

Render test_bad.svg at half-size:

	rsvg -h325 test_bad.svg  test_bad_half.png

Actual results:
The text is too small in the one that was rendered by rsvg at half-size.

Expected results:
The text be the same size.

Does this happen every time?

Other information:
Comment 1 Rupert Millard 2009-03-08 12:30:54 UTC
Created attachment 130275 [details]
Small test case
Comment 2 Rupert Millard 2009-03-08 12:32:47 UTC
Just to add that if you take away the <path> element, the text scales properly. (See test_ok.svg)

Many thanks,

Rupert Millard
Comment 3 Perhelion 2014-04-08 23:10:32 UTC
I could not that reproduce.
Comment 4 GNOME Infrastructure Team 2017-12-13 17:35:50 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: