REPLY: 1:229/452 3A6C1B5A
MSGID: 2:280/464.113 5cc47081
Hallo Nancy!
NB> Except that some thing or things took exception to it....
I think I now know why. If I am right it has to do with MS codepages, and in
the case of 0x8d, specifically CP1252 which has a 'hole' at that code. On my
system using 'iconv' this is what happens when feeding it 0x8d;
-={ ':read !echo -e "\x8d" | iconv -t cp1252' starts }=-
iconv: illegal input sequence at position 0
-={ ':read !echo -e "\x8d" | iconv -t cp1252' ends }=-
Not a good sign. Given that 0x8d is a valid trailing byte in utf8, which
range from 0x80-0xbf, makes the above issue far worse than just a single
character.
To demonstrate the above I made up a new table with just the IBM and MS
codepages which show the holes in MS codepages that will impact messaging
conversions both 8 bit and utt8.
==========================================================================
8bit CP437 IBM848 CP850 CP852 CP866 CP1250 CP1251 CP1252
==========================================================================
80 c387 d090 c387 c387 d090 e282ac d082 e282ac
81 c3bc d091 c3bc c3bc d091 d083
82 c3a9 d092 c3a9 c3a9 d092 e2809a e2809a e2809a
83 c3a2 d093 c3a2 c3a2 d093 d193 c692
84 c3a4 d094 c3a4 c3a4 d094 e2809e e2809e e2809e
85 c3a0 d095 c3a0 c5af d095 e280a6 e280a6 e280a6
86 c3a5 d096 c3a5 c487 d096 e280a0 e280a0 e280a0
87 c3a7 d097 c3a7 c3a7 d097 e280a1 e280a1 e280a1
88 c3aa d098 c3aa c582 d098 e282ac cb86
89 c3ab d099 c3ab c3ab d099 e280b0 e280b0 e280b0
8a c3a8 d09a c3a8 c590 d09a c5a0 d089 c5a0
8b c3af d09b c3af c591 d09b e280b9 e280b9 e280b9
8c c3ae d09c c3ae c3ae d09c c59a d08a c592
8d c3ac d09d c3ac c5b9 d09d c5a4 d08c
8e c384 d09e c384 c384 d09e c5bd d08b c5bd
8f c385 d09f c385 c486 d09f c5b9 d08f
==========================================================================
8bit CP437 IBM848 CP850 CP852 CP866 CP1250 CP1251 CP1252
==========================================================================
90 c389 d0a0 c389 c389 d0a0 d192
91 c3a6 d0a1 c3a6 c4b9 d0a1 e28098 e28098 e28098
92 c386 d0a2 c386 c4ba d0a2 e28099 e28099 e28099
93 c3b4 d0a3 c3b4 c3b4 d0a3 e2809c e2809c e2809c
94 c3b6 d0a4 c3b6 c3b6 d0a4 e2809d e2809d e2809d
95 c3b2 d0a5 c3b2 c4bd d0a5 e280a2 e280a2 e280a2
96 c3bb d0a6 c3bb c4be d0a6 e28093 e28093 e28093
97 c3b9 d0a7 c3b9 c59a d0a7 e28094 e28094 e28094
98 c3bf d0a8 c3bf c59b d0a8 cb9c
99 c396 d0a9 c396 c396 d0a9 e284a2 e284a2 e284a2
9a c39c d0aa c39c c39c d0aa c5a1 d199 c5a1
9b c2a2 d0ab c3b8 c5a4 d0ab e280ba e280ba e280ba
9c c2a3 d0ac c2a3 c5a5 d0ac c59b d19a c593
9d c2a5 d0ad c398 c581 d0ad c5a5 d19c
9e e282a7 d0ae c397 c397 d0ae c5be d19b c5be
9f c692 d0af c692 c48d d0af c5ba d19f c5b8
==========================================================================
Note 0x81, 0x83, 0x88, 0x8d, 0x8f, 0x90, 0x98, and 0x9d. These are all valid
trailing bytes in utf8. Also worthy of noting is that none of the IBM
codepages are affected, especially CP437 which is what you are using. However
any Windows based BBS you are recieving offline packets from may definetly
have an impact on the characters noted with holes, such as the 'i' created by
0x8d in CP437.
Bottomline for me is that I'm happy to say I don't do Windows. :-)
Het leven is goed,
Maurice
... Cybertoasts van belang:
2020-01-01 is 249 dagen vanaf nu en valt op een woensdag.
2024-11-05 is 2019 dagen vanaf nu en valt op een dinsdag.
--- GNU bash, version 5.0.7(1)-release (x86_64-pc-linux-gnu)
* Origin: Little Mikey's EuroPoint - Ladysmith BC, Canada (2:280/464.113)
SEEN-BY: 1/123 15/2 18/200 123/1970 154/10 203/0 221/0 226/17 229/107
SEEN-BY: 229/354 426 452 1014 240/5832 249/206 317 400 280/464 5003
SEEN-BY: 310/31 317/3 322/757 342/200 393/68 396/45 423/120 633/280
SEEN-BY: 770/1
PATH: 280/464 229/426
|
