Konstantin Baierer

OK, then let's not include this PR in the next release and focus on fixing the permission error during image build.

I tend to resort to package.json + webpack once dependencies become non-trivial.

See also: https://hackmd.io/g-8QuOAnSQeqnb8PRNjFbQ (ht @bertsky) - https://github.com/OCR-D/ocrd-website/blob/master/site/en/developer-guide.md (not linked into ocr-d.de) - https://github.com/OCR-D/ocrd-website/blob/master/site/en/dev-best-practice.md (linked into ocr-d.de) - https://github.com/OCR-D/ocrd-website/wiki/OCR-D-Code-Review-Guidelines (new, just on the Wiki)

Right, I forgot that you already implemented this. The example above was just a basic draft. I would be fine with formalizing your solution here in spec, so it can...

Widely implemented but not defined in our spec. Should be remedied.

With #206, range can expressed with `{exclusiveM,m}{ini,axi}mum`.

> I strongly recommend the introduction of a third GT subset devel. @wrznr Can you elaborate?

@Doreenruirui's work on okralact has diverged significantly from these specs. It makes little sense to publish these specs with the only implementation implementing it differently. @doreenruirui can you compare your...

@Doreenruirui We're discussing these changes/new files: https://github.com/OCR-D/spec/pull/105/files. In particular I would like to harmonize the proposal here (https://github.com/OCR-D/spec/pull/105/files?file-filters%5B%5D=.md#diff-2ae93b1f468c44b9f7e195133a0fb539) of using BagIt for the line GT with your approach in okralact...

c.f. https://github.com/OCR-D/spec/issues/55