Hi Xianwen Chen, Xianwen Chen wrote on Sun, Feb 11, 2018 at 08:50:20AM +0000:
> Would you agree that a good startig point would be to look at how > your implemented UTF-8 support in ksh(1)? Probably, that's one of the pieces of information you need. I'm not sure it will be sufficient, though; i did not look at the csh(1) codebase, and it may differ and pose other challenges. In any case, make sure you study https://www.openbsd.org/papers/eurobsdcon2016-utf8.pdf https://www.openbsd.org/papers/eurobsdcon2016-utf8.roff carefully. > I tried to find your commit It was more than one commit. > on GitHub, which implement UTF-8 support in ksh(1). > I could not find it. I'm not surprised. Github is simply unusable. It is an extremely hostile user interface. Use $ cd /usr/src/bin/ksh/ $ cvs log -wschwarze | less /schwarze Some examples of relevant revisions include: emacs.c 1.61 2015/12/10 10:00:14 1.64 2016/01/08 13:17:57 1.67 2017/05/12 14:37:52 vi.c 1.40 2016/10/11 19:52:54 1.41 2016/10/17 17:19:08 1.42 2016/10/17 17:44:47 1.47 2017/05/31 20:18:43 main.c 1.81 2016/10/11 19:52:54 1.82 2016/10/17 17:44:47 You can also use the command-line git(1) program if you understand the bloated user interface, but simply using cvs(1) is almost certainly easier. The above list may not be complete, and others may also have contributed, but most related changes are likely in emacs.c and vi.c. > Was the change commited to a file in src/bin/ksh/? Yes, the related changes are in that directory. Have fun, Ingo
