[Clipart] [Bug 3745] broken files in collection

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Thu Aug 25 15:02:33 PDT 2005


Please do not reply to this email: if you want to comment on the bug, go to    
       
the URL shown below and enter yourcomments there.     
   
https://bugs.freedesktop.org/show_bug.cgi?id=3745          
     




------- Additional Comments From jonadab at bright.net  2005-08-25 15:02 -------
This bug used to have more info in it, before the RAID failure.  I'm going to
try to restore some of it, from my mail archives...

******************

           Summary: broken files in collection
           Product: openclipart.org
           Version: unspecified
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: clipart
        AssignedTo: clipart at lists.freedesktop.org
        ReportedBy: sas00003 at btinternet.com


There are a number of SVG files in the collection that have various problems. A
list of those I have found in release 0.15 is given below (at the end).

Five types of problem occur here:

* Unbound prefix. This means that a namespace prefix is used without having been
declared in the file. If the prefix is 'xlink' then adding the attribute
xmlns:xlink="http://www.w3.org/1999/xlink" to the root 'svg' element will fix
the problem. If the prefix is 'inkscape' (caused by an old Inkscape bug) then
the file can be fixed by removing all attributes that have the 'inkscape' prefix.

* Path has no d attribute. These files (most of which seem to be produced by
Sodipodi) can be fixed by removing the offending path elements (of which there
are often several), since these elements are presumably not intended to render
anyway.

* Mismatched tag. These files were trashed by a bug in one of the scripts, and
need to be recovered from an old version of the collection.

* No element found at line 1. These files are empty and should be deleted.
(Corresponding good files already exist in the collection.)

* Undefined entity. This is usually caused by HTML entities being used instead
of UTF-8.


  animals/birds/jonathon_s_duck_01.svg: parse error (unbound prefix at line 22
column 4)
  animals/fish/altum_angelfish_01.svg: parse error (unbound prefix at line 24
column 4)
  animals/fish/brown_fish_01.svg: parse error (unbound prefix at line 36 column 4)
  animals/fish/clown_loach_01.svg: parse error (unbound prefix at line 35 column 4)
  animals/fish/giraffe_cichlid_01.svg: parse error (unbound prefix at line 26
column 4)
  animals/horse_1_rotkevich_konsat_01.svg: parse error (unbound prefix at line
11 column 1)
  animals/mammals/horse_1_rotkevich_konsat_01.svg: parse error (unbound prefix
at line 11 column 1)
  computer/etiquette_cd-rom_01.svg: parse error (unbound prefix at line 6 column 4)
  computer/hardware/etiquette_printer_01.svg: parse error (unbound prefix at
line 6 column 4)
  computer/hardware/etiquette_scanner_01.svg: parse error (unbound prefix at
line 6 column 4)
  computer/icons/etiquette_printer_01.svg: parse error (unbound prefix at line 6
column 4)
  computer/icons/etiquette_scanner_01.svg: parse error (unbound prefix at line 6
column 4)
  computer/icons/lemon-theme/actions/reload.svg: path has no d attribute
  computer/icons/lemon-theme/apps/browser.svg: path has no d attribute
  computer/icons/lemon-theme/filesystems/home1.svg: path has no d attribute
  computer/icons/lemon-theme/filesystems/home13.svg: path has no d attribute
  computer/icons/lemon-theme/filesystems/home3.svg: path has no d attribute
  computer/icons/lemon-theme/filesystems/home5.svg: path has no d attribute
  computer/icons/lemon-theme/filesystems/home6.svg: path has no d attribute
  computer/icons/otto_02.svg: parse error (unbound prefix at line 13 column 6)
  education/otto_02.svg: parse error (unbound prefix at line 13 column 6)
  food/beverages/coffe_tea_01.svg: parse error (unbound prefix at line 35 column 4)
  logos/OpenClipArtLibrary/open_clip_art_librarylogo_02.svg: parse error
(unbound prefix at line 12 column 6)
  logos/OpenClipArtLibrary/open_clip_art_librarylogo_03.svg: parse error
(unbound prefix at line 9 column 6)
  logos/OpenClipArtLibrary/open_clipart_library_proposal_02_global_01.svg: parse
error (unbound prefix at line 6 column 4)
  logos/linux/tux_bulgarian_licho_lich_01.svg: parse error (unbound prefix at
line 17 column 2)
  logos/linux/tux_is_chilean_01.svg: parse error (unbound prefix at line 11
column 4)
  shapes/blokken_arjen_meijer_01.svg: parse error (unbound prefix at line 13
column 6)
  signs_and_symbols/AIGA_Currency_Exchange_2.svg: path has no d attribute
  signs_and_symbols/flags/america/canada/canada_new_brunswick.svg: path has no d
attribute
  signs_and_symbols/flags/europe/denmark/denmark_jutland.svg: path has no d
attribute
  signs_and_symbols/flags/europe/germany/germany_eastfrisia.svg: path has no d
attribute
  signs_and_symbols/flags/tux_bulgarian_licho_lich_01.svg: parse error (unbound
prefix at line 17 column 2)
  signs_and_symbols/map_symbols/AIGA_Currency_Exchange_2.svg: path has no d
attribute
  signs_and_symbols/usb_logo_philipp_e._imho_01.svg: parse error (unbound prefix
at line 47 column 8)
  unsorted/blokken_arjen_meijer_01.svg: parse error (unbound prefix at line 13
column 6)
  unsorted/cake_etienne_bersac_01.svg-repaired.svg: parse error (no element
found at line 1 column 0)
  unsorted/dcplusplus_icon_gergely__01.svg: parse error (undefined entity at
line 231 column 32)
  unsorted/dcplusplus_icon_gergely__02.svg: parse error (undefined entity at
line 233 column 32)
  unsorted/eiffel_tower_michael_jas_01.svg-repaired.svg: parse error (no element
found at line 1 column 0)
  unsorted/eye_01.svg: parse error (mismatched tag at line 58 column 2)
  unsorted/interlaced_ribbons_celt_01.svg: parse error (unbound prefix at line
84 column 4)
  unsorted/kubuntu_logo_yogesh_kani_01.svg-repaired.svg: parse error (no element
found at line 1 column 0)
  unsorted/mr_lakshman_s_poonyth_02.svg: parse error (unbound prefix at line 29
column 2)
  unsorted/sprint_cell_phone_joel_m_01.svg-repaired.svg: parse error (no element
found at line 1 column 0)
  unsorted/ubuntu_linux_logo_yogesh_01.svg-repaired.svg: parse error (no element
found at line 1 column 0)
  unsorted/usb_logo_philipp_e._imho_01.svg: parse error (unbound prefix at line
8 column 8)
  unsorted/woman_eye_01.svg: parse error (mismatched tag at line 58 column 2)
  unsorted/world_in_eye_01.svg: parse error (mismatched tag at line 66 column 2)
         
     
******************

------- Additional Comments From horkana at maths.tcd.ie  2005-07-11 03:06 -------
> * Unbound prefix. 

I'm pretty sure every file I've ever created for OpenClipart.org has this problem.  
I really do not want to see extra markup added to ever file for a few crappy
renders but I would love to see an SVG Tidy script to allow people to post
process their files to work with crappy software.  

One of our ancilliary goals is to promote the SVG standard and the last thing we
want to do is allow it to decend into a mess of really bad markup like HTML did.  

If we continue to use Batik and Adobe as our yardstick and be very conservative
about what mistakes we tolerate from other crappy renderers I'd be fairly happy
about it.              
     

------- Additional Comments From holger at treebuilder.de  2005-07-11 04:00 -------
ive fixed these errors for the 0.14 release, and i found this error (unbound
namespace prefix) is in fact an xml error, not an svg error. these files must be
considered not well formed. 

they not only break svg implementations:
Batik, mozilla, librsvg2
but also xml implementations:
msxml, saxon

also , if there is no default namespace, there will be no error, since xml alows
a document to be in the NULL namespace. but these files will not be SVG files,
since SVG requires a default namespace. so i suggest we should care about this
as well.

------- Additional Comments From sas00003 at btinternet.com  2005-07-11 04:50 -------
Alan Horkan writes:

> > * Unbound prefix. 
> 
> I'm pretty sure every file I've ever created
> for OpenClipart.org has this problem.

No, not at all. Of the 95 files in your pattern collection, 23 are broken due to
containing the null character (U+0000), which is not allowed in XML, but none
have any problem with unbound prefixes.

> I really do not want to see extra markup added
> to ever file for a few crappy renders

It's not every file that has this problem; in fact it's less than 1%. And some
of the files with the unbound prefix problem cannot be displayed by Batik or
Adobe, which I don't consider "crappy" renderers.

Moreover, any problem that causes reasonable XML parsers to choke on the files
needs to be fixed anyway, regardless of what SVG renderers do.

> One of our ancilliary goals is to promote the
> SVG standard and the last thing we want to do
> is allow it to decend into a mess of really bad
> markup like HTML did.

Yes, indeed.  So we should fix bad markup when we find it.

> If we continue to use Batik and Adobe as our
> yardstick and be very conservative about what
> mistakes we tolerate from other crappy renderers
> I'd be fairly happy about it.

I'm not suggesting that we should tolerate outright mistakes in renderers. But
we certainly shouldn't present renderers with bad SVG. Of the five types of
problem that I found, four cause the XML parser to fail (with good reason),
while the other one (path elements without a d attribute) is a violation of the
SVG spec.

******************          
     
     
--           
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email         
     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.



More information about the clipart mailing list