Currently, the web GUI is automatically prettied printed the outputs while in the CLI the user has not much clue how to do that. It is written in the help that any Saxon parameter can be passed, but how to pretty print then is still not clear. For me it feels that the used !indent=yes used in the call from the web GUI is hard to find out. Thus, I suggest to introduce a new parameter --pretty i
In addition to or replacing the ocrd-tool.json fields or README, it might make sense to encourage proper python documentation with docstrings on modul level at least for the processors and use that information for the generation of documentation.
Please debug your ocrd_tool.json file.
I found some errors:
<error>[tools.ocrd-kraken-binarize.input_file_grp] 'OCR-D-IMG' is not of type 'array'</error>
<error>[tools.ocrd-kraken-binarize.output_file_grp] 'OCR-D-IMG-BIN' is not of type 'array'</error>
<error>[tools.ocrd-kraken-binarize.parameters.level-of-operation] 'description' is a required propert
The current formulation of the setup guide recommends running the docker image individually for the individual processor CLIs (translating native commands to docker calls). This is one possibility, but I would not recommend it first/exclusively.
The current (fat) Docker configuration is tailored specifically for