-
Notifications
You must be signed in to change notification settings - Fork 64
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
Add and handle val tags #938
Add and handle val tags #938
Conversation
@rettinghaus could you please resolve conflicts and then ping me for review? |
@bwbohl merge conflicts have been resolved. |
Thank you @rettinghaus. Please find some comments and open questions above. |
Thank you @rettinghaus for addressing the comments. Looks good to me. |
ODD meeting, May 25, 2022: Thank you @rettinghaus . @kepper will have a final look and check about consequences for the XLST workflows. |
Ping @kepper. Would you be able to have a look until the next ODD meeting? |
Merged at ODD meeting (July 2022). @kepper If you think that there is some change needed afterwards, please let us know. |
Thank you @rettinghaus for the improvements. |
This PR tries to address one part of #913 by unifying the handling of attribute values in the Guidelines.
Before values were treated very differently in different locations, sometimes they were in italics, sometimes in single or double quotes, sometimes in plain text. I tried to find every occurrence, wrap it into
tei:val
tags and added a corresponding css rule, so that every value should be shown in single quotes (as it is done in the TEI Guidelines). Furthermore I created a newguidelines.css
to collect specific rules there.Additionally this brings some typographically correct possessive apostrophes.