Re: fortran character set

Dan Nagle wrote:
Hello,

Phillip Helbig---remove CLOTHES to reply wrote:

<snip>

But isn't this just because the pound sign (£) and the number sign (#) are often on the same key and depending on the environment either one or the other might be printed? Alternatively, the ASCII code might be interpreted in a non-standard variant as the pound sign, so if I send you £ and say it is pound, you might see # and call it the pound sign.

We're getting into issues of fonts and so on.

That is probably why character sets are processor-dependent.
(Originally, character sets were processor-dependent
because they were very processor-dependent, sometimes
called "display codes" and varying from hardware to hardware
or even OS to OS on the same hardware.)

Today we have ASCII to standardize our confusion. :-)

Sounds like what we need is an ISCII.

cheers,

paulv
.

Relevant Pages

  • Re: fortran character set
    ... Alternatively, the ASCII code might be interpreted in a non-standard variant as the pound sign, so if I send you £ and say it is pound, you might see # and call it the pound sign. ... That is probably why character sets are processor-dependent. ... called "display codes" and varying from hardware to hardware ...
    (comp.lang.fortran)
  • Re: CAtlRegExp crashes with pound sign!
    ... > The pound sign is in my experience the only common character that ... it's because it has an Ascii code in the upper half of the table ... This would happen to any character in the upper Ascii, not just a pound ...
    (microsoft.public.vc.atl)