Date: Sat, 4 Feb 2023 08:36:02 -0500 From: George Mitchell <george+freebsd@m5p.com> To: stable@freebsd.org Subject: Re: Grep with non-ascii Message-ID: <f57a12c0-1043-e79d-9ecf-2ac00d1d4d04@m5p.com> In-Reply-To: <20230204131637.4e8e66e086eea57f4bb27b12@dec.sakura.ne.jp> References: <20230203110642.70e4a076@elg.hjerdalen.lokalnett> <819a4336-9689-bdbe-a90d-8f1d7b842662@grosbein.net> <20230203151853.02732bd6@elg.hjerdalen.lokalnett> <20230204010605.4874609f80eed28543407807@dec.sakura.ne.jp> <c77ad75b-b8c4-9014-0bc7-f1a0ec78272c@m5p.com> <20230204131637.4e8e66e086eea57f4bb27b12@dec.sakura.ne.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2/3/23 23:16, Tomoaki AOKI wrote: > [...] > And FreeBSD already has UTF-8. ;-) > > Drawbacks of UTF-8 are... > *Han unification. Not exactly same but lookalike characters in > Japanese, Chinese and Korean are fatally missingly unified. > > *Lack of proper support for variant forms of characters. > Maybe Unicode should have another 2 dimensions, one for classifying > wrongly unified CJK characters and another one for variants. I confess that I don't know enough to comment on those. > > *Font sets. Very limited number of fonts covers the whole > Unicode codepoints that are assigned any of actual character. > > *FreeBSD base does not have full Unicode font for vt yet. > (Input methods are the different problem, though.) > Yes, but FreeBSD is making progress on remedying these problems. Many fonts DO have support for the codepoints I need, though. I think these are less of a problem than the problems that UTF-8 solves. -- George
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f57a12c0-1043-e79d-9ecf-2ac00d1d4d04>