[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: nvi i18n
thank you for spotting these quite big issues. I will transmit them to
Sven (who is the maintainer of nvi). My usage pattern is too
restricted: at most I will use UTF-8 files with latin1 and latin2
I will investigate the seriousness of these issues, too.
What was the state of nvi-m17n with respect to this? Do you think we
could get some inspiration from it?
yamt%mwd.biglobe.ne.jp@localhost (YAMAMOTO Takashi) writes:
> nozaki-san and i had a look at src/dist/nvi.
> - it seems to assume 24-bit wchar_t. (ie. <= 0xffffff)
> it won't work with some of our locales like ja_JP.ISO2022-JP and
> zh_CN.GB18030 which use the whole 32-bit.
> - cursor position sometimes get incorrect when using japanese characters.
> it's likely a wcurses problem than nvi itself because, according to
> nozaki-san, it works fine with ncurses.
> - it seems to expect users to know raw wchar_t values for <control-X>.
> it isn't desirable as our wchar_t is an opaque type.
> YAMAMOTO Takashi
Main Index |
Thread Index |