[pre-review feedback] qa-html-language-declarations

Hi Richard,
 From some WG protocoll I knew you were working on an update of 
http://www.w3.org/International/questions/qa-html-language-declarations-new

Will you continue?

I’ve already incorporated your changes into my translation: 
http://dev.bittersmann.de/International/questions/qa-html-language-declarations.de

You guessed it, I’ve found a thing or two: ;-)

»»
Always use a language attribute on the html tag
««

Using ‘element’ instead of ‘tag’ would be more precise:
Always use a language attribute on the html element


In some alt attribute:
»»
from the document text 'español'
««

Uppercase, actually:
from the document text 'Español'


In the source code (two times):
»»
<span xml:lang="sv" lang="sv">Español</span>
««

Fits well under heading ‘What if element content and attribute values 
are in different languages?‘ ;-) Not intended, I guess.

Make it both times:
<span xml:lang="es" lang="es">Español</span>


Sample code:
»»
<span title="Spanish"><a lang="es" 
href="qa-html-language-declarations.es">Español</a></span>
««

IMHO, the tooltip belongs to the link, i.e. the a element. Hence the 
elements should rather be nested the other way around, span inside a:

<a href="qa-html-language-declarations.es" title="Spanish"><span 
lang="es">Español</span></a>

(This doesn’t necessarily mean to change the article template, but would 
make a better example.)


»»
Instead, move the attribute containing text in a different language to 
another element, as shown in this example, where the span tag inherits 
the default en setting of the html tag.
««

Again, ‘element’ instead of ‘tag’ (both times):
Instead, move the attribute containing text in a different language to 
another element, as shown in this example, where the span element 
inherits the default en setting of the html element.


Under ‘Specifying metadata about the audience language’:
»»
Here is an example of an HTTP header that declares the resource to be a
mixture of English, Hindi and Punjabi:”
««

I wonder if “resource” wouldn’t refer to the text (instead of the target
audience), i.e. to what Content-Language is *not* about?


»»
HTTP or meta Content-Language information
««

Both ‘meta’ and ‘Content-Language’ are code keywords:
HTTP or <code class="kw">meta</code> <code 
class="kw">Content-Language</code> information


»»
on the html tag
««

Dito:
on the <code class="kw">html</code> tag

But should be better:
on the <code class="kw">html</code> element

Same in the following sentence:
If you have used the language attribute on the html element, as you 
always should

»»
Secondly, the <code class="kw">doctype</code> that should start any 
<del>HTML or</del> XHTML file
««

‘DOCTYPE’ must be in capitals for XHTML/polyglot HTML5:
Secondly, the <code class="kw">DOCTYPE</code> that should start any 
<del>HTML or</del> XHTML file

»»
The <code class="kw">doctype</code> in the example below
««

Dito:
The <code class="kw">DOCTYPE</code> in the example below


»»
Latin 1 (iso-8859-1)
««

Use uppercase (as elsewhere):
Latin 1 (ISO-8859-1)


»»
All this, however, is nowadays moot,
««

“Moot” refers to point ‘Thirdly’, not to all above. Remove ‘All‘. Don’t 
make it a separate paragraph, rather append the sentence to the previous 
paragraph.


»»
For example, Azerbaijani can be written using both right-to-left and 
left-to-right scripts
««

This would be clearer with the addition of the actual scripts:
For example, Azerbaijani can be written using both right-to-left 
(Arabic) and left-to-right scripts (Latin, Cyrillic)

Or without parentheses:
For example, Azerbaijani can be written using both right-to-left Arabic 
script and left-to-right Latin and Cyrillic scripts

Cheers,
Gunnar

Received on Monday, 25 August 2014 14:10:12 UTC