On Fri, Jan 9, 2015, at 17:48, FRIGN wrote: > Did you read what I said? I explicitly went away from POSIX in this > regard, > because no human would write ""tr '\303\266o' 'o\303\266'".
POSIX doesn't require people to write it, it just requires that it works. POSIX has no problem with also allowing a literally typed multibyte character to refer to itself. It's basically saying that if someone _does_ write '\303\266o' 'o\303\266', you have to treat it the same as öo oö, and not as the individual bytes. > The reason why POSIX prohibits collating elements is only because they > are > inhibited by their own overload of different character sets and locales. > Given assuming a UTF-8-locale is a very sane way to go (see Plan 9), this > limit can easily be thrown off and makes life easier. I don't think you're understanding the difference between multi-character collating elements and multibyte characters. Multi-character collating elements are things like "ch" in some Spanish locales. They have nothing to do with UTF-8.
