Last modified on 19 August 2013, at 03:13

Commons talk:Transition to SVG

Return to "Transition to SVG" page.
Fairytale Trash Questionmark No.svg

This project page was nominated for deletion on 13 March 2011 but was kept.
The deletion debate is here. Please consider that decision before you re-nominate it.

العربية | বাংলা | Čeština | Dansk | Deutsch | English | Español | فارسی | Suomi | Français | Galego | עברית | Magyar | Italiano | 日本語 | 한국어 | Lëtzebuergesch | Македонски | മലയാളം | Plattdüütsch | Nederlands | Norsk bokmål | Polski | Português | Русский | Slovenščina | Svenska | Türkçe | Українська | +/−


Please remember that this talk page is not for questions and answers.

It is intended for discussing improvements to the Commons:Transition to SVG page.

Information icon.svg

For general help on SVG see Help:SVG

The best place for questions and discussion about SVG is the Graphics village pump


SVG also has the advantage that it is possible to internationalize a picture's text. Now, I don't expect mediawiki supposts SystemLanguage, but it is part of the standard. [1]Mobius 18:44, 9 December 2007 (UTC)

I expect. It will be very easy to implement. It is possible to use "uselang" attribute to make things happen. But will they? BPK (talk) 01:15, 8 August 2011 (UTC)
There's a patch for this, so yes, it's being worked on, FTR. Jarry1250 (talk) 20:21, 20 July 2012 (UTC)

Blur & ClonesEdit

The page claims that the gaussian blur filter is not supported; yet it does render (although rather buggily) in images such as Image:WP CSI image.svg. Stannered 16:17, 27 January 2008 (UTC)

It does not seem that buggy to me; On the other hand I seem t have problems with < use > (clones in inkscape) see Image:Portable Radio.svg for an example of working blur, and failing to render gradient in clones)

--Inkwina (talk contribs) 16:55, 22 March 2008 (UTC)

It doesn't appear that bad in larger images (or scaled-up images), but in smaller images (or scaled-down images) it's very noticeable - the blurred object is mispositioned upward and to the left (as if it is mistaking the post-blur Left and Top co-ordinates with the pre-blur ones somewhere along the line). It often makes drop shadows invisible and outside glows asymmetric and fugly. Stannered 17:12, 22 March 2008 (UTC)
For example, look at this: Portable Radio.svg Stannered 17:14, 22 March 2008 (UTC)
I too have noticed the bugginess of gaussian blur. One pixel in size makes a huge difference to the outputted image. I think it might be because my gaussian blur has a stddeviation>3. Anyway, here is my example:
Lightsaber Example
Dueling lightsabers.svg
Dueling lightsabers.svg
-- Tkgd2007 04:24, 9 April 2008 (UTC)
Hmmm, does look funny at those sizes, I was comparing to Firefox which does not seem to render the blur at all :-( But are you seeing the problem with clones in Image:Portable Radio.svg or is it just me? the grid should be black not red! FF renders this correctly. Anyway what can be done about it? I think we should try and collect a couple more examples and submit a few bug reports. --Inkwina (talk contribs) 07:19, 9 April 2008 (UTC)
Yes, I can see the problem (and it renders properly in Opera, too). Just about any image that uses a visible Gaussian blur can be made to show the Gaussian blur problem (the blur will also disappear at smaller pixel sizes - OK for shadows which you can't see at the smaller sizes, but disastrous for images like Image:Wiki notes.svg where I'd tried to blur the grey treble clef (see the old revisions). Stannered 09:49, 9 April 2008 (UTC)

Mediawiki uses Imagemagick to render SVGs, which in turn uses librsvg. This is an open source project and relies on all of us to report bugs, if bugs are not reported to the developers then they will never be fixed! I have reported the one to do with blurred objects vanishing, please do the same for any other bugs which you come across. Bitplane (talk) 01:16, 2 January 2010 (UTC)

VectorMagic starts chargingEdit

See [2]. Should we note this? Suggest something else? Marnanel 02:55, 23 February 2008 (UTC)

Yes, I think we should. Both, if possible. Globbet 09:33, 23 February 2008 (UTC)

Sizing of non-free images and logos under Fair Use RationaleEdit

Some instructions need to be added on how to control the size of thumbnails that doesn't make a mockery of the "low resolution" criterion of the Fair Use Rationale when uploading SVG images of logos, official seals, etc. While it's true that an SVG image can be smoothly scaled to almost any desired size, even big enough to fill a billboard, the default size presented in Wikipedia projects should be kept small to stay within the spirit of the rule. However, I haven't been able to find any information here in the Commons on how to limit the thumbnail preview to a specific size.

Most Infobox templates that I've encountered have a default image size of 220 pixels wide. It seems reasonable that the default size of SVG images that are under Fair Use Rationale should also be constrained to 220 pixel width, or smaller. The way to do this in Inkscape, I recently discovered by experimentation, is to apply a Transform/Scale operation to the entire image, set the units to "px" (pixels), check the "Scale proportionally" box, and then enter the actual pixel width desired in the Width box. Save or save-as the modified SVG file, then upload it to Wikipedia or Wikimedia Commons. As some SVG images are created by tracing a bitmap sample — the bigger the better — they acquire the pixel dimensions of the prototype, which can be HUGE. Once the artwork has been completed, this is a way to get it back down to reasonable preview size. —Quicksilver@ 20:18, 21 May 2010 (UTC)


Apparently the restriction is no longer present or not in general?

To give just four examples. Who has a bug example? -- Perhelion (talk) 19:05, 15 November 2010 (UTC)

I have complains about this policyEdit

Well, as author of an PNG image that other user forcibly converted to SVG version of poor quality and now attempting to replace original image in some Wikipedia articles, I have complains about this policy. Firstly, I think that SVG maps are bad image format compared to PNG. It is not possible to achieve certain standards with software that is designated for creation of SVG maps. Photoshop that can create PNG maps is undoubtedly superior to Inkscape or similar softwares. Also, there are many problems with SVG images: in original form, they cannot be viewed with some image viewing softwares, and if they are converted to PNG during download, their quality becomes even more bad. So, is there a way that SVG policy is modified a bit? I think that many other authors would be frustrated that PNG maps that they created are converted to crappy SVG versions of low quality. The current policy will prevent many people to draw something for this site. I do not see what problem some of you have with PNG maps? If they are free for use and accurate, I do not see a single reason why they should be converted to SVG. Due to that, is there a way that conversion of existing PNG images to SVG becomes "more difficult" i.e. that the users who would want to "convert" the image should be obligated to discuss whether author/uploader of original PNG image agrees with that conversion? If deletion proposals are discussed like that, why not "conversion to SVG"? The two processes are much similar by my opinion. PANONIAN (talk) 09:04, 22 January 2012 (UTC)

I also disagree with claim from this page that SVG images "could be edited more easily". On the contrary, I find editing of SVG images very difficult especially because they could not be edited with Photoshop software. For me, modification of an PNG, JPG, GIF or any other image compatible with Photoshop is much more easy than modification of an SVG image. PANONIAN (talk) 15:45, 22 January 2012 (UTC)
It's not necessarily easier or harder to create an SVG vs. creating a raster (they just use different skill-sets). However, it's often easier to edit an existing SVG (to translate into a different language, etc.) than it would be for a raster. I can understand not wanting to learn an entirely new way of doing things, but in several ways vector is kind of the wave of the future... Meanwhile, no one can "forcibly" replace a raster without going through a formal deletion nomination. Otherwise, it's really up to the individual Wikipedias which version to use. AnonMoos (talk) 05:27, 27 January 2012 (UTC)
Well, I can agree in one thing: it might be more easy to translate descriptions in SVG maps in other languages. However, this advantage is not a large benefit compared to various disadvantages of the software that is used for creation of SVG maps - there are some things that simply cannot be done with Inkscape and the problem of lower accuracy and lower level of details in SVG files remains (not to mention problem with transparent background of downloaded SVG files and problem of impossibility of viewing of such files with some image viewing softwares). I am only saying that SVG format should not be "imposed" here like this. It is one thing if there is a recommendation for users to use this format, but this recommendation should not be an obligation and we certainly should not replace PNG files of good quality with their SVG versions of much lower quality and accuracy. The second problem is the fact that some users misunderstood the SVG recommendation and they are actually believing that it is an obligation instead recommendation. What is a bad consequence of the pro-SVG policy? There are people who prefer to use PNG files instead of SVG. I am also among those people and it is not only that I prefer to draw maps in PNG format, but I also prefer to download maps created by other people in that format (my favorite image viewing software does not support SVG and therefore I consider SVG files completely non-useful for my collection of 40,000 maps that I collected over the years). Nevertheless, some people who creating maps for Wikipedia in non-SVG formats would be frustrated by the fact that some other users "converted" these files into SVG format (often of lower quality than original file) and are aiming to replace original image with that file. Due to the fact that I released maps that I created into public domain, I am aware of the fact that these files are completely free for further modifications and editing. Usually, I do not object if somebody change these maps in constructive way i.e. if changes that other users made in these maps are obvious improvements. However, if somebody aims to replace original PNG file with its SVG version of lower quality, that certainly cannot be described as an improvement and it is rather something that many other authors would describe as a "spoilage of their work". This will certainly destroy motivation of these authors for further contributions to this project, which certainly would not be a good thing. PANONIAN (talk) 06:51, 30 January 2012 (UTC)

Copying a free pictureEdit

I run a Mediawiki site. I like the Creative Commons release. I check the copyright. But if I try to copy a free picture that is SVG, it does not copy. I try to import it into my wiki, but it does not look correct. All I can do is copy the entire page and then crop out the picture. So you have destroyed the Creative Commons free and released to the public. My wiki is informational only. I make no money or any compensation in any form. kitchen remedies.