Last modified: 2010-05-15 15:38:50 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T7261, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 5261 - SVG resizing uses bitmap interpolation not vector resize
SVG resizing uses bitmap interpolation not vector resize
Status: RESOLVED INVALID
Product: MediaWiki
Classification: Unclassified
File management (Other open bugs)
1.5.x
All All
: Low enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-03-15 23:40 UTC by keenan tims
Modified: 2010-05-15 15:38 UTC (History)
0 users

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description keenan tims 2006-03-15 23:40:18 UTC
The SVG renderer currently seems to render the image at the specified size, then
resizes it as a bitmap, resulting in poor-quality upscaling and overly-aliased
downscaling. Though not a major concern for Wiki software, it would be a
worthwile improvement to embrace the use of vector graphics over bitmaps.

See: http://en.wikipedia.org/wiki/User:Ktims/Sandbox/SVG for example.
Comment 1 Brion Vibber 2006-03-16 00:02:47 UTC
You've requested a rendering larger than the natural size of the image, which isn't 
allowed to avoid resource-hogging.
Comment 2 keenan tims 2006-03-16 00:05:39 UTC
Especially on commons, I'm not sure this is a good idea. Many vector images
don't have a 'natural' size and their size is determined by context. I think it
would be more appropriate to base the resource limitation on absolute size
instead. For iconography, the natural size might be quite small, however the
ability to increase the size losslessly may be useful.

A minor thing in any case.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links