On Sun, Aug 11, 2013 at 1:35 AM, Alexey Dokuchaev <da...@freebsd.org> wrote: > On Sat, Aug 10, 2013 at 10:33:20AM -0700, Peter Wemm wrote: >> I've been tinkering with the nvi refresh from the GSoC in 2011, aka nvi2. >> >> https://www.google-melange.com/gsoc/proposal/review/google/gsoc2011/zy/1 >> https://github.com/lichray/nvi2 >> >> The goal was to update the multibyte handling in nvi-1.79 (the one we >> have in our tree) in such a way we could import it. > > Yes, please do something about our base(1) being unable to talk in anything > non-ASCII. I'm using editors/nvi-devel now, which was WIDECHAR option, and > was wondering why those changes were never imported into the base. > > How is nvi 1.81.6 (per editors/nvi-devel) is different from nvi2, btw?
The original reason was that nvi-devel switched from the db-1.x API to db-3/db-4 which were sleepycat licensed, and are now Oracle. It was a big chunk of code at the time. eg: USE_BDB= 42+ CONFIGURE_ARGS+= --with-db-prefix=${LOCALBASE} nvi2 is nvi-1.79 from base with a serious cleanup pass. The iconv/multibyte code will look quite familiar if you've looked at the nvi-devel code, along with a cherry-picking of additions from nvi-m17n for better CJK/non-utf8 support. nvi2 does not have the same level of sophisticated encoding detection that nvi-m17n has. -- Peter Wemm - pe...@wemm.org; pe...@freebsd.org; pe...@yahoo-inc.com; KI6FJV UTF-8: for when a ' just won\342\200\231t do. <brueffer> ZFS must be the bacon of file systems. "everything's better with ZFS" _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"