2017-08-01 0:15 GMT+09:00 Tony Mechelynck <[email protected]>:
> On Mon, Jul 31, 2017 at 4:29 PM, Ken Takata <[email protected]> > wrote: > > Hi Bram, > > > > Two years ago, you announced closing of Vim-multibyte mailing list. > > > > Vim-multibyte mailing list is closed > > https://groups.google.com/d/msg/vim_announce/3Kzdhtsp9dQ/afcHmpksN7QJ > > > > In the announcement, you said: > > > >> Multi-byte text is a core part of Vim these days, mainly > >> because UTF-8 is wide spread now. > > > > I strongly agree with this. Nowadays, support for UTF-8 is mandatory for > > text editors. > > Support for GB18030 (a Unicode transformation format) is mandatory in > mainland China. In practice, I suppose that for software publishers > this implies support (in China) for other Unicode encodings such as > UTF-8 and UTF-16. I'm much less sure about Unicode support being > mandatory everywhere _outside_ of China. (France? USA? UK? Jamaica? > Haiti? etc.) > Primarily out of curiosity, yet to remind me of what the original Vi looks like and where we come from, I sometimes run "The Traditional Vi": http://ex-vi.sourceforge.net According to README, it is actually a port of BSD vi 3.7 (I have no idea how old it is, though). Although it doesn't mention whether or not it compiles on macOS, I found it possible with a couple of tweaks in Makefile. The code size is 288536, and remarkably, it supports UTF-8 by default. Yes, I run a port of original Vi on iTerm2 on macOS 10.11.6 and can use multi-byte characters with it just out of the box. > > Thus how about removing the `FEAT_MBYTE` build option on next minor > release > > and make it always available? It can make the code simpler (a bit). > > > > I also think it's better to set `enc=utf-8` as the default on all > platforms > > near the future. (After the next minor release?) > > > > What do you think? > > > > Regards, > > Ken Takata > > And remove the possibility to compile a "lean and mean" vi with Tiny > features, working only in 8-bit encodings such as the various avatars > of ISO 8859 in use in Europe? (At the moment, +multi_byte is already > compiled-in in every build of Vim except Tiny and Small.) > > (Yes, I am pleading devil's advocate in this discussion. I use UTF-8 > myself — mostly. But I also keep an up-to-date Tiny build of Vim under > executable name "vi" and I build it with as few optional features as I > can. Executable sizes: Huge, 2934944 bytes; Tiny, 766992 bytes. Size > ratio: 3.826564 to 1.) > As I wrote somewhere previously, my PC broke due to a memory module failure recently, and the kernel panic caused by that made the hard disk not bootable. When rescuing the files in the hard disk, it was a normal build Vim on Recovery Disk that helped me much. So I personally know well the importance of the "lean and mean" vim. Allowing a build such that it is kept small in size and less dependent on share libraries is a key feature of Vim which gives it the privilege of being linked against /usr/bin/vi. That said, having seen the example of "The Traditional Vi", I feel that the privilege will still be held even if Vim drops non-multibyte builds. > > Best regards, > Tony. > > Best regards, Kazunobu -- > -- > 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. > -- -- 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.
