Open PromiseDodzi opened 3 months ago
Current integration is done via the output file that you gave me. This is the file called manually-edited.tsv
. I'd suggest to run the code and then replace the manually edited file and run the cldfbench code again. This is the preferred way of handling it, rather than integrating parsers into the lexibank script. Ideally, you describe somehwere you you use your code to create the manually-edited.tsv
file.
Awesome! I get it perfectly. Thank you, Mattis.
We are working on making the parser(utils.py) even more accurate. We realize the current parser either under or over-parses some forms, eg. (e.g. bird) fly). Is there a way for us to integrate a more accurate parser into the workflow directly once this is ready?