-
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JATS: support articleauthoring tag set #6014
Comments
Can you explain a bit more what you have in mind? Looks like we already switched from publishing to the archiving DTD. Are you saying that the response to #5511 (moving from inline footnotes to footnotes in fn-group in the backmatter) was needed only because we were using the publishing DTD, and now we can go back to inline fn elements? Perhaps it would be clearest if you just prepared a PR with the changes you propose. |
The JATS tag set can be set via the `jats-tag-set` meta variable. Recognized values are - `archiving` for the "Archiving and Interchange Tag Set", - `publishing` for the "Journal Publishing Tag Set", and - `articleauthoring` for the "Article Authoring Tag Set." Closes: jgm#6014
The JATS tag set can be set via the `jats-tag-set` meta variable. Recognized values are - `archiving` for the "Archiving and Interchange Tag Set", - `publishing` for the "Journal Publishing Tag Set", and - `articleauthoring` for the "Article Authoring Tag Set." Closes: jgm#6014
The JATS tag set can be set via the `jats-tag-set` meta variable. Recognized values are - `archiving` for the "Archiving and Interchange Tag Set", - `publishing` for the "Journal Publishing Tag Set", and - `articleauthoring` for the "Article Authoring Tag Set." Closes: jgm#6014
The JATS tag set can be set via the `jats-tag-set` meta variable. Recognized values are - `archiving` for the "Archiving and Interchange Tag Set", - `publishing` for the "Journal Publishing Tag Set", and - `articleauthoring` for the "Article Authoring Tag Set." Closes: jgm#6014
The JATS tag set can be set via the `jats-tag-set` meta variable. Recognized values are - `archiving` for the "Archiving and Interchange Tag Set", - `publishing` for the "Journal Publishing Tag Set", and - `articleauthoring` for the "Article Authoring Tag Set." Closes: jgm#6014
New formats: - `jats_archiving` for the "Archiving and Interchange Tag Set", - `jats_publishing` for the "Journal Publishing Tag Set", and - `jats_articleauthoring` for the "Article Authoring Tag Set." The "jats" output format is now an alias for "jats_archiving". Closes: jgm#6014
New formats: - `jats_archiving` for the "Archiving and Interchange Tag Set", - `jats_publishing` for the "Journal Publishing Tag Set", and - `jats_articleauthoring` for the "Article Authoring Tag Set." The "jats" output format is now an alias for "jats_archiving". Closes: jgm#6014
New formats: - `jats_archiving` for the "Archiving and Interchange Tag Set", - `jats_publishing` for the "Journal Publishing Tag Set", and - `jats_articleauthoring` for the "Article Authoring Tag Set." The "jats" output format is now an alias for "jats_archiving". Closes: jgm#6014
New formats: - `jats_archiving` for the "Archiving and Interchange Tag Set", - `jats_publishing` for the "Journal Publishing Tag Set", and - `jats_articleauthoring` for the "Article Authoring Tag Set." The "jats" output format is now an alias for "jats_archiving". Closes: #6014
JATS offers three different tag sets: archiving, publishing, and articleauthoring, with the latter ones being a subset of the preceding tag set. Pandoc currently uses the publishing set. Since the easy authoring of article is one of pandoc's great strengths, it seems reasonable to also support the most restrictive variant of these tag sets.
As far as I can tell, this would only require different handling of footnotes. The articleauthoring tag set does not allow
fn-group
as part of the backmatter, so<fn>
footnote elements have to be placed inline. All other changes can be handled in a custom template.The current behavior has been implemented in response to #5511.
The text was updated successfully, but these errors were encountered: