ENIG: Auto Korean conjugator/adjustor/adopter/converter

[ bsd3, library, natural-language-processing ] [ Propose Tags ]

Please see the README on GitHub at https://github.com/QuietJoon/ENIG#readme


[Skip to Readme]
Versions [faq] 0.0.0.2
Change log ChangeLog.md
Dependencies base (>=4.7 && <5), text, unicode-transforms, vector [details]
License BSD-3-Clause
Copyright 2016-2019 YongJoon Joe
Author YongJoon Joe
Maintainer developer+ENIG@quietjoon.net
Category Natural Language Processing
Home page https://github.com/QuietJoon/ENIG#readme
Bug tracker https://github.com/QuietJoon/ENIG/issues
Source repo head: git clone https://github.com/QuietJoon/ENIG
Uploaded by yongjoon at Sat Mar 16 14:05:58 UTC 2019
Distributions NixOS:0.0.0.2
Downloads 41 total (22 in the last 30 days)
Rating (no votes yet) [estimated by rule of succession]
Your Rating
  • λ
  • λ
  • λ
Status Hackage Matrix CI
Docs uploaded by user
Build status unknown [no reports yet]

Modules

[Index] [Quick Jump]

Downloads

Maintainer's Corner

For package maintainers and hackage trustees


Readme for ENIG-0.0.0.2

[back to package description]

ENIG

ENIG is an acronym of typical Korean particles "Eun Neun I Ga (은는이가)". Korean postposition particles change their form depending on the pronounciation 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.

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 error like invalid argument or invalid character

When you get a message during test the library like invalid argument or invalid character, check your language configuration.

This is not program error.

Because of this library handling Hangul itself, the test code should contains Korean characters. Therefore, You should set your shell's encoding by chcp 65001 for Windows or export LC_ALL=en_US.UTF-8 for *nix platforms.