> I can add more tests.
Thanks. > However I'm not very clear about those `dbcs_` > functions. They are incomplete and seem to be used when 'encoding' is > not utf-8. (I've tested that it works with 'fileencoding' set to gbk > even the comments above `#define DBCS_` mention 'fileencoding'.) These double-byte encodings all have characters that exist in the Unicode space, since they can be converted to Unicode and back. Thus it's just a matter of finding a way to know which Unicode character is used in which DBCS encoding. > If so, is it OK for this to work only in UTF-8 mode? There are a lot > of issues with UI or plugins when 'encoding' is not utf-8 anyway. I know quite a few users in Asia still use DBCS encodings, for various reasons. Thus it would be really nice if we can make this work. But we could do it in two steps, first implement it for Unicode, and then someone knowledgeable of a specific DBCS encoding in a followup CL. For now, we can make those dbcs functions a no-op. -- Why is "abbreviation" such a long word? /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org /// -- -- 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/d/optout.
