Closed GoogleCodeExporter closed 9 years ago
Will the output always be valid HTML5? I guess so, which makes me think that it
might be useful to include a HTML5 validator (i.e. validator.nu) in Pipeline 2
to validate the output when writing tests for the stylesheet. wdyt?
Original comment by josteinaj@gmail.com
on 16 May 2013 at 1:36
Mmm, I think the validity of the output will very much depend on the validity
of the input. The upgrade stylesheet will mostly do basic translation.
More advanced content model fixing would be rather performed in the html-fixer
stylesheet.
Integrating an HTML5 validator generally makes sense, but I don't see how it's
useful for the unit tests: we can make sure the expected result is valid when
we write it.
Original comment by rdeltour@gmail.com
on 16 May 2013 at 1:45
For reference, here's the spec that summarizes HTML 5 changes from HTML 4:
http://www.w3.org/TR/html5-diff/
Original comment by rdeltour@gmail.com
on 16 May 2013 at 1:46
True.
The current stylesheet performs some cleanup, so I suppose the html-fixer will
be more important when we re-write the stylesheet, and they will in most cases
be run right after one another in most scripts.
Original comment by josteinaj@gmail.com
on 16 May 2013 at 1:50
Original comment by josteinaj@gmail.com
on 20 Jun 2013 at 2:24
see https://github.com/daisy/pipeline-issues/issues/315
Original comment by rdeltour@gmail.com
on 23 Jun 2014 at 2:31
Original issue reported on code.google.com by
rdeltour@gmail.com
on 16 May 2013 at 1:31