Improve supported language documentation in README #240
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello!
First, let me say "thanks" for creating lingua. It's outstanding, and very useful!
I'm integrating it into my application. My application uses ISO-639 codes to identify languages, so the first thing I did was to map the names of the supported languages in the README to their respective ISO-639 codes.
Since I needed it, I figured others might, too. This pull request replaces the list of supported languages in the README with a table that includes the language names, plus their respective ISO-639 codes, and any additional commonly-used names. All data comes from the List of ISO 639 language codes page on Wikipedia.
All feedback welcome! Please feel free to reject if you think this isn't useful. Also, I tried to pick reasonable column header names, but there's a lot of room for opinions there, so that's an easy change.