Hi Bram, On Wed, Sep 16, 2020 at 12:50 PM Bram Moolenaar <[email protected]> wrote:
> > Yegappan wrote: > > > On Wed, Sep 16, 2020 at 8:56 AM Bram Moolenaar <[email protected]> > wrote: > > > > > > > > > On Wed, Sep 16, 2020 at 3:23 AM Maxim Kim <[email protected]> wrote: > > > > > > > > > =D0=B2=D1=82=D0=BE=D1=80=D0=BD=D0=B8=D0=BA, 15 > =D1=81=D0=B5=D0=BD=D1= > > =82=D1=8F=D0=B1=D1=80=D1=8F 2020 =D0=B3. =D0=B2 22:34:33 UTC+3, bfrg: > > > > > > > > > >> But matchfuzzy() returns only a list of byte indexes (column > > > numbers). > > > > >> > > > > >> Does that mean we wouldn't be able to match unicode (cyrillic for > > > > > example)? > > > > > > > > Currently the matchfuzzy() function does not support multibyte > > > characters. > > > > But it can be extended to support multibyte characters. > > > > > > Would be the first thing that people ask for. > > > Does it already use case folding? > > > > > > > > No. The current code uses vim_tolower() to lower case a letter before > > comparison. If str_foldcase() is used to convert the entire string and > the > > search pattern, will it solve the case-folding problem? > > Note that in some cases changing case also changes the number of bytes, > thus after using foldcase for the whole string the byte positions may > not be correct. > > > I have the changes ready to support fuzzy matching multibyte characters. Can you merge the PR for the mutchfuzzypos() function? I will then create a new PR for this. Thanks, Yegappan -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/CAAW7x7n2%3DFmwg1%3D7BDGbqwxwGc06YovkDA_Hh_pppkBMyBBiCA%40mail.gmail.com.
