BpDF edition 2: rename remaining HTML/CSS-unfriendly tags #21
castedo
started this conversation in
Baseprint Feature D's
Replies: 1 comment
-
|
A discussion post #22 is about HTML/CSS interoperability. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Following plan #18, testing has identified four more JATS tags where BpDF can be made more interoperable with modern HTML5/CSS technologies:
<article-body>rather than JATS<body><source-title>rather than JATS<source><license_ref>rather than JATS<ali:license_ref><title>(under<ref-list>)A separate discussion post will detail what I mean by interoperability with modern HTML5/CSS tech.
These changes are still JATS-transformable. They require trivial additions to the XSLT file transform of Baseprint XML to JATS already implemented in the compat/jats folder in the epijats repo.
JATS
<body>and<source>collide with HTML tags. The HTML DOMParser does not preserve/parse them properly when parsing Baseprint XML into an HTMLDocument object.<ali:license_ref>is not CSS addressable due to it using an XML namespace.ref-list/titlecollides with HTML tagtitle. It does not cause any major issue, butref-list/titleto date has not been used by any baseprints except to set the value to "References", which is a sensible default anyway. If there is a need to change this title in the future, a different more HTML-friendly tag can be introduced. For nowref-list/titlecan just quietly disappear, with only the default value living on.Beta Was this translation helpful? Give feedback.
All reactions