Sun, Apr 11
Sat, Apr 10
The code should never be looking for underscores in a systemLanguage attribute.
I noticed that one user made several Kurdish translations in Arabic script that failed to show up. Looking at the SVG, the files had systemLanguage="ku_ARAB" instead of systemLanguage="ku-Arab" (capitalization is not important).
Sun, Apr 4
Sat, Apr 3
I would decline this request. The creator should always specify a size.
Fri, Apr 2
This basic problem is reported in T270889.
Mar 10 2021
Thanks for the note about @ sections. I'd like to see support for (color) and not (color), but that is beyond SVG 1.1.
Thanks for running the test. Resvg has more support than I expected.
Mar 9 2021
Thanks for trying it.
Mar 8 2021
IIRC, resvg uses a simple CSS parser. Could you try rendering
tests several SVG 1.1 (CSS 2) selectors.
Mar 2 2021
First, the indicated SVG file, https://commons.wikimedia.org/wiki/File:Multilingual_SVG_example.svg has one switch element with several language clauses. Currently, it does not have a default final clause (i.e., a text element without a systemLanguage attribute). Consequently, if there is not an explicit langtag match, the switch element should not render any text. For the case of "(default language)", no text should be displayed.
Feb 28 2021
I was faked out. Long ID names do work. The file probably has other issues (linearGradient, isolation:isolate, or mix-blend-mode:overlay).
Two proposals: increase the number of bytes read or shift multilingual testing to upload time (when the file is read anyway).
Feb 27 2021
I would close this issue as won't fix.
Nov 25 2020
My current understanding is that WMF already does some sanitization of SVG files.
Nov 20 2020
Where to begin?
Oct 17 2020
SVG language name handling is a mess on many levels.
May 14 2020
This issue is the same as T36947. Font sizes in original Command_Pattern.svg were below 5px.
May 10 2020
The tool should also give a reasonable error message for
May 5 2020
possibly same issue as T221382 which identifies CSS selectors as a problem and points to a discrepancy in appConfig.translations
May 4 2020
The message looks OK (but beware that a single text element may have dozens of nested tspan elements.
I vote for fixing the files on Commons. Every XML file should start with an XML processing instruction.
May 3 2020
I think this falls out from the inner workings of Commons. Commons tells the world the file is plain text, so why should SVG Translate believe otherwise?
Apr 30 2020
Apr 29 2020
The nested tspan is not "erroneous code" but rather legitimate SVG that the tool does not support.
Apr 28 2020
- Failing to give a reasonable message for this case looks like a bug. The SVG file contains text. A reasonable user saw the text, wanted to translate that text, and fired up the translate tool. Then tool told him there is no text to translate. Why shouldn't the user take that as anything but a counterfactual. There's an elephant in the room and the tool is telling the user it does not see an elephant.
Apr 18 2020
Apr 17 2020
I would close this ticket as Won't Fix.
Apr 12 2020
Bug hunting is made tedious by the inability to flush the tool's cache. The file must be uploaded to Commons to run the tool, so I've been overwriting the original file and overwriting Test.svg to do tests. After two tests, I need to wait half a day. I did not want to upload a bunch of spurious files just to test ideas.
Aug 12 2019
The original file has a two-line label of "Observation" "Screen".
Jul 20 2019
Jul 18 2019
https://gitlab.gnome.org/GNOME/librsvg/issues/48 GNOME 48 "[BZ#641823] transform="rotate(x)" causes incorrect gradient rendering."
Jul 17 2019
Jun 20 2019
I've skimmed the comments going back about 2.5 years. It looks like most bases are covered.
Apr 30 2019
Looking at Meta SVG fonts.svg suggests:
I've been thinking about this request. Adding more fonts seems like it must be a good idea, but many of the fonts above raise questions. Do we need Fira Sans, Linux Biolinum, Cardo, Junicode, Vollkorn, or Avocado? That a font is free is a requirement for Commons, but that does not mean that every free font should be loaded onto Commons. So I'm left to ponder the meaning of "Missing fonts".
Feb 15 2019
should be subtask of T215835
There was a problem with File:999-percentages.svg when used on toolforge. I suspect toolforge cached a local copy of the file. I uploaded a new version of the file to Commons and purged the Commons File: page. I suspect the purge invalidates conventional WMF servers but not toolforge's cache. Toolforge probably thinks the file is still fresh, so it does not contact Commons to see if the file is still current.
Feb 14 2019
File:999-percentages.svg had issues.
Original SVG preview shows. Changes do not show and trigger another popup.
Should be sub of T215835
No, you should not overlook any transform.
The file has text element stroke and fill properties countermanded by tspan elements. Generally, text should not be stroked in an SVG file unless one is looking for special effects. The "Pinna" rendering is the most dramatic for the bug. Look at "Pinna" in the tool's rendering; only the strokes are visible and the fill is none. On Commons, the text is not stroked but filled with saturated red.
The bug looks like the tool scanned the switch element:
Feb 13 2019
The sustainable text starts out as
Feb 11 2019
I edited File:Human leg bones labeled.svg to clean it up and fix the leaders. Originally, the text elements looked something like:
When the page loads, "sustainable" appears on the image over the radial fill, but then the image is overwritten and "sustainable" disappears.
Just a note about the original files.
Feb 10 2019
These issues arise from the underlying graphics, which are less than ideal for translation.
Jan 4 2019
Thank you for the progress update. I'm happy to hear the good news.
Jan 3 2019
The 380kB file in T212660
Dec 3 2018
This ticket is similar T180923, which complained about fc-list and unknown fallbacks.
Dec 2 2018
My take is it is bad. The fc-list should be an accurate reflection of the fonts available to librsvg. I think that problem was raised in another librsvg ticket.
Nov 11 2018
Nov 2 2018
A better option would always serve small (say less than 20kB) SVG files.
Oct 30 2018
Gnome closed issue 319 on 23 August 2018 with commit https://gitlab.gnome.org/GNOME/librsvg/commit/3d84acca9c11482cb0d2f75d379086be21bd4c91
Oct 24 2018
The good news: Gnome #131 and Gnome #256 have been closed.
Oct 19 2018
Sep 13 2018
The cited example is from File:Neural_crest.svg
Sep 6 2018
Sep 5 2018
There are several issues.
Aug 29 2018
Ignoring subscripts, font shifts, and other exotica:
Aug 17 2018
The Translation possible - SVG category is/was an invitation to use SVGTranslate on the file or to use a graphics editor to change the strings and upload to a new file name.
Aug 16 2018
Aug 15 2018
Kelvin13 might have good advice. He wrote this page of related guidance (that I just found) https://commons.wikimedia.org/wiki/User:Kelvin13/SVG_text_tutorial , which I wish I had seen a few days ago when I was converting an SVG!
Aug 14 2018
I commend Nikerabbit's brain dump. I'm having trouble paging all the details back in.
Aug 10 2018
Adding TheDJ because this is similar to T201274
Aug 9 2018
Tried to do manual upload, but had problems.
Aug 7 2018
Aug 6 2018
I ran SVGTranslate on [[File:Planetary transit.svg]] and keyed in some bogus translations.