Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

We need a consistent file naming scheme #17

Open
kosloot opened this issue Jun 5, 2018 · 2 comments
Open

We need a consistent file naming scheme #17

kosloot opened this issue Jun 5, 2018 · 2 comments
Assignees

Comments

@kosloot
Copy link
Collaborator

kosloot commented Jun 5, 2018

A lot of modules (including those from foliautils assume certain file extensions for input, or create output with a predefined extension.

This is good to prevent modules from reading the wrong files. But is also very rigid.
And at the moment there are some inconsistencies. Which influences PICCL too.

So we need to overhaul this scheme once and for all (hopefully).

@kosloot
Copy link
Collaborator Author

kosloot commented Jun 5, 2018

This is closely related to:
https://github.com/LanguageMachines/foliautils/issues#23

An example is TICCL-chain, which makes files with the extension .chained but we want this as an input for FoLiA-correct, which demand an extension '.ranked'

@kosloot
Copy link
Collaborator Author

kosloot commented Jul 12, 2018

Merging in #27:
It would be desirable if all modules are capable of handling a (one?) filename prefix (including a PATH) and add their own suffixes on output.
Also the usage() and man pages should be clear about this.

This might (should?) also involve some FoLiA utils and the pipeline(s)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants