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

From: Peter Constable (petercon@microsoft.com)
Date: Wed Mar 09 2005 - 19:18:43 CST

Next message: Rick McGowan: "Re: Small Java implementation of NFC"

Previous message: Peter Constable: "RE: Encoded rendering instructions (was Unicode's Mandate)"
Maybe in reply to: Dean Snyder: "Encoded rendering instructions (was Unicode's Mandate)"
Next in thread: Dean Snyder: "Re: Encoded rendering instructions (was Unicode's Mandate)"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Mail actions: [ respond to this message ] [ mail a new topic ]

> From: unicode-bounce@unicode.org [mailto:unicode-bounce@unicode.org]
On Behalf
> Of Dean Snyder

> >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...

I don't think a limitation in XML regarding overlapping hierarchies
should be made a basis for encoding new characters.

Peter Constable

Next message: Rick McGowan: "Re: Small Java implementation of NFC"
Previous message: Peter Constable: "RE: Encoded rendering instructions (was Unicode's Mandate)"
Maybe in reply to: Dean Snyder: "Encoded rendering instructions (was Unicode's Mandate)"
Next in thread: Dean Snyder: "Re: Encoded rendering instructions (was Unicode's Mandate)"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Mail actions: [ respond to this message ] [ mail a new topic ]

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