Skip to content
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

Updates to correspondence display key #236

Open
kmcmullen opened this issue Feb 7, 2023 · 3 comments
Open

Updates to correspondence display key #236

kmcmullen opened this issue Feb 7, 2023 · 3 comments
Assignees
Labels
design design work/decisions

Comments

@kmcmullen
Copy link
Contributor

Text marked with <unclear> currently displays as grey font with a "[?]". I think that's fine, but we should explain what it means in the display key. We may want to consider whether it's too similar to the archivist note display...?

@kmcmullen kmcmullen self-assigned this Feb 7, 2023
@kmcmullen kmcmullen added the design design work/decisions label Feb 7, 2023
@kmcmullen kmcmullen changed the title Add unclear text display to key for correspondence Updates to correspondence display key Feb 9, 2023
@kmcmullen
Copy link
Contributor Author

We also need to account for metamarks in the key (these are the marks with blue shading that we originally created for the galley proofs). You can see one here: https://cdrhdev1.unl.edu/chesnutt/item/ccda.corr00152.

I think we can label them as "Proofreading mark"

@kmcmullen
Copy link
Contributor Author

kmcmullen commented Sep 10, 2024

I have added metamark/proofreading mark to the display key for correspondence on the dev branch:

. We'll just want to make sure this gets updated on production when we do our next push.

@kmcmullen kmcmullen reopened this Sep 10, 2024
@kmcmullen
Copy link
Contributor Author

The thing about unclear text still stand; I didn't tackle that yet

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
design design work/decisions
Projects
None yet
Development

No branches or pull requests

2 participants