I think we should fix all files, by making any edit (e.g. adding ´<?xml version="1.0" encoding="UTF-8"?>´), as I did on the last mentioned file.
Since it does not affect newly uploaded files we might consider closing it.
It only affects files from ~March 2016? (e.g. 7.March 2016 to 27.March 2016)
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Mon, Sep 23
Aug 25 2024
Aug 4 2024
In T370044#10033078, @Glrx wrote:Could someone please check if this problem persists in more recent librsvg versions? Thanks.
Jun 11 2024
The last 3 version of https://commons.wikimedia.org/wiki/File:Oxygen480-mimetypes-image-vnd.dwg.svg already contains a workaround so that the last version renders at the preview-size of 120px.
Jan 14 2024
Dec 23 2023
Aug 23 2023
Aug 6 2023
mix-blend-mode is not part of the current SVG 1.1-Secifications, therefore ignoring is imho technically correct, see also https://github.com/RazrFalcon/resvg/issues/240#issuecomment-592200025 or https://github.com/RazrFalcon/resvg/issues/243#issuecomment-592811200
Jul 5 2023
I assume that is because the cache is not purged
Jun 11 2023
Jun 9 2023
@Glrx: According to T65236#8458679 the SVG-file has been fixed, could you provide an image that currently provides this issue and edit the task-description. (Otherwise I find it unclear&confusing.)
May 27 2023
I'm not shure if it helps if I provide simple SVG-examples with systemLanguage=
May 24 2023
Could someone update https://noc.wikimedia.org/conf/fc-list
May 23 2023
May 21 2023
description | SVG-file | librsvg 2.40(svgcheck) | librsvg2.44(Wikimedia) | librsvg2.56(Fedora38) | resvg | inkscape |
description | svg-file |
May 19 2023
again confirming fix
now the file is rendered according to SVG2.0 (resolved)
May 18 2023
librsvg2.52 will set the default to 96dpi see https://gitlab.gnome.org/GNOME/librsvg/-/issues/646, maybe we should set 96dpi.
it seems to be fixed
it seems to be fixed
file | current rendering 118px | current rendering 117px |
https://commons.wikimedia.org/wiki/File:Grundriss_Burg_Hageneck.svg |
May 17 2023
both not correct
confirm fix
confirm fix
The spacing in https://commons.wikimedia.org/wiki/File:Types_of_Sentences-pa.svg is still not perfect.
There might still be kerning issues, however I consider this issue as resolved.
Apr 26 2023
Apr 25 2023
Apr 20 2023
I think it is diffciult to reproduce it now, and this image is related to other rendering-bugs, therefore based on the comment by @Umherirrender in T228433#8794434 I close it as Resolved.
Apr 19 2023
@Umherirrender ; You have to compare the PNG not the SVG, because the rendering has several rendering librsvg-bugs
Mar 2 2023
Jan 25 2023
Jan 20 2023
In T282864#8544224, @taavi wrote:apt-browser displays which packages are available with a given component, and that's working correctly. It does *not* display which packages have been installed on a specific host.
librsvg which runs on Thumbor is still on strech
@Jdforrester-WMF : Please update the description at T216815 which currently states:
Upgade Thumbor from Debian stretch to Debian bullseye
Jan 19 2023
Jan 13 2023
I can reproduce this on Android 11.
Jan 5 2023
@Dzahn: Thanks and packing resvg from https://github.com/RazrFalcon/resvg/ might be out of scope?
Dec 20 2022
Maybe it is not buggy for the developers since I know only few cases wher SVGo couln't create an "optimized" SVG from a Commons-SVG, however those so called "optimized" SVGs are often broken (=don't render as intended). SVGo already broke too many SVG-files on commons, that's why (SVGo-)Users reuploading "optimized" SVG-files get reproved on commons, see Commons:SVG guideline for details. The damage-rate of any optimizer is way too high, expecially of the default settings of SVGo. Maybe you deactivated the most problematic ones. I just pointed out 6 common SVGo-Bugs for SVG-files on Commons on your talkpage. Can you tell me your settings and I can tell you the relevant bugs relating to those settings (even if you deacitate everything, svgo still breaks files).