Add IIIF 3 support #161
Merged
Add IIIF 3 support #161
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
Update all dependencies to their latest version, except OpenSeadragon. Update build scripts to make them compatible with latest Vite. Update Vitest config and move it to a separate file. Make the package a module and update required Node.js version to 18 and npm to 9.
Co-authored-by: ipf <[email protected]>
This adds support for IIIF 3 presentation and image APIs. All functions have been changed to only support IIIF 3, while IIIF 2 manifests are automatically converted to 3. - Update all components for IIIF 3 - Add a new localization function for strings from the manifest - Rewrite TOC panel to display actual structures instead of page ranges - Separate IIIF and other formats in export panel, remove unreliable literature management URL recognition - Re-order items in info panel, add support for homepages and logos - Add fallback language for items that are available neither in the current interface language nor in English
- Display document title in bold - Increase logo size so vertical logos are properly readable - Fix display of images in attributions
Note that only the German translation is complete, other language should be revised.
- Make TOC work with flat structures - Hide toggle-all buttons when there is nothing to toggle, add e2e tests
@iiif/parser v2.1 provides a separate "upgrade" module, which we now use.
- Add class for lists to better separate them from the website's styles - Remove bullet from single-item lists - Make "Related Resources" an actual list - Remove redundancy
Make sure no "related resources" are omitted when converting a v2 manifest to v3.
Issues with table of contents have been resolved. The first item is hidden according to IIIF requirements.
Use "at" instead of "slice" where appropriate.
With some manifests, the top level ancestor was not highlighted when the current element is deeply nested.
t11r
force-pushed
the
iiif3
branch
3 times, most recently
from
f9ff76a to
2820940
Compare
- Select manifest URL on focus for improved usability - Update input and button styles to match TIFY's styles - Shorten manifest input placeholder - Change close button shape to reduce title overlap
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.
No description provided.