W3C home > Mailing lists > Public > public-comments-wcag20@w3.org > November 2007

[UND WCAG2] i18n comment: Content in two languages

From: Richard Ishida <ishida@w3.org>
Date: Tue, 27 Nov 2007 18:46:32 -0000
To: <public-comments-wcag20@w3.org>
Message-ID: <00ad01c83125$d4d307d0$6401a8c0@rishida>


Thank you.  The i18n Core WG is satisfied wrt this comment.

RI

============
Richard Ishida
Internationalization Lead
W3C (World Wide Web Consortium)
 
http://www.w3.org/International/
http://rishida.net/blog/
http://rishida.net/

 
 

> -----Original Message-----
> From: public-i18n-core-request@w3.org 
> [mailto:public-i18n-core-request@w3.org] On Behalf Of Richard Ishida
> Sent: 16 November 2007 14:07
> To: public-i18n-core@w3.org
> Subject: RE: [UND WCAG2] i18n comment: Content in two languages
> 
> 
> > -----Original Message-----
> > From: Loretta Guarino Reid [mailto:lorettaguarino@google.com]
> > Sent: 04 November 2007 05:09
> ...
> > Please review our resolutions for the following comments,
> and reply to
> > us by 19 November 2007 at public-comments-wcag20@w3.org to
> say whether
> > you are satisfied. Note that this list is publicly archived.
> ...
> > WCAG 2.0 Editor's Draft of May-October 2007 at 
> > http://www.w3.org/WAI/GL/WCAG20/WD-WCAG20-20071102/
> > 
> ...
> > ----------------------------------------------------------
> > Comment 2: Alternative language for example 1
> > Source: 
> > http://lists.w3.org/Archives/Public/public-comments-wcag20/200
> 7Jun/0012.html
> > (Issue ID: 1960)
> > ----------------------------
> > Original Comment:
> > ----------------------------
> > 
> > > Comment 4
> > > At
> http://www.w3.org/International/reviews/0606-understanding-wcag2/
> > > Editorial/substantive: S
> > > Owner: RI
> > >
> > > Location in reviewed document:
> > > 3.1.1 Example 1
> > >
> > > Comment:
> > > "A Web unit produced in Germany includes content in both
> German and
> > > English, but most of the content is in German. The
> primary natural
> > > language is identified as German (de)."
> > >
> > >
> > > If the primary language is expressed using HTTP or meta
> tags, it is
> > > possible that both languages should be identified if this is a 
> > > document aimed at a bilingual audience. If the primary
> > language is to
> > > be expressed in the html element tag, only one language can
> > be chosen.
> > > This example is too vague. This goes back to the question
> > of what WCAG
> > > means by 'primary language'.
> > >
> > > ----------------------------
> > > Response from Working Group:
> > > ----------------------------
> > >
> > > We have clarified our use of primary language to be the
> > default human
> > > language of the Web page, and we changed SC
> > > 3.1.1 to read "The default  human language  of each  Web
> > page  within
> > > the content can be programmatically determined." We included a 
> > > reference to Internationalization Best Practices:
> > > Specifying Language in XHTML & HTML Content, and added a
> > discussion of
> > > multilingual documents to the Intent section.
> > > We added "default" to the example to make it clearer why this 
> > > satisfies the SC.
> > >
> > > Currently assistive technologies do not support specifying
> > languages
> > > in HTTP headers or meta tags, so those techniques are not
> > considered
> > > sufficient at this time.
> > >
> > > HTTP headers and meta tag marking of languages can identify
> > multiple
> > > languages, as you point out. Specifying multiple languages
> > in the http
> > > header or in meta-data would not specify a default text
> processing
> > > language, so such usage would not satisfy this success
> > criterion. This
> > > would be discussed when those techniques are written.
> > 
> > The I18n Core WG thanks you for these changes.
> > 
> > We are not sure how useful the example is, without implementation 
> > detail, but that is a different question.  We think we would have 
> > preferred something like "A Web page written in HTML and produced...
> > The default human language is identified in a lang attribute on the 
> > html element.  Since the lang attribute can take only one
> value, and
> > since most of the content is in German, German was specified as the 
> > default human language."
> > 
>  ---------------------------------------------
>  Response from Working Group:
>  ---------------------------------------------
>  
>  We have made the example more specific, so it now reads:
>  
>  A Web page produced in Germany and written in HTML includes content 
> in both German and English, but most of the content is in German. The 
> default human language is identified as German (de) by the lang 
> attribute on the html element.
>  
>  Implementation details are typically available in techniques. 
>  We have added the following to technique H57:
>  
>  Both the lang and the xml:lang attributes can take only one value.
> 
> 
Received on Tuesday, 27 November 2007 18:43:48 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 17 July 2011 06:13:24 GMT