I don't follow you. If metadata and data are kept seperate there wouldn't
be _any_ confusion as to what is text. And how does Postscript, Tk get
into the picture? Rendering is after the underlying data is understood.
<chaim>
"NI" == Nick Ing-Simmons <nick(_at_)ni-s(_dot_)u-net(_dot_)com> writes:
NI> Chip Salzenberg <chip(_at_)perlsupport(_dot_)com> writes:
Defining the content in terms of markup leaves would imply that no
text exists that does not participate in the metadata system somehow.
NI> In the limit :
NI> The byte 0x41 is markup, saying render upper-case variant of 1st letter
NI> of Latin alphabet.
I don't feel comfortable with that, even as an abstraction.
NI> I do feel confortable to some extent, because of issues with
NI> displaying / formatting text in PostScript, Tk etc.
NI> Outside the bounds 0x20..0x7E you need meta data (perhaps implied)
NI> to know what a byte _means_ as text.
--
Chaim Frenkel Nonlinear Knowledge, Inc.
chaimf(_at_)pobox(_dot_)com
+1-718-236-0183
