It's all fun and games until someone loses an .
looks good here from the console terminal with the new unicode
work that's been done in sbbs :)
How about the 0x8d cp866 character in this reply?looks good here from the console terminal with the new unicode
work that's been done in sbbs :)
ет, это не так. It looks good since the 0x8d cp437 character survived.
@REPLY: 753.fido-asianlin@1:3634/12 218b6a34
@MSGID: 1:153/7001 5d265e82
@CHRS: CP866 2
Hey mark!
looks good here from the console terminal with the new unicode
work that's been done in sbbs :)
ет, это не так. It looks good since the 0x8d cp437 character survived. How about the 0x8d cp866 character in this reply?
Life is good,396/45
Maurice
... Don't cry for me I have vi.
--- GNU bash, version 5.0.7(1)-release (x86_64-pc-linux-gnu)
* Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001) SEEN-BY: 57/0 153/757 7001 154/10 30 40 700 203/0 220/70 221/0 6 227/400 SEEN-BY: 229/426 240/5832 267/800 280/464 5003 310/31 340/800 393/68
SEEN-BY: 423/120 712/848 770/0 1 10 100 330 340 772/0 1 210 500 3634/12 SEEN-BY: 116/116 123/25 150 755 135/300 153/7715 261/38 3634/15 27 50 123/50
SEEN-BY: 123/115 3634/0 18/0 123/0 1/120
@PATH: 153/7001 757 770/1 280/464 154/10 3634/12
there's still work being done on sbbs' unicode implementation so
it may be that it doesn't know how to translate those
"CHRS: CP866 2" would be wrong.there's still work being done on sbbs' unicode implementation so
it may be that it doesn't know how to translate those
Last I heard about it the default is to assume cp437 -> utf8 which when
Bottomline is that all the 8-bit characters retained their values
and didn't get deleted.
Sysop: | Ruben Figueroa |
---|---|
Location: | Mesquite, Tx |
Users: | 3 |
Nodes: | 4 (0 / 4) |
Uptime: | 96:31:35 |
Calls: | 79 |
Files: | 53 |
Messages: | 73,865 |