aboutsummaryrefslogtreecommitdiff
path: root/runtime/lua/vim/_meta/vimfn.lua
diff options
context:
space:
mode:
authordundargoc <gocdundar@gmail.com>2024-06-18 14:01:20 +0200
committerdundargoc <33953936+dundargoc@users.noreply.github.com>2024-08-07 15:31:18 +0200
commit328ea02eb7dec32286ae6c691ecef71d988c905b (patch)
tree7ed364062b329648eff486da8d34cecc95a0f0b8 /runtime/lua/vim/_meta/vimfn.lua
parent11a6f3c9301b3deb71f7e5886fce3718420355be (diff)
downloadrneovim-328ea02eb7dec32286ae6c691ecef71d988c905b.tar.gz
rneovim-328ea02eb7dec32286ae6c691ecef71d988c905b.tar.bz2
rneovim-328ea02eb7dec32286ae6c691ecef71d988c905b.zip
refactor!: use utf8proc full casefolding
According to `CaseFolding-15.1.0.txt`, full casefolding should be preferred over simple casefolding as it's considered to be more correct. Since utf8proc already provides full casefolding it makes sense to switch to it. This will also remove a lot of unnecessary build code. Temporary exceptions are made for two sets characters: - `ß` will still be considered `ß` (instead of `ss`) as using a full casefolding requires interfering with upstream spell files in some form. - `İ` will still be considered `İ` (instead of `i̇`) as using full casefolding requires making a value judgement on the "correct" behavior. There are two, equally valid case-insensetive comparison for this character according to unicode. It is essentially up to the implementor to decide which conversion is correct. For this reason it might make sense to allow users to decide which conversion should be done as an added option to `casemap` in a future PR.
Diffstat (limited to 'runtime/lua/vim/_meta/vimfn.lua')
0 files changed, 0 insertions, 0 deletions