- From: Chris Ridpath <chris.ridpath@utoronto.ca>
- Date: Thu, 13 Oct 2005 08:44:43 -0400
- To: "Richard Ishida" <ishida@w3.org>, "'Gregg Vanderheiden'" <gv@trace.wisc.edu>, "'WAI WCAG List'" <w3c-wai-gl@w3.org>
- Cc: "'Addison Phillips'" <addison.phillips@quest.com>, <fsasaki@w3.org>
> I cannot understand this. Images and binary content are transferred as > bytes, but not Unicode characters, surely. > Images and binary content are usually send as ASCII characters. Weird eh? Here's what Wikipedia has to say about the MIME standard: http://en.wikipedia.org/wiki/MIME RFC 822: http://www.ietf.org/rfc/rfc822.txt You can try it yourself. Send an image using email then look at the message source. The binary image file has been converted to ASCII characters. Cheers, Chris ----- Original Message ----- From: "Richard Ishida" <ishida@w3.org> To: "'Gregg Vanderheiden'" <gv@trace.wisc.edu>; "'Chris Ridpath'" <chris.ridpath@utoronto.ca>; "'WAI WCAG List'" <w3c-wai-gl@w3.org> Cc: "'Addison Phillips'" <addison.phillips@quest.com>; <fsasaki@w3.org> Sent: Thursday, October 13, 2005 7:00 AM Subject: RE: Glossary "non-text content" Small Nit > > I cannot understand this. Images and binary content are transferred as > bytes, but not Unicode characters, surely. > > Also, please be careful to maintain the separation between characters as > represented by the Unicode repertoire (asbstract) and characters > represented > in a particular Unicode character encoding. > > (See http://www.w3.org/TR/charmod/#sec-Perceptions and > http://www.w3.org/TR/charmod/#sec-Digital for further clarifications re > the > meaning of character). > > RI > > ============ > Richard Ishida > W3C >
Received on Thursday, 13 October 2005 12:44:53 UTC