W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > October to December 2005

RE: Glossary "non-text content" Small Nit

From: Richard Ishida <ishida@w3.org>
Date: Thu, 13 Oct 2005 12:00:28 +0100
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>
Message-Id: <20051013110029.61BC84EECF@homer.w3.org>

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

http://www.w3.org/People/Ishida/
http://www.w3.org/International/
http://people.w3.org/rishida/blog/
http://www.flickr.com/photos/ishida/
 

> From: w3c-wai-gl-request@w3.org 
> [mailto:w3c-wai-gl-request@w3.org] On Behalf Of Chris Ridpath
> Sent: Wednesday, October 12, 2005 8:43 AM
> To: WAI WCAG List
> Subject: Glossary "non-text content" Small Nit
> 
> 
> Our glossary defines non-text content as "Content that is not 
> represented by a Unicode character or sequence of Unicode characters".
> 
> Images and other binary content are often converted to 
> Unicode characters for transmission over the Internet. 
> It 
> could be interpreted that images and other binary content can 
> be represented as Unicode characters which is not the intent 
> of our glossary term.
> 
> I suggest that we add the text "in its native format" to the 
> glossary term so it reads:
> 
> "Content that is not represented by a Unicode character or 
> sequence of Unicode characters in its native format."
> 
> There is a note in the Wiki stating:
> It is possible to encrypt or encode any content including 
> binary files using Unicode characters but that would not 
> "represent the content using Unicode characters."
> 
> I think that the character encoded file does represent (stand for,
> symbolize) the original file. If we add the "in its native 
> format" text then this note could be removed.
> 
> Cheers,
> Chris
> 
> 
> 
Received on Thursday, 13 October 2005 11:00:56 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:47:40 GMT