Date: Sun, 3 Nov 2019 12:25:30 +0100 From: Per Hedeland <per@hedeland.org> To: Robert Huff <roberthuff@rcn.com> Cc: "Ronald F. Guilmette" <rfg@tristatelogic.com>, freebsd-questions@freebsd.org Subject: Re: sort is broken Message-ID: <425ec8a5-8694-c487-eb88-2c7c4954ab45@hedeland.org> In-Reply-To: <23998.18328.317629.206400@jerusalem.litteratus.org> References: <8847.1572745058@segfault.tristatelogic.com> <f416a932-7084-bec3-8a7a-8efaaebc2952@hedeland.org> <23998.18328.317629.206400@jerusalem.litteratus.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2019-11-03 04:20, Robert Huff wrote: > > So ... I ran "iconv -l" and saw among the known encodings: > > UNICODE-1-1-UTF-7 UTF-7 CSUNICODE11UTF7 > > Is that an valid encoding? It looks like a couple of separate > entries got mushed together on the same line. There's a lot of strange stuff in the output of "iconv -l":-) - I'm not sure there even exists a concept of "validity" for those things. But in this particular case, https://www.iana.org/assignments/character-sets/character-sets.xhtml lists csUnicode11UTF7 as an alias for UNICODE-1-1-UTF-7 - and iconv(1) says: [...] the names are printed in upper case, separated by whitespace, and alias names of an encoding are listed on the same line as the encoding itself. --Per
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?425ec8a5-8694-c487-eb88-2c7c4954ab45>