chips@usfvax2.UUCP (Chip Salzenberg) (08/24/87)
[I've added comp.text to the list.] In article <8892@brl-adm.ARPA>, edstrom%UNCAEDU.BITNET@wiscvm.wisc.EDU writes: } } In article <1804@vice.TEK.COM> dougg@vice.TEK.COM (Doug Grant) writes: } } > For those who say "but too much bandwidth would be used for } > 64-bit characters!" I say hang on - fiber optic communications } > are coming! } } [...] it's overkill. Single characters are relatively unimportant. } The rare occasions where one changes font in the middle of a word are } so few and far between that I can't remember the last time I missed } that feature. } } I could see something like that at the word or sentence level. Perhaps } define a data type called "form_string" whose first 4 or 8 bytes would } be formatting information. Actually, it's rather presumptuous to define n bits for color, m bits for font, etc. -- how many fonts will _you_ be using in five years? Nobody knows. It would be much simpler to store text in the "form_string" mentioned above. But why exclude font changes in the middle of a word? If we need a common interchange format for formatted text, let's use PostScript. It already exists and it's been implemented in several places. -- Chip Salzenberg UUCP: "uunet!ateng!chip" or "chips@usfvax2.UUCP" A.T. Engineering, Tampa Fidonet: 137/42 CIS: 73717,366 "Use the Source, Luke!" My opinions do not necessarily agree with anything.