Johannes Baiter

Which version of Mirador are you using? The plugin is currently incompatible with the bleeding edge version, if you use that, try switching to the last stable release (3.3.0, I...

Found the problem, the ALTO endpoint is missing the CORS header, which prevents the plugin from accessing the XML for parsing. Add the `Access-Control-Allow-Origin: *` header on the ALTO response...

Sorry guys, having a baby must have messed me up more than I noticed... Both of your manifests are IIIFv3, which currently is only supported on a development branch: https://github.com/dbmdz/mirador-textoverlay/tree/iiifv3...

I created a bare-bones manifest with the ALTO here (CORS-enabled): https://rawgit.com/jbaiter/d5fcd5f72349a6ad19ccb8f6e9e7d9db/raw/9ec3c5655d3749a4461103b49f06b674f6a7c440/bsb00084914.json Looks like right-to-left reading order works out of the box, so one thing less to worry about!  One...

Thanks for reporting,I think I've only really tested it with v2 annotations so far, although the code already has paths for v3 support. Should probably be only a question of...

Thanks for providing the full manifest, I'll try to find time to work on this, this week or next.

So, some long overdue updates on this front, sorry it took so long, thanks to everybody for the feedback! The example from the IIIF Cookbook now renders the annotations, **but**:...

Thanks for letting me know! I've updated the code to also look at `rendering` to discover referenced OCR files and fixed some other IIIF3 stuff related to annotations along the...

Found the problem: There's a mismatch between the Canvas size and the Image and OCR size: - Canvas: `3602x5000px` - Image: `3517x5000px` - OCR: `3517x5000px`

I just published 0.3.8 on npm, can you check if it fixes your problem?