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

Decide on one encoding scheme for language #15

Closed
kosloot opened this issue Oct 11, 2016 · 3 comments
Closed

Decide on one encoding scheme for language #15

kosloot opened this issue Oct 11, 2016 · 3 comments

Comments

@kosloot
Copy link
Collaborator

kosloot commented Oct 11, 2016

To keep everything under control, all FoLiA and FoLiA related tools should use the same encoding for language parameters.
IMNHO only ISO 692-2 is applicable.

Even then some issues like 'nld' versus 'dut' remain.
@proycon @martinreynaert

@kosloot kosloot changed the title Decide on one encoding schem for language Decide on one encoding scheme for language Oct 11, 2016
@proycon
Copy link
Member

proycon commented Oct 11, 2016

Don't use iso-639-2, use iso-639-3 instead then (three letter codes for tons of languages), dutch is nld. Ucto currenctly uses iso-639-1 though (two letter codes, more limited). We can also simply use iso-639-1 for Frog and fall back to iso-639-3 only for the more exotic languages.

@kosloot
Copy link
Collaborator Author

kosloot commented Oct 12, 2016

ok, so ISO 693-3 looks the best choice in the long run.
This means some changes in existing code, an probably some hackery to be backward compatible.
This affects mainly ucto and uctodata, maybe FoLiA-langcat too
The language option in Frog is in development and can be ISO 396-3 from the start.

@kosloot
Copy link
Collaborator Author

kosloot commented Oct 26, 2016

ISO 693-3 it will be.

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