- From: Gregg Vanderheiden <gv@trace.wisc.edu>
- Date: Wed, 12 Oct 2005 11:04:29 -0500
- To: "'Chris Ridpath'" <chris.ridpath@utoronto.ca>, "'WAI WCAG List'" <w3c-wai-gl@w3.org>
I think this wording (Chris's) is much better at getting at the problem Unless I hear otherwise - I am changing the text we will review later to this wording. This allows us to get rid of the awkwardly worded note. Thanks Chris. Others - comment if you see a hole. Gregg -- ------------------------------ Gregg C Vanderheiden Ph.D. Professor - Ind. Engr. & BioMed Engr. Director - Trace R & D Center University of Wisconsin-Madison -----Original Message----- 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 Wednesday, 12 October 2005 16:06:06 UTC