From: dski@ms17.hinet.net () Newsgroups: alt.folklore.computers Subject: The Evils of ASCII Date: 29 Dec 1999 12:52:19 GMT Organization: DCI HiNet Lines: 11 Message-ID: <84d063$euo@netnews.hinet.net> NNTP-Posting-Host: ms17.hinet.net NNTP-Posting-User: dski X-Newsreader: TIN [version 1.2 PL2] Path: chonsp.franklin.ch!pfaff.ethz.ch!news-zh.switch.ch!newsfeed-zh.ip-plus.net!news.ip-plus.net!News.Amsterdam.UnisourceCS!skynet.be!newsfeed00.sul.t-online.de!newsfeed01.btx.dtag.de!t-online.de!newsfeed.tli.de!howland.erols.net!spring.edu.tw!netnews.hinet.net!ms17!dski Never having heard anything of the sort before, and wondering if this thesis is a remnant of a bygone age, I offer for your consideration: http://www.cuenet.com/archive/wordstar/1999/99-12/msg00675.html http://www.cuenet.com/archive/wordstar/1999/99-12/msg00677.html http://www.cuenet.com/archive/wordstar/1999/99-12/msg00683.html http://www.cuenet.com/archive/wordstar/1999/99-12/msg00684.html The messages linked to above were inspired by: http://www.cuenet.com/archive/wordstar/1999/99-12/msg00644.html Dan Strychalski dski at em ess (mail server!) 17 dot hinet dot net ###### From: jsavard@domain.ctry (John Savard) Newsgroups: alt.folklore.computers Subject: Re: The Evils of ASCII Date: Thu, 30 Dec 1999 11:32:58 GMT Organization: PowerSurfr - High Speed Internet Lines: 36 Message-ID: <386b40ee.2418357@news.prosurfr.com> References: <84d063$euo@netnews.hinet.net> <386b58d2.1722257@news.ecn.ab.ca> <84frvr$jos$1@nntp1.u.washington.edu> NNTP-Posting-Host: c9169-003.v-wave.com X-Trace: burn.ab.videon.ca 946578671 10288 24.108.21.103 (30 Dec 1999 18:31:11 GMT) X-Complaints-To: abuse@powersurfr.com NNTP-Posting-Date: 30 Dec 1999 18:31:11 GMT X-Newsreader: Forte Free Agent 1.11/32.235 Path: chonsp.franklin.ch!pfaff.ethz.ch!news-zh.switch.ch!newsfeed-zh.ip-plus.net!news.ip-plus.net!News.Amsterdam.UnisourceCS!skynet.be!cyclone.bc.net!rover.ucs.ualberta.ca!news.ab.videon.ca!not-for-mail dpeschel@u.washington.edu (Derek Peschel) wrote, in part: >In article <386b58d2.1722257@news.ecn.ab.ca>, >John Savard wrote: >>(In any case, there _is_ "ASCII over AMTOR", so one can represent >>ASCII by a 5-level code if one needs to.) >Damn it, now I'm thinking about UNICODE over UTF-8 over ASCII over AMTOR, >and it's your fault. >I've been trying to figure out how you might work with ASCII using a 5-bit >device (say, a Teletype) rather than just using it on a 5-bit channel. It >would be pretty ugly, I can tell you that. I'm assuming that the "5-bit ASCII" the fellow wanted might look something like this: 1 23456 ABCDEFGHIJKLMNOPQRSTUVWXYZ abcdefghijklmnopqrstuvwxyz !"#$%&'()*+,-./0123456789: [\]^_` ;<=>?@ {|}~ with 26 control codes, and a different shifting scheme from that of 5-level code. Space might be special character 2, but CR and LF would be shifted control codes. As I noted, this wouldn't fit in a 7-bit representation any more; the only way it could is if the punctuation marks were as limited as those of 5-level code (or lower case was omitted). (ASCII over AMTOR only handles the printable ASCII characters, not the control characters, so I don't know if it would handle UTF-8.) John Savard (jsavardecnabca) http://www.ecn.ab.ca/~jsavard/crypto.htm ###### From: jsavard@tenMAPSONeerf.edmonton.ab.ca (John Savard) Newsgroups: alt.folklore.computers Subject: Re: The Evils of ASCII Date: Thu, 30 Dec 1999 13:12:27 GMT Organization: Edmonton Community Network Lines: 21 Message-ID: <386b58d2.1722257@news.ecn.ab.ca> References: <84d063$euo@netnews.hinet.net> NNTP-Posting-Host: freenet.edmonton.ab.ca X-Trace: newsfeed.sas.ab.ca 946559810 29933 198.161.206.2 (30 Dec 1999 13:16:50 GMT) X-Complaints-To: news@sas.ab.ca NNTP-Posting-Date: 30 Dec 1999 13:16:50 GMT X-Newsreader: Forte Free Agent 1.1/16.230 Path: chonsp.franklin.ch!pfaff.ethz.ch!news-zh.switch.ch!newsfeed-zh.ip-plus.net!news.ip-plus.net!news.datacomm.ch!newscore.gigabell.net!newsfeeds.belnet.be!news.belnet.be!newsfeed.direct.ca!cyclone.bc.net!rover.ucs.ualberta.ca!sas.ab.ca!ecn.ab.ca!198.161.206.170 On 29 Dec 1999 12:52:19 GMT, dski@ms17.hinet.net () wrote: >Never having heard anything of the sort before, and wondering if this >thesis is a remnant of a bygone age, I offer for your consideration: > http://www.cuenet.com/archive/wordstar/1999/99-12/msg00675.html Although I can find some faults with ASCII, for example the fact that 0123456789ABCDEF is not a sequence of contiguous characters, the idea that designing ASCII as a 7-bit code, instead of a 7-bit representation of a 5-bit code, is somehow a failure or a waste of computer resources strikes me as rather bizarre. Doing that would waste enough character positions that giving ASCII both lower case and a decent repertoire of punctuation symbols would require 8 bits rather than 7. (In any case, there _is_ "ASCII over AMTOR", so one can represent ASCII by a 5-level code if one needs to.) John Savard (teneerf <-) http://www.ecn.ab.ca/~jsavard/index.html ###### From: dpeschel@u.washington.edu (Derek Peschel) Newsgroups: alt.folklore.computers Subject: Re: The Evils of ASCII Date: 30 Dec 1999 14:59:07 GMT Organization: University of Washington, Seattle Lines: 15 Message-ID: <84frvr$jos$1@nntp1.u.washington.edu> References: <84d063$euo@netnews.hinet.net> <386b58d2.1722257@news.ecn.ab.ca> NNTP-Posting-Host: saul9.u.washington.edu X-Trace: nntp1.u.washington.edu 946565947 20252 (None) 140.142.17.35 X-Complaints-To: help@cac.washington.edu NNTP-Posting-User: dpeschel Path: chonsp.franklin.ch!pfaff.ethz.ch!news-zh.switch.ch!news-ge.switch.ch!enews.sgi.com!nntp.primenet.com!nntp.gctr.net!newsfeed.direct.ca!news.u.washington.edu!dpeschel In article <386b58d2.1722257@news.ecn.ab.ca>, John Savard wrote: >(In any case, there _is_ "ASCII over AMTOR", so one can represent >ASCII by a 5-level code if one needs to.) Damn it, now I'm thinking about UNICODE over UTF-8 over ASCII over AMTOR, and it's your fault. I've been trying to figure out how you might work with ASCII using a 5-bit device (say, a Teletype) rather than just using it on a 5-bit channel. It would be pretty ugly, I can tell you that. -- Derek ###### Sender: eric@ruckus.brouhaha.com From: Eric Smith Newsgroups: alt.folklore.computers Subject: Re: The Evils of ASCII References: <84d063$euo@netnews.hinet.net> <386b58d2.1722257@news.ecn.ab.ca> <84frvr$jos$1@nntp1.u.washington.edu> X-Disclaimer: Everything I write is false. Organization: Eric Conspiracy Secret Labs X-Eric-Conspiracy: There is no conspiracy. Date: 05 Jan 2000 16:06:54 -0800 Message-ID: Lines: 16 X-Newsreader: Gnus v5.5/Emacs 20.3 NNTP-Posting-Host: ruckus.brouhaha.com X-Trace: 5 Jan 2000 16:43:25 -0800, ruckus.brouhaha.com Path: chonsp.franklin.ch!pfaff.ethz.ch!news-zh.switch.ch!news-ge.switch.ch!enews.sgi.com!news.sgi.com!news.spies.com!ruckus.brouhaha.com Xref: chonsp.franklin.ch alt.folklore.computers:47496 dpeschel@u.washington.edu (Derek Peschel) writes: > I've been trying to figure out how you might work with ASCII using a 5-bit > device (say, a Teletype) rather than just using it on a 5-bit channel. It > would be pretty ugly, I can tell you that. In my youth a friend asked me to write a driver for his model 28 Teletype (an RO, if memory serves). He was using a TLB computer, a 6502-based system developed by Tommy L. Billings, running the Apex operating system. I wrote a driver in 6502 assembly code that would buffer one line of text. If the characters all mapped to 5-level directly, it would print the line in the normal and obvious fashion. Otherwise it would print overstrikes by making two passes over the same line (since there wasn't a backspace). This worked great for output; it never occurred to us to use the same scheme for input, but I don't see any reason why it wouldn't work. ###### From: dpeschel@u.washington.edu (Derek Peschel) Newsgroups: alt.folklore.computers Subject: Re: The Evils of ASCII Date: 6 Jan 2000 01:21:54 GMT Organization: University of Washington, Seattle Lines: 36 Message-ID: <850qni$dcs$1@nntp1.u.washington.edu> References: <84d063$euo@netnews.hinet.net> <386b58d2.1722257@news.ecn.ab.ca> <84frvr$jos$1@nntp1.u.washington.edu> NNTP-Posting-Host: saul4.u.washington.edu X-Trace: nntp1.u.washington.edu 947121714 13724 (None) 140.142.17.38 X-Complaints-To: help@cac.washington.edu NNTP-Posting-User: dpeschel Path: chonsp.franklin.ch!pfaff.ethz.ch!news-zh.switch.ch!news-ge.switch.ch!news.maxwell.syr.edu!logbridge.uoregon.edu!news.nero.net!news.uidaho.edu!sea-feed.news.verio.net!news.u.washington.edu!dpeschel Xref: chonsp.franklin.ch alt.folklore.computers:47487 In article , Eric Smith wrote: >dpeschel@u.washington.edu (Derek Peschel) writes: >> I've been trying to figure out how you might work with ASCII using a 5-bit >> device (say, a Teletype) rather than just using it on a 5-bit channel. It >> would be pretty ugly, I can tell you that. > >In my youth a friend asked me to write a driver for his model 28 Teletype >(an RO, if memory serves). He was using a TLB computer, a 6502-based system >developed by Tommy L. Billings, running the Apex operating system. > >I wrote a driver in 6502 assembly code that would buffer one line of text. >If the characters all mapped to 5-level directly, it would print the line >in the normal and obvious fashion. Otherwise it would print overstrikes by >making two passes over the same line (since there wasn't a backspace). OK, that's more or less what I was thinking of. I probably should have been less vague. The ugly part arises if you want to create translations for as many ASCII characters as possible. For example, there are four sets of brackets ( ) < > [ ] { } and a bunch of other punctuation marks that don't exist in any of the 5-bit character sets. (I'm being vague because I don't have a reference on hand, so I don't know what _does_ exist.) >This worked great for output; it never occurred to us to use the same scheme >for input, but I don't see any reason why it wouldn't work. Again, I was setting high standards. What if you want to input control characters? What about (gasp) lowercase? You only have overstriking, figures/letters, and maybe one or two punctuation characters to work with. (Isn't there an unused character? That would be good.) It would require intense concentration. -- Derek ###### Sender: eric@ruckus.brouhaha.com From: Eric Smith Newsgroups: alt.folklore.computers Subject: Re: The Evils of ASCII References: <84d063$euo@netnews.hinet.net> <386b58d2.1722257@news.ecn.ab.ca> <84frvr$jos$1@nntp1.u.washington.edu> <850qni$dcs$1@nntp1.u.washington.edu> X-Disclaimer: Everything I write is false. Organization: Eric Conspiracy Secret Labs X-Eric-Conspiracy: There is no conspiracy. Date: 11 Jan 2000 16:57:21 -0800 Message-ID: Lines: 13 X-Newsreader: Gnus v5.5/Emacs 20.3 NNTP-Posting-Host: ruckus.brouhaha.com X-Trace: 11 Jan 2000 17:36:17 -0800, ruckus.brouhaha.com Path: chonsp.franklin.ch!pfaff.ethz.ch!news-zh.switch.ch!news-ge.switch.ch!isdnet!newsfeed.cwix.com!news-peer.gip.net!news.gsl.net!gip.net!enews.sgi.com!news.sgi.com!news.spies.com!ruckus.brouhaha.com Xref: chonsp.franklin.ch alt.folklore.computers:47865 I wrote: > This worked great for output; it never occurred to us to use the same scheme > for input, but I don't see any reason why it wouldn't work. dpeschel@u.washington.edu (Derek Peschel) writes: > Again, I was setting high standards. What if you want to input control > characters? What about (gasp) lowercase? You only have overstriking, > figures/letters, and maybe one or two punctuation characters to work with. > (Isn't there an unused character? That would be good.) It would require > intense concentration. I'd have written the input side if it would have been useful. But on the Teletype model 28 RO, input would have been way to slow to be practical.