|
CoverageInfo
Simple ODF specification coverage analysis
IntroductionI wrote a small coverage analysis utility: odf2html/trunk/tests/coverage.py. It runs from within tests subdirectory and requires Python and built all-in-one.xsl. Any suggestions are appreciated. Here are it's run results against all-in-one.xsl rev.292 : Details./coverage.py Fetching all element/attribute names from OpenDocument schema: 524 elements, 1130 attributes fetched Fetching supported elements/attributes from odf2html XSL: 89 elements, 97 attributes Overall elements coverage: 16.98%, attributes coverage: 8.58% Elements coverage: text: 29 of 169 (17.16%) style: 18 of 39 (46.15%) office: 13 of 26 (50.00%) table: 10 of 94 (10.64%) draw: 6 of 44 (13.64%) dc: 5 of 6 (83.33%) meta: 3 of 14 (21.43%) number: 3 of 26 (11.54%) presentation: 1 of 20 (5.00%) svg: 1 of 9 (11.11%) anim: 0 of 12 (0.00%) chart: 0 of 21 (0.00%) config: 0 of 5 (0.00%) dr3d: 0 of 6 (0.00%) form: 0 of 30 (0.00%) math: 0 of 1 (0.00%) script: 0 of 1 (0.00%) xforms: 0 of 1 (0.00%) Attributes coverage: fo: 33 of 58 (56.90%) style: 21 of 184 (11.41%) table: 13 of 155 (8.39%) text: 9 of 133 (6.77%) meta: 7 of 15 (46.67%) draw: 6 of 200 (3.00%) svg: 5 of 64 (7.81%) office: 1 of 20 (5.00%) presentation: 1 of 52 (1.92%) xlink: 1 of 5 (20.00%) <no namespace>: 0 of 5 (0.00%) anim: 0 of 11 (0.00%) chart: 0 of 61 (0.00%) config: 0 of 2 (0.00%) dr3d: 0 of 40 (0.00%) form: 0 of 68 (0.00%) number: 0 of 24 (0.00%) script: 0 of 3 (0.00%) smil: 0 of 29 (0.00%) xforms: 0 of 1 (0.00%) Totally ignored namespaces: anim, chart, config, dr3d, form, math, script, xforms |
Sign in to add a comment
