Consider whether it is useful to express the intended linguistic audience of a resource, in addition to specifying the language used for text processing.
+Consider whether it is useful to express the [=intended linguistic audience=] of a resource, in addition to specifying the language used for text processing.
@@ -268,7 +268,7 @@It is normal to express a text-processing language as the default language, for processing the resource as a whole, but it may also be necessary to indicate where the language changes within the resource.
Use the HTML lang and XML xml:lang language attributes where appropriate to identify the text processing language, rather than creating a new attribute or mechanism.
Use the HTML lang and XML xml:lang language attributes where appropriate to identify the text processing language, rather than creating a new attribute or mechanism.
lang attribute, while XML provides xml:lang which can be used in all XML formats. It's useful to continue using those attributes for relevant markup formats, since authors recognize them, as do HTML and XML processors.
@@ -281,7 +281,7 @@ It may also be useful to describe the language of a resource as a whole. This type of language declaration typically indicates the intended use of the resource. For example, such metadata may be used for searching, serving the right language version, classification, etc.
+It may also be useful to describe the language of a resource as a whole. This type of language declaration is called the intended linguistic audience of a resource. For example, such metadata may be used for searching, serving the right language version, classification, etc.
This type of language declaration differs from that of the text-processing declaration in that (a) the value for such declarations may be more than one language subtag, and (b) the language value declared doesn't indicate which bits of a multilingual resource are in which language.
@@ -875,7 +875,7 @@Do not assume that direction can be determined from language information.
Can we derive base direction from language?, W3C article.
+Can we derive base direction from language?, W3C article.
The information in this section is pulled from Requirements for Language and Direction Metadata in Data Formats. That document is still being written, so these guidelines are likely to change at any time.
+The information in this section is pulled from Strings on the Web: Language and Direction Metadata. That document is still being written, so these guidelines are likely to change at any time.
@@ -3567,7 +3567,7 @@