On 21/04/2026 07:12, Collin Funk wrote:
Hi Pádraig,Was looking at stuff to do post release, and saw that your page listed 'comm' as needing i18n work [1]. As far as I can see there are no issues with it. Here is a simple test case to demonstrate: $ echo 'é' > file1; echo 'f' > file2; $ LC_ALL=en_US.UTF-8 comm file1 file2 é f $ LC_ALL=C comm file1 file2 f é It looks like it has been correct for a long time as well [2]. The --output-delimiter option just takes whatever bytes it is given, so nothing needs to be done there either. It looks like it could use some tests for this, though. I'll have a look at adding some tomorrow. Collin [1] https://www.pixelbeat.org/docs/coreutils_i18n/ [2] https://github.com/coreutils/coreutils/commit/3ad83e6ad0f4cc930b04b111af23c320c070b2f3
I've removed it from the page. thanks, Padraig
