You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While using ocrd-fileformat-transform, I was thinking about some modifications which I'd like to discuss:
Wouldn't ocrd-transform be sufficient as name instead of the current lengthy one?
from-to is a strange parameter name. I see no technical need to inherit the specific needs of ocr-fileformat here and would prefer two parameters from and to. Are there use cases where from cannot be omitted? Technically it should be possible to derive it for all entries in the input file group, and typically it will simply be PAGE. So most users will only have to provide a to parameter or – if it defaults to `ALTO – no parameter at all.
The text was updated successfully, but these errors were encountered:
While using
ocrd-fileformat-transform
, I was thinking about some modifications which I'd like to discuss:ocrd-transform
be sufficient as name instead of the current lengthy one?from-to
is a strange parameter name. I see no technical need to inherit the specific needs ofocr-fileformat
here and would prefer two parametersfrom
andto
. Are there use cases wherefrom
cannot be omitted? Technically it should be possible to derive it for all entries in the input file group, and typically it will simply bePAGE
. So most users will only have to provide ato
parameter or – if it defaults to `ALTO – no parameter at all.The text was updated successfully, but these errors were encountered: