-
Notifications
You must be signed in to change notification settings - Fork 3
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
Set up export for Ed/Markdown #14
Comments
Here is a sample of an Ed edition done with semantic markup: Here is a sample of an Ed diplomatic edition of a ms. with additions and deletions: |
How will we deal with the georefences in the final edition? Probably we will want to keep them and make it easy for users to access the references and notes related to the entities. |
That could be an HTML span with a data attribute maybe? |
But in terms of the general purpose of Ed and doing an edition for simple reading with footnoted annotation, that might end up being just spans no one uses. Perhaps an option to export to markdown and markdown+ with extra semantic content? |
Speaking of which, notes ideally would end up being properly coded annotations. If the ids in issue #9 get resolved this should be no problem. |
In the Ed case, we would want appropriate TEI Header elements to become part of the YAML header of our average Jekyll .md page for Ed editions. TEI Body would then be converted to Ed-flavored kramdown in the content area.
Samples of all possible scenarios can already be found on the Ed demo:
Demo: https://minicomp.github.io/ed/
Repo: https://github.com/minicomp/ed
The text was updated successfully, but these errors were encountered: