Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!spool.mu.edu!munnari.oz.au!manuel!ccadfa!prolix!dac From: dac@prolix.pub.uu.oz.au (Andrew Clayton) Newsgroups: comp.sys.amiga.advocacy Subject: Re: Here's an EASY one for you Message-ID: <18f73ee5.ARN18a5@prolix.pub.uu.oz.au> Date: 10 Apr 91 11:04:37 GMT References: <18f0bf14.ARN1771@prolix.pub.uu.oz.au> <1080@cbmger.UUCP> Reply-To: dac@prolix.pub.uu.oz.au Followup-To: comp.sys.amiga.advocacy Organization: More like Mis~, really. Lines: 49 In article <1080@cbmger.UUCP>, Peter Kittel GERMANY writes: > In article <18f0bf14.ARN1771@prolix.pub.uu.oz.au> dac@prolix.pub.uu.oz.au writes: > > > > I could put all 95 characters in the > ^^^^^^^^^^^^^^^^^ > >lookup table > >-- > >{Send your flames to =Marc Barrett=, he's used to 'em} > > Ehm, I think here's a flame necessary: WHY THE H*LL DO YOU ONLY RECOGNIZE > 95 CHARACTERS??? From my counting, the Amiga character set holds excatly *** Oy, I told you to flame =MB=, not me! :-( *** But, to answer your question; Of course, you are correct, there is no real reason, other than lazyness, for not recognising all the wonderful characters in the normal USA keymap, or even the international ones, and if I had a 'read the bitmap from the font' program, I could do it, I guess. But I don't. Yet. Is anyone going to answer that one? [Remember - Arexx solutions only!] Manipulating characters that are generated by deadkeys is, to my eyes, a hardship that I don't want to go through. Heck, the whole premise of the 'project' is to put a heading in a file -- so I can label listings and code with something that STANDS OUT. [The fact that I can also /easily/ generate large letters to irritate the **** out of netters is largely irrelevent :-)] Who is going to use ASCII 193 in the normal scheme of things? [Yes, lots of anal retentives out there will pick up obscure examples where such vacuosity is required, but I expect that, and snub them beforehand!] [Offhand, I don't know what ASCII 193 even is :-)] > double as many chars!!! And when I'm on my way: Why the h*ll are those > quite normal characters always represented as dots (== non-chars) in > hex dumps? Why? Those things with accents, graves, and umlauts on them? Removing all that extraneous data makes [the ascii part of] dumps easier to read! Obviously! > Let's take this to .advocacy, but let also all programmers know, that > there are more things than simply considering PAL or NTSC! Oh, ok. [See, I can be reasonable]. Dac --