On Thu, Mar 24, 2011 at 5:17 PM, Johan van Selst <joh...@stack.nl> wrote: > Zhihao Yuan wrote: >> 2. nvi does not use iconv, nvi-m17n only supports limited non-Unicode >> mbyte encodings, nvi-devel has too many problems. So we don't have a >> nvi which comes with fully mbyte enconding support; > > Could you please eleborate on the nvi-devel problems? I'm the current > maintainer of this port, and as far as I know it's fully functional. > nvi-devel does have proper UTF-8 support via libiconv. It is based on > the nvi version we currently have in base and much of the code base is > still identical. > > > Johan >
1. It does not support non-Unicode encodings. Actually, these encodings are mainstream in multi-byte encodings world. A proper iconv-awared implementation should be able to handle all of the encodings in `iconv -l`; 2. It depends on DB3/4. We won't accept DB3/4 in base system and we won't accept nvi-devel. 3. It's not 100% compatible with nvi 1.79. -- Zhihao Yuan The best way to predict the future is to invent it. _______________________________________________ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
