| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | pesky moose and squirrel |
Hallo Paul! PQ> Does this make any sense to you? Sort of. However in this case the most important is the retention of the trailing 0x8d byte. Once that has been stripped then none of the four multibyte characters are multibyte anymore and only the four leading bytes remain. PQ> I can produce *.png happy snaps of these screens on demand, if PQ> it'll help. I suppose it is possible help but again, in this case, there are only four bytes that *need* to be there in order for it to be a true utf8 message. They can be readily searched for in a text file. In fact for a regular 8-bit codepage the 0x8d character will also get deleted. This is not unique to utf8. Het leven is goed, Maurice ... Huil niet om mij, ik heb vi. --- 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: 103/705 154/10 203/0 221/0 1 360 229/426 240/5832 280/464 5003 5006 SEEN-BY: 280/5555 292/854 310/31 320/219 396/45 423/120 633/0 267 280 281 412 SEEN-BY: 633/509 640/1321 1384 712/848 770/1 2452/250 5020/545 @PATH: 280/464 221/1 640/1384 633/280 267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.