Re: [bug-gawk] Exposing wcwidth(3) as a built-in function

[Eric Pruitt]

On Fri, Dec 01, 2017 at 09:41:14PM +0200, Eli Zaretskii wrote:
> Thanks, but doesn't this still assume UTF-8 encoding of characters?
> If so, it's not portable to non-UTF-8 locales, right?

That is correct. By "portable" I meant that it works on the most popular
AWK implementations although I still need to test the script on a BSD
box. I'm not trying to reimplement setlocale or iconv. UTF-8 is easy to
parse, far saner than its predecessors (IMO) and conveniently happens to
be the only encoding other "C" that I use on my machines.

Eric