[Date Prev][Date Next]
[Thread Prev][Thread Next]
[Date Index]
[Thread Index]
[New search]
To: Lee Richardson <lhr@xxxxxxxxx>
Subject: Re: Help!: Update Frame for Mac OSX; We Need Your Votes!
From: Mark Barratt <markb@xxxxxxxxxxxxxxx>
Date: Fri, 29 Jun 2001 10:40:29 +0100
Organization: Text Matters
References: <5.1.0.14.2.20010628045803.03c70d90@mailsj.corp.adobe.com> <054601c0ffe3$877c1910$b77671d4@ydhomew2kws> <p05100301b76173cb2ec2@[216.15.97.176]>
Sender: owner-framers@xxxxxxxxx
Lee Richardson wrote: > That's silly. Full Unicode support has nothing to do with XML support I'm with Dmitry on this. The XML spec says: Legal characters are tab, carriage return, line feed, and the legal characters of Unicode and ISO/IEC 10646. The versions of these standards cited in A.1 Normative References were current at the time this document was prepared. New characters may be added to these standards by amendments or new editions. Consequently, XML processors must accept any character in the range specified for Char. The use of "compatibility characters", as defined in section 6.8 of [Unicode] (see also D21 in section 3.6 of [Unicode3]), is discouraged.] (let's leave aside the facts that competing products have patchy Unicode support and that other tools in the workflow may be ASCII- or ANSI-only, so full Unicode might not be much of a blessing for most users, but am I right in thinking taht if it's not Unicode-compliant it's not XML-compliant?) -- Mark Barratt Text Matters phone +44 (0)118 986 8313 fax +44 (0)118 931 3743 email markb@textmatters.com web http://www.textmatters.com ** To unsubscribe, send a message to majordomo@omsys.com ** ** with "unsubscribe framers" (no quotes) in the body. **