| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | not all is lost but far too much for far too long |
Hey Ozz! Just for the record, the message I am replying to -> MSGID: 1:1/123.0 5D164D19 <- never arrived at 1:153/7001 through the normal uplink 1:153/757. However it was recieved via 1:154/10 which I am using as the main link for 1:153/7001.2989. Also it shows up on the Europoint which I use for verification purposes as well. With or without a BOM makes no difference not unlike the CHRS kludge for UTF-8. Also it does nothing to solve the obvious flaw of the 'ignored' 0x8d characters no matter what the encoding is or whether or not the CHRS kludge is deployed. I see no fix proposed in your message. Life is good, Maurice ... Don't cry for me I have vi. --- GNU bash, version 5.0.7(1)-release (aarch64-raspi3b+-linux-gnu)* Origin: Little Mikey's CanadARM - Ladysmith BC, Canada (1:153/7001.2989) SEEN-BY: 153/7001 154/10 30 40 700 203/0 221/1 6 360 227/201 400 229/310 426 SEEN-BY: 280/464 5003 5555 292/854 320/219 340/800 633/0 267 280 281 412 509 SEEN-BY: 640/1321 1384 712/848 3634/12 5020/545 @PATH: 153/7001 154/10 221/6 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™.