Hello! Steffen Nurpmeso wrote in <20220513135904.hhnsw%stef...@sdaoden.eu>: |Steffen Nurpmeso wrote in | <20220513132857.xzhqq%stef...@sdaoden.eu>: ||Harald van Dijk wrote in || <9aa0b43f-c5de-1698-9f34-c725a40e6...@gigawatt.nl>: |||On 12/05/2022 23:10, Steffen Nurpmeso wrote: |||> Harald van Dijk wrote in |||> <bd336669-960b-1f5f-fffc-30905d4c8...@gigawatt.nl>: |||>|On 12/05/2022 18:19, Steffen Nurpmeso via austin-group-l at The Open |||>|Group wrote: |||>|> Bruno Haible wrote in |||>|> <4298913.vrqWZg68TM@omega>: | ... |||> LC_ALL=C printf 'ab\0' | iconv -f iso-8859-1 -t utf-16 | od -t c |||> 0000000 \0 \0 a \0 b \0 \0 \0 |||> |||> Two leading NULs? ||| |||This is not what GNU iconv prints at all, at least not on my system, |||which just uses the GNU version unmodified. Rather, it prints || ||Interesting. Unmodified here too. Bruno Haible contacted me in ||private, i gave him all i have. | |Looking at the code (iconvdata/utf-16.c) i admit i fail to see how |this can happen, except maybe due to gcc 11.2.0 miscompilation |(CFLAGS="-O2 -march=x86-64 -pipe", shall that be honoured). The |above is however surely what i see here, reproducably.
Bruno Haible had the fantastic idea of checking od(1), and that was it! When i use hexdump -C the BOM is back. Or the GNU version of od(1). --steffen | |Der Kragenbaer, The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(By Robert Gernhardt)
