nvi fails to when encountering 0xa9 character

Kevin Oberman rkoberman at gmail.com
Fri Jan 17 19:44:22 UTC 2014


Thanks, everyone! I feel rather silly now, as I thought I had locality
stuff defined on the account. A quick check shows I was wrong. Guess it was
my old laptop that I replaced over two years ago. :-(

I really need to get a better grasp of all of the LC environmental
variables. Being a native U.S. English speaker, I'm rather spoiled.


On Fri, Jan 17, 2014 at 8:30 AM, Zhihao Yuan <zy at miator.net> wrote:

> On Fri, Jan 17, 2014 at 10:55 AM, David Demelier
> <demelier.david at gmail.com> wrote:
> > Unfortunately nvi is really not unicode capable AFAIK. You probably want
> > to switch to vim or another editor.
>
> The current nvi does has some issue with handling Unicode width,
> and problem Unicode composite chars, but it does support
> multichar encodings, including UTF-8.
>
> --
> Zhihao Yuan, ID lichray
> The best way to predict the future is to invent it.
> ___________________________________________________
> 4BSD -- http://4bsd.biz/
> _______________________________________________
> freebsd-stable at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org"
>



-- 
R. Kevin Oberman, Network Engineer, Retired
E-mail: rkoberman at gmail.com


More information about the freebsd-stable mailing list