On 31/05/2013 11:23, Ron Aaron wrote:
I think there should be an option (probably an option, not a regex flag) which controls whether or
not the engine finds "ff" (unicode 0xfb00) when searching for "f", for example.
It seems to me that most people may not need it, but those of us who frequently edit multilingual
or other rich texts, encounter the need quite often.
Searching (in the above example) for "ff" should only find "ff", but searching for
"f" should also find it (if the option were enabled).
"ff" is a ligature, not a composed character. Although it has a
decomposed form it cannot be recomposed with Unicode composing rules (f
is not a composing character) There are others including "ffi" - should a
search for "fi" match the second and third characters?
The question is do you want a search on the unicode codepoints (e.g. a
search on "ffi") or do you want a search on the semantic Unicode character
sequence (i.e. "ffi")?
As long as I'm on a roll, I'll also reiterate my request from long ago that in addition to the "\Z"
regex flag, there be an option (which is what I originally added, but you {Bram} didn't like and replaced
with the \Z). I would call it "ignorecombining", to parallel "ignorecase".
To be orthogonal, the option listed above could be "ignoreprecomposed", maybe
"\Y" regex option (for the sake of orthogonality).
Wouldn't this be "ignoreligatures" for the case above? In addition to
any "ignoreprecomposed".
TTFN
Mike
--
Some push the envelope to the edge. Others just lick it!
--
--
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].
For more options, visit https://groups.google.com/groups/opt_out.
