[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: mhfixmsg character set conversion
From: |
Ken Hornstein |
Subject: |
Re: mhfixmsg character set conversion |
Date: |
Fri, 04 Feb 2022 14:00:25 -0500 |
>Looking at the first 8-bit character in the excerpt, E9 in iso8859-1,
>that should have been converted to C3A9 in UTF-8. iconv correctly does
>that:
>
>$ printf '\xE9' | iconv -f iso-8859-1 -t utf-8 | hexdump -C 00000000 c3
>a9 |..|
>
>Instead, it got converted to C383C2A9. I'm not sure why.
Hm. C3 83 is the UTF-8 for U+00C3. C2 A9 is the UTF-8 for U+00A9. And
the UTF-8 for U+00E9 is C3 A9. Is it possible it was ran through
iconv twice?
--Ken
- Re: In Memoriam: Norman Z. Shapiro 1932-2021, Ken Hornstein, 2022/02/01
- Re: In Memoriam: Norman Z. Shapiro 1932-2021, Jon Steinhart, 2022/02/01
- mhfixmsg character set conversion, Steven Winikoff, 2022/02/03
- Re: mhfixmsg character set conversion, David Levine, 2022/02/04
- Re: mhfixmsg character set conversion,
Ken Hornstein <=
- Re: mhfixmsg character set conversion, Steven Winikoff, 2022/02/04
- Re: mhfixmsg character set conversion, David Levine, 2022/02/04
- Re: mhfixmsg character set conversion, Steven Winikoff, 2022/02/04
- Re: mhfixmsg character set conversion, Ken Hornstein, 2022/02/04
- Re: mhfixmsg character set conversion, Steven Winikoff, 2022/02/04
- Re: mhfixmsg character set conversion, David Levine, 2022/02/05
- Re: mhfixmsg character set conversion, David Levine, 2022/02/06
- Re: mhfixmsg character set conversion, Steven Winikoff, 2022/02/06
- Re: mhfixmsg character set conversion, David Levine, 2022/02/06
- Re: mhfixmsg character set conversion, Steven Winikoff, 2022/02/07