W3C home > Mailing lists > Public > public-i18n-its@w3.org > April to June 2005

[ESW Wiki] Update of "its0503ReqLangLocale" by YvesSavourel

From: <w3t-archive+esw-wiki@w3.org>
Date: Fri, 15 Apr 2005 11:59:41 -0000
To: w3t-archive+esw-wiki@w3.org
Message-ID: <20050415115941.23234.61243@swada.w3.org>
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "ESW Wiki" for change notification.

The following page has been changed by YvesSavourel:
http://esw.w3.org/topic/its0503ReqLangLocale


------------------------------------------------------------------------------
  
  = Identifying Language/Locale =
  
+ 
+ == Description ==
+ 
+ Any document at its beginning should declare a language/locale that is applied to both main content and external content stored separately. While the language/locale may be declared for the whole document as a primary language/locale, when an element or a text span is in a different language/locale from the primary declaration, it should be labeled appropriately. The language/locale declaration should use industry standard approaches.      
+ 
+ 
+ == Background ==
+ 
+ Identifying languages (such as French and Spanish) and locales (such as Canadian French and Ecuadorian Spanish) are very important in rendering and processing document text and content properly since they provide specifications of hyphenation, text wrapping rules, color usage, fonts, spell checking quotation marks and other punctuation, etc. 
+ 
+ In order to simplify parsing process by documentation and localization tools, there should be declaration of a primary language/locale that is applied to the whole document as well as externalized content. This should be done as a document-level property. Meanwhile, as a document may contain content with multiple languages/locales, subsets of the document needs a language/locale attribute. Such a local language/locale specification should be declared against an element or a span.  
+ 
+ 
+ == Note ==
+ 
+ Currently there are several different standards for language/locale specifications, such as RFC 1766 [http://www.ietf.org/rfc/rfc1766.txt] and RFC3066 [http://www.ietf.org/rfc/rfc3066.txt]. ITS should carefully review existing industry standards and clearly define what is a language/locale and its purpose in order to successfully meet this requirement.
+ 
Received on Friday, 15 April 2005 11:59:42 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:12:44 GMT