Since the scripts.build module manages calling scripts.tsv2lmf.convert(), there was no longer a need for tsv2lmf.py to be directly callable from the command line, at least for OMW data. But it now occurs to me that there are other wordnets (namely KurdNet) that uses the OMW methodology but isn't included in OMW, so for supporting these wordnets it would make sense to make tsv2lmf.py callable for a single resource.
For this to work, it needs to better handle paths, like for log files and CILI files, that might not be in the locations OMW expects. Otherwise it should be simple to add a main() function and some argparse front end.
Since the
scripts.buildmodule manages callingscripts.tsv2lmf.convert(), there was no longer a need fortsv2lmf.pyto be directly callable from the command line, at least for OMW data. But it now occurs to me that there are other wordnets (namely KurdNet) that uses the OMW methodology but isn't included in OMW, so for supporting these wordnets it would make sense to maketsv2lmf.pycallable for a single resource.For this to work, it needs to better handle paths, like for log files and CILI files, that might not be in the locations OMW expects. Otherwise it should be simple to add a
main()function and someargparsefront end.