Re: DC.language Re: January 14 Minutes

So I am not sure why it matters to tools that these things are redundant. If
they don't know which is relevant to a particular instance (and in some
environments that is already known) they can readily include both, based on
an authoring interface that just asks for the language (and doesn't require
the author to know which particular encodings are being used anyway).

chaals

On Wed, 30 Jan 2002, Phill Jenkins wrote:

  Liddy,

  I'm still trying to get DC to fix a problem with the language meta tag.
  <HTML lang="en-US"> is very redundant with the <meta scheme="rfc1766" name
  ="DC.Language" content="en-us"/>

  Who in DC can help fix this?

  Authors, tools, and ATs are confused which to support.

  Regards,
  Phill Jenkins,  (512) 838-4517
  IBM Research Division - Accessibility Center
  11501 Burnet Rd,  Austin TX  78758    http://www.ibm.com/able


  Liddy Nevile <Liddy.Nevile@motile.net>@w3.org on 01/30/2002 03:36:36 PM

  Sent by:    w3c-wai-au-request@w3.org


  To:    Charles McCathieNevile <charles@w3.org>, Phill
         Jenkins/Austin/IBM@IBMUS
  cc:    <w3c-wai-au@w3.org>
  Subject:    Re: DC.language Re: January 14 Minutes



  Phill and Charles

  DC has just OK'd the new DC Accessibility IG and I am about to launch
  that - so that will be the perfect place for this discussion.

  The aim of the DC Accessibility IG is to work on Accessibility
  metadata - with the pay-off that will come from being part of one of
  the most effective standard movements...DC is starting to be
  everywhere.

  stay tuned!


  Liddy




-- 
Charles McCathieNevile    http://www.w3.org/People/Charles  phone: +61 409 134 136
W3C Web Accessibility Initiative     http://www.w3.org/WAI    fax: +1 617 258 5999
Location: 21 Mitchell street FOOTSCRAY Vic 3011, Australia
(or W3C INRIA, Route des Lucioles, BP 93, 06902 Sophia Antipolis Cedex, France)

Received on Thursday, 31 January 2002 12:27:28 UTC