ENIG alternatives and similar packages
Based on the "Natural Language Processing" category.
Alternatively, view ENIG alternatives based on common mentions on social networks and blogs.
-
minimorph
English spelling functions with an emphasis on simplicity. Originally by https://github.com/kowey. -
sentiwordnet-parser
Parser for the [SentiWordNet](http://sentiwordnet.isti.cnr.it/) tab-separated file
CodeRabbit: AI Code Reviews for Developers
Do you think we are missing an alternative of ENIG or a related project?
README
ENIG
ENIG is an acronym of typical Korean particles "Eun Neun I Ga (은는이가)". Korean postposition particles change their form depending on the pronunciation of the previous consonant. However, in trouble, because figuring out the previous consonant is not an easy problem. Therefore, most of the programmers who handle Korean treat Korean by starting with "SOMETHING은(는) ~~". This seems to be awkward in a sentence like "SOMETHING is(are), Two apple(s)."
ENIG focuses on programmers to handle Korean strings.
How to use
Core functions
enigPPP
You can get a proper Korean particle by giving enigPPP post word and a Korean postposition particle category.
Handy functions
You can use ENIG without any integration on your code by enigAuto.
When you give a text like "과자이(가) 두개입니다." to enigAuto like enigAuto "과자이(가) 두개입니다.", the function returns "과자가 두개입니다."
Long-range Plans
Korean
- Managing Korean string which involves Korean particle.
English
- Managing English string which involves plural/singular form.
Known Issues
When you get an error like invalid argument or invalid character
When you get a message like invalid argument or invalid character during the library test, check the language configuration of your shell.
This error does not mean a program bug.
Because of this library handling Hangul itself, the test code should contain Korean characters encoded by UTF-8. However, when your shell's language configuration is not set to Unicode(UTF-8), the compiler assumes the code's encoding as the system's default language setting. This behavior leads the compiler fails to read the code and put the error message like above.
Therefore, you should set your shell's encoding by chcp 65001 for Windows or export LC_ALL=en_US.UTF-8 for *nix platforms before testing the library.