On Sunday, July 9, 2000, Andras Kadinger <[EMAIL PROTECTED]> wrote:
>Peter Gutowski wrote:
>>
>> I'll risk betraying my Macintosh roots, but would somebody
>please explain what 'codepages' are, and what they're used for.
>I've always got the sense that it had something to do with
>character encoding, but have no idea how to appreciate and
>evaluate what a sun wrote last month...
>
>Computers in the last few decades (historians would probably cringe at
....
>I hope after this short tour, the above sentence is
>understandable now.
>
>Regards,
>Andras Kadinger
Wow! That was quite an explanation. I'm delighted of course -- I never expected such
depth. Thank you.
You mentioned
> user could 'turn pages', change the character
> set displayed with a command
Are there Linux (Windows, Mac..) commands that do that? Are we just talking about file
names or text content of files? If I write:
"G�ste kamen und G�ste gingen" (R. Wagner, "Die Walk�re", 1. Acte)
...does this look incorrect to you? (Umlauts over a's in Gaste and u in Walkure)
I noticed when looking at Mac files (e.g. "OurLogo/Blk&PMS284.eps") in a terminal
window under Linux and that the "objectionable" characters were rendered with a colon
(:) followed by 2 hexidecimal digits of that character (same example:
OurLogo:2fBlk&PMS284.eps). My afpd (preasun2.1.4-39) seems not to render the "/" as a
single charater, but as a trigraph. Is that what a sun means that it's without
codepage support?
--
Peter Gutowski / [EMAIL PROTECTED]
"Millions long for immortality who don't know what to do on a rainy day." -- Susan
Ertz (c. 1894-1985), American Writer
