Re: tr not respecting UTF-8 locale ?

[Paul Eggert]

Michał Kosmulski <address@hidden> writes:

> I am using a UTF-8 locale and all coreutils except for tr seem to
> agree on that. However, tr behaves differently and seems to always
> assume that 1 byte == 1 character even in a UTF-8 locale.

Most coreutils utilities do not support UTF-8 in general, and
tr is no exception.

POSIX does not require support for multibyte locales, so this is not a
standards-conformance issue, though of course it is a problem.

Personally, I don't even understand what tr is _supposed_ to do with
UTF-8 in general.  For example, I don't really understand the
difference between "tr -c" and "tr -C" as specified by POSIX.