RE: Fixed Width Spaces (was: Printing and Displaying DependentVow els)

From: Mike Ayers (mike.ayers@tumbleweed.com)
Date: Fri Apr 02 2004 - 14:00:34 EST

  • Next message: Kenneth Whistler: "Re: New Currency sign in Unicode"

    > From: unicode-bounce@unicode.org [mailto:unicode-bounce@unicode.org]On
    > Behalf Of Doug Ewell
    > Sent: Friday, April 02, 2004 8:34 AM

    > Arcane Jill wrote:
    >
    > > 0x80 if I remember correctly.
    >
    > I know you've already corrected yourself, realizing that you were
    > thinking of the extended-ASCII character set used by the ZX
    > Spectrum (TS
    > 2068, IIRC), but just to finish this thought:

            Another example is the dreaded "shifted space" of the Commodore 64.
    If you happened to have the shift key down when you hit the space bar, you
    generated a different character that printed as space, but didn't match
    space. So if there was a shifted space in a filename, the file was
    inaccessible until you tried shifting the spaces.

    > I'm sure they existed, but I can't remember anything sophisticated
    > enough to be called a "line breaking algorithm" in the ZX8*
    > environment.

            I know that runoff and word processors were common in CP/M
    environments (I had a Commodore 128, so I got three different machines to
    play with - lucky me!), and those had pretty sophisticated line breaking. I
    don't recall anything for the 64, so the ZX8* probably didn't have much, if
    anything, either.

    /|/|ike



    This archive was generated by hypermail 2.1.5 : Fri Apr 02 2004 - 14:44:01 EST