Last modified: 2013-06-23 12:17:21 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 T15196, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 13196 - Screen all previously uploaded SVG files for invalid structure
Screen all previously uploaded SVG files for invalid structure
Status: REOPENED
Product: Wikimedia
Classification: Unclassified
SVG rendering (Other open bugs)
unspecified
All All
: Lowest normal (vote)
: ---
Assigned To: Nobody - You can work on this!
http://commons.wikimedia.org/wiki/Ima...
: shell
Depends on: 36040
Blocks: 16660
  Show dependency treegraph
 
Reported: 2008-02-29 17:01 UTC by Mike Startup
Modified: 2013-06-23 12:17 UTC (History)
3 users (show)

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


Attachments

Description Mike Startup 2008-02-29 17:01:38 UTC
I was trying to view the higher definition svg for Windows CE.

The following error message was given:

XML Parsing Error: prefix not bound to a namespace
Location: http://upload.wikimedia.org/wikipedia/commons/6/61/Windows_CE_Timeline.svg
Line Number 111, Column 4:			<use xlink:href="#lend4" transform="scale(-2.8333333333333,-2.8333333333333) "/>
------------------------^


Regards

Mike
Comment 1 Brion Vibber 2008-02-29 18:31:49 UTC
Yep, that's a bad file.

Currently, such files would be prevented from being uploaded. Older files already present have not yet all been screened.
Comment 2 Brion Vibber 2008-02-29 18:32:48 UTC
Changed summary to indicate what needs to be done.
Comment 3 Brion Vibber 2009-05-06 22:25:00 UTC
Tossing on fixup tracking bug 16660, though it's not 100% database cleanup :D
Comment 4 Brion Vibber 2009-08-03 16:53:50 UTC
Assigning SVG bugs to Ariel -- need a cleanup pass to see what's fixed up by a librsvg upgrade, what can be resolved with fixes to our font configuration, what can be fixed on our end, and what still needs to be pushed upstream.
Comment 5 Sam Reed (reedy) 2011-09-28 22:34:57 UTC
Do we even have a script to check the svg files?
Comment 6 Brion Vibber 2011-09-28 22:49:50 UTC
I don't think we have an explicit one...

Basically want to go through existing files & do equivalent of an action=purge to verify they come up as valid, then make a list of broken ones that need fixing.
Comment 7 Sam Reed (reedy) 2012-04-17 16:32:56 UTC
Closing as LATER due to lack of script to do this at the moment.
Comment 8 Andre Klapper 2012-12-12 13:38:15 UTC
[Removing RESOLVED LATER as discussed in
http://lists.wikimedia.org/pipermail/wikitech-l/2012-November/064240.html .
Reopening and setting priority to "Lowest".
For future reference, please use either RESOLVED WONTFIX (for issues that will
not be fixed), or simply set lowest priority. Thanks a lot!]

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


Navigation
Links