W3C home > Mailing lists > Public > www-international@w3.org > January to March 2007

Re: Comment on working draft "Specifying Language in XHTML and HTML Content"

From: CE Whitehead <cewcathar@hotmail.com>
Date: Fri, 23 Mar 2007 14:52:55 -0400
Message-ID: <BAY114-F4786A8E6DE2D1DE183075B36A0@phx.gbl>
To: cewcathar@hotmail.com
Cc: ishida@w3.org, www-international@w3.org

Hi,  my comments that I sent before because they were confusing;
here they are again;

(I put my comments online too

Comments on: "Internationalization Best Practices: Specifying Language in 
XHTML & HTML Content" 

    * Section 3
          o Section 3.1 par 4 {NOTE: Below par 4 you might discuss the 
language code:

            which might be used audience language only, and only under 
certain circumstances: (but I would never recommend it for text-processing 
language!--see note below:} "There are also pages where the navigational 
information, including the page title, is in one language but the real 
content of the page is in another. While this is not necessarily good 
practice, it doesn't change the fact that the language of the intended 
audience is usually that of the content, regardless of the language at the 
top of the document source."

            {ADD ??}

            > "A case where the audience and text processing languages 
differ slightly is an online foreign language lesson, written in a single 
language (immersion) but aimed at speakers of multiple languages; for 
example, the text-processing language might be only:


            (or only en , or only ar), while the audience language might be 
declared as:

            mul (multiple)

            or as both:

            mul, fr

            (since presumably the audience speaks some French)."
    * Section 5
          o Best Practice 1, "Note"

            "rather than an attribute on the html element"

            > "rather than attribute[s] on the html element"

            {COMMENT: there's more than one attribute sometimes, as both the 
lang and xml:lang attributes may be used.}
          o Best Practice 1, Par 8/9 (last Par before Background 

            "The relevance will depend on the structure used for the 

            {COMMENT: "relevance" is confusing. Do you mean "usefulness" or 
"effectiveness," or do you mean "location"?}
          o ??? Best Practice 2 "Discussion" par 3

            "Although we would normally recommended to declare the default 
text-processing language in the html tag, since only one language can be 
defined at a time when using attributes, there may appear to be little point 
in doing so if a document has separate content to support multilingual 
audiences. It may be more appropriate to begin labeling the language on 
lower level elements, where the actual text is in one language or another."
            {add to the end??}

            > ", and to just specify the character set in the html tag."

            {COMMENT: I'm new to some of this, you can declare the character 
set in the document type declaration and you can declare it in the meta tags 
can you declare it without a language tag such as en or mul??? SORRY!!}
          o Best Practice 4: Identifying changes in language within the 
document, "How to", par 2/3 ???

            "The lang attribute can be used on all HTML elements . . . "

            > "The lang and xml:lang attributes can be used on all . . . "

            {COMMENT: There is no mention of the xml: lang attribute in this 
paragraph. though not only can it can be used on all HTML elements; it is 
also used on XML elements.}

(I am still working on the French translation (sections 5 on, as I think we 
got feedback on the first part--
and may have more--
but if anyone wants to translate sections 6-8 into French for the purpose of 
getting comments, that would be great too as I may not get it done that 
fast; have other things to do; sorry; it's summer and not that shady here 
for the kitty who likes to sit in the car when I'm at the library)

--C. E. Whitehead

Exercise your brain! Try Flexicon. 
Received on Friday, 23 March 2007 18:53:19 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:40:53 UTC