Commons:Graphics village pump/September 2020

Option to bypass rsvg and just view the SVG on pages

Everyone knows rsvg is absolutely terrible at text rendering and has shown very few signs of getting any less terrible, along with its many other bugs. Will there ever be an option to just display the SVG directly instead of forcing conversion every time? The whole convert-to-PNG workaround is very early 2000s, every browser I've used for the last decade is at least as fast as loading the thumbnail, and significantly better quality. SilverbackNet^talk 05:33, 17 September 2020 (UTC)

We've tried to get SVG to appear natively in Mediaviewer in 2016 but it got nowhere. If you wish to revive it, please see https://phabricator.wikimedia.org/T138665 for the job tracker. Good luck! cmɢʟee ⋅τaʟκ 09:50, 17 September 2020 (UTC)

The task https://phabricator.wikimedia.org/T134455 really seems to be the most related one. The larger task is way out of scope for this. So a patch is there, but no one wants to triage or add it even experimentally; it would do me no good to write another one that no one wants to deal with. I couldn't care less about MediaViewer, it's just basic thumbnails on pages that matter. SilverbackNet^talk 23:40, 19 September 2020 (UTC)

SVG image updating

Yesterday I made an updated version of the SVG image Europe 814.svg, but the updated version can be seen in a specific width, mobile version of Wikipedia, and so on. It's like the updated version is uploaded but is still loading. Why is this happening? Are the uploading and loading gradual? Is it common for updated images, with SVG format...?--Miki Filigranski (talk) 23:09, 19 September 2020 (UTC)

Yes, caching has been an issue for over a decade. You can flush cache by appending '&action=purge' to any link, but since anyone can customize their image sizes, you can't do that universally. After a day or two it'll be fixed for everyone. SilverbackNet^talk 23:29, 19 September 2020 (UTC)

@Miki Filigranski and SilverbackNet: See also COM:PURGE.   — Jeff G. ツ _{please ping or talk to me} 23:38, 19 September 2020 (UTC)

Ok, thanks!--Miki Filigranski (talk) 07:14, 20 September 2020 (UTC)

@Miki Filigranski: You're welcome.   — Jeff G. ツ _{please ping or talk to me} 10:31, 20 September 2020 (UTC)

Resolved

SVG colors don't change

Hey, there's an issue I'm having with a file replacement. File:NHL teams and conferences_map - 2017-18.svg has a dot representing Las Vegas, but the dot is the wrong colour - it is orange when it should be red. In an attempt to fix this, I opened up the SVG in a text editor, and thankfully every city marker is listed under a section named <g id="Symbols">, if you're interested in checking in out. In there, they each have a parameter defining what colour they are (smythe_city for red, norris_city for orange, patrick_city for green, and adams_city for blue). I changed the Las Vegas marker from "norris" to "smythe", and went to upload a new version. The dot even looked red on the preview before I actually uploaded it. But once I uploaded it, my change just seemingly wasn't there, the dot was still orange. I downloaded the replaced SVG, and my change just didn't exist in the XML. Did Wikimedia just somehow ignore the change of a single parameter? I'd appreciate if someone could help me out. Thank you.

SnowyNix (talk) 17:27, 28 September 2020 (UTC)

@SnowyNix: , I see that you've already gone in and apparently resolved this for this particular file, but it looks like there probably wasn't any actual problem, the cache just hadn't been purged yet, leaving the old version of the image showing. When uploading a new version of an SVG, I always have to purge the cache before the new changes show up. I use the UTCLiveClock / LocalLiveClock gadget in my preferences so that I have a nice purge button always available in the top right corner of every page, and I literally hit it every time right after I upload a new version of a file.

The reason why files don't instantly update is that Wikimedia is run through hundreds of different servers at the same time, but you only get to interact with one at a time. The change you upload only exists on one of those servers until it can be propogated to all the others. In the time that takes, you've already called up to load the file page, and there's only a miniscule chance that you would happen to get the page from the exact same server you uploaded the new version of the file to. Purging just tells all of the servers to let go of their old version and download the new updated master version of that page. VanIsaac (en.wiki) 22:38, 28 September 2020 (UTC)