Robert Sachunsky

Note: you are out of luck with OCR-D Docker images on MacOS. We base `ocrd/core` (used as basic build stage here) on `ubuntu:20.04`, which in principle is multi-platform, including arm64/aarch64...

But if you feel like trying it out yourself, checkout #151 and run `make docker` to build `ocrd/eynollah` yourself, or use `docker pull bertsky/eynollah` for something equivalent. The usage is:...

Also: When you `ocrd workspace clone --download /some/path/to/mets.xml` (**with** the download option) on a workspace which contains local files, the following happens: 3. a mets:file with only local path FLocat...

@kba this is a severe problem IMO.

Another example of this (trying to get ocrd_tesserocr tests to work on v3): ``` @fixture def workspace_kant_binarized(tmpdir): initLogging() with pushd_popd(tmpdir): > yield Resolver().workspace_from_url(METS_KANT_BINARIZED, dst_dir=tmpdir, download=True) test/conftest.py:15: _ _ _ _...

> It just didn't occur to me, I wanted to make the downloads reversible on the METS level but we can add the option to actually remove the files. Then...

> > It just didn't occur to me, I wanted to make the downloads reversible on the METS level but we can add the option to actually remove the files....

> If the `type` is string, then we don't need to (and should not) try to parse with JSON. That is probably the best solution here, right? Yes, I think...

I now have some realistic tests as well. But before I push these: Please help me understand a detail of the current implementation @kba: In … https://github.com/OCR-D/core/blob/79c61e303c87f229d5c96aedc0da31ef82b0f5d3/src/ocrd/task_sequence.py#L120 …the workspace instantiated...

cf. da7e960 i.e. need for `resolve_mets_arguments` is what I'm talking about.