Hi Bram,

2017/8/1 Tue 23:40:27 UTC+9 Ken Takata wrote:
> Hi Bram,
> 
> 2017/8/1 Tue 5:30:56 UTC+9 Bram Moolenaar wrote:
> > Ken Takata wrote:
> > 
> > > 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.
> > > 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?
> > 
> > I still like to be able to build a tiny Vim with the smallest set of
> > features.  Can be used on rescue systems and embedded systems.
> > It is especially important to have a minimal set of dependencies, e.g.
> > no iconv library.
> 
> Personally I think the difference of size between with/without multibyte
> support is negligible. As per the result by James, it is 838K vs. 978K.
> Moreover, Ubuntu (and some other distributions) uses vim-tiny for an alias
> of vi, however, actually it is vim-tiny with multibyte support.
> 
> But, okay, I agree with you that it is needed for rescue/embedded systems.
> 
> Then, how about setting `enc=utf-8` as the default?

And, I have another proposal.

I propose always enabling FEAT_MBYTE on Windows, because Windows version
can convert encodings without iconv and will rarely used for rescue/embedded
systems.
There are so many `#ifdef FEAT_MBYTE`s in os_win32.c, os_mswin.c and
gui_w32.c.  They exist everywhere calling Unicode APIs.  Enabling multibyte
makes them simpler.

Regards,
Ken Takata

-- 
-- 
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.

Raspunde prin e-mail lui