Improve usability of file types #4327
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ajrbyers
approved these changes
Jul 23, 2024
joemull
force-pushed
the
4326-file-type-usability
branch
from
6f39163 to
f5d821d
Compare
|
I've rebased this to make it easier to test openlibhums/typesetting#216 as that one was dependent on this and #4328, which is now merged. |
mauromsl
approved these changes
Aug 22, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #4326, or at least the first part of it.
This work was required to tackle openlibhums/typesetting#166 effectively, because without it users can't effectively manage proofing file types during typesetting.
A big part of making file types more usable is having consistent names and definitions. We should put these in the end-user documentation when we have a full list and are happy with the definitions. I've opened an issue for it here: https://github.com/BirkbeckCTP/memory-alpha/issues/42