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

RE: Glossary "non-text content" Small Nit

From: Christophe Strobbe <christophe.strobbe@esat.kuleuven.be>
Date: Wed, 12 Oct 2005 18:20:48 +0200
Message-Id: <6.0.0.22.2.20051012181025.03338180@mailserv.esat.kuleuven.be>
To: <w3c-wai-gl@w3.org>


At 18:04 12/10/2005, Gregg Vanderheiden wrote:

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

Chris proposed:
"Content that is not represented by a Unicode character or sequence of
Unicode characters in its native format."

The wording is very important here, because 'its' refers to 'content'.
If it is interpreted as referring to Unicode, we suddenly
appear to require a Unicode Transformation Format (UTF-8, UTF-16, ...),
which is not the intention.

How about the following?
"Content that is not represented by a Unicode character or sequence of
Unicode characters in the content's character encoding scheme."

Should we also modify definition of text 
(http://www.w3.org/TR/WCAG20/#textdef)?
We could change the first part to
"A sequence of characters in a character encoding scheme."

Regards,

Christophe Strobbe


>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

-- 
Christophe Strobbe
K.U.Leuven - Departement of Electrical Engineering - Research Group on 
Document Architectures
Kasteelpark Arenberg 10 - 3001 Leuven-Heverlee - BELGIUM
tel: +32 16 32 85 51
http://www.docarch.be/ 


Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm
Received on Wednesday, 12 October 2005 16:23:39 GMT

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