| 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 |
Re: not all is lost but far too much for far too long By: Maurice Kinal to Rob Swindell on Thu Jul 04 2019 02:50 am > Hey Rob! > > RS> Well mannered implementations should gracefully handle this > RS> situation > > Do you mean like the 'ignoring' of 0x8d as opposed to deleting it? I think that's a completely different issue. > Anyhow > for my part it really doesn't matter as there is no consequences for > 'ignoring' ftsc standards with utf-8. With or without it is still utf8 ... > unless of course there are any 0x8d trailing bytes which will the be > stripped and then the kludge will be wrong. I agree: tossers probably should not be stripping 0x8d's. I don't think that has anything to do with "CHRS: UTF-8 2" vs "CHRS: UTF-8 4". --- SBBSecho 3.07-Linux* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705) SEEN-BY: 103/705 154/10 203/0 218/700 221/0 1 360 229/426 240/5832 280/464 SEEN-BY: 280/5003 5006 5555 292/854 310/31 320/219 396/45 423/120 633/0 267 SEEN-BY: 633/280 281 412 509 640/1321 1384 712/848 770/1 2452/250 5020/545 @PATH: 103/705 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™.