homepage: https://github.com/QuietJoon/ENIG#readme
changelog-type: markdown
hash: 2a2884e40a2bf37ddf2a301377ebcfd6d88e7590542b3a56acdd0d80c8dd448f
test-bench-deps:
  test-framework-hunit: -any
  test-framework: -any
  base: -any
  unicode-transforms: -any
  text: -any
  test-framework-quickcheck2: -any
  HUnit: -any
  test-framework-th: -any
  ENIG: -any
  QuickCheck: -any
maintainer: developer+ENIG@quietjoon.net
synopsis: Auto Korean conjugator/adjustor/adopter/converter
changelog: |
  # Changelog for ENIG

  ## [Unreleased]

  ## [0.0.0.1] -- 2018-06-20

  ### Changed
  * Use `unicode-transforms` instead of `text-icu`

  ### Added
  * Reimplement ENIG with features 2016 and 2018 only
    * Reimplementing features 2017 is postponed
  * Implement handy functions
basic-deps:
  base: ! '>=4.7 && <5'
  unicode-transforms: -any
  text: -any
  vector: -any
all-versions:
- 0.0.0.2
author: YongJoon Joe
latest: 0.0.0.2
description-type: markdown
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.
license-name: BSD-3-Clause

Update from Hackage at 2019-03-16T14:10:38Z
Update from Hackage at 2019-03-16T14:10:38Z
