X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: f996b,1bcc16dd96d9ea5f
X-Google-Attributes: gidf996b,public
From: alanp@netcom.ca (Alan Popow)
Subject: Re: infinity
Date: 1996/11/19
Message-ID: <32920a3e.6435561@nntp.netcruiser>#1/1
X-Deja-AN: 197357103
references: <328B6ED4.361F@mach.uni-karlsruhe.de>
 <Pine.A32.3.95.961117100844.58363C-100000@homer19.u.washington.edu>
content-type: text/plain; charset=us-ascii
organization: Netcom Canada
x-netcom-date: Mon Nov 18 11:38:12 PM EST 1996
mime-version: 1.0
reply-to: alanp@netcom.ca
newsgroups: alt.ascii-art


On Sun, 17 Nov 1996 10:14:30 -0800, "J. Melusky" <whatfer@u.washington.edu>
wrote:

>Extended ASCII Characters in Windows and Help Files
>
>Actually, none of the extended ASCII figures appear in most Windows files
>according to the standard character set. This XASCII Help file shows you
>what each extended ASCII character number actually produces in a Help file
>and most other Windows files.
>
>ASCII characters 127-144, and 147-159 are null in Windows and Help files,
>they produce a black area on the screen ().  Character 160 produces a
>space which can act as a "hard space."

The thing is that the characters above 127 are "extended characters" NOT
"extended ASCII characters". There is nothing defined (or ascii) about any
of the extended characters. Mac will do one thing, IBM another etc. The
ASCII characters (127 and below) are defined the same way on all systems
that use ascii. That's why different system can actually exchange meaningful
information.

Alan