Re: Encoded rendering instructions (was Unicode's Mandate)

From: Christopher Fynn (
Date: Wed Mar 09 2005 - 21:18:23 CST

  • Next message: Dean Snyder: "Re: Encoded rendering instructions (was Unicode's Mandate)"

    Dean Snyder wrote:

    > Patrick Andries wrote at 9:53 AM on Wednesday, March 9, 2005:

    >>Or a clever XML editor that would split such spans into well-formed
    >>(non-overlapping) equivalent hierarchies?

    > Yes, of course, but those sorts of kludges are only indicators of the
    > design problems inherent in current xml (and why I use empty tags for
    > everything). Plus these markup "solutions" quickly balloon into
    > complicated fragility and undermine the xml's design goals for robustness
    > and simplicity.

    And encoding "damage indicators" wouldn't undermine the design goals,
    simplicity and robustness of Unicode?

    If you have a manuscript with a big hole in it or a tear wouldn't you want
    to be able to indicate that kind of overall damage as well as damage to
    individual glyphs?

    - chris

    This archive was generated by hypermail 2.1.5 : Wed Mar 09 2005 - 21:19:26 CST