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

[ESW Wiki] Update of "its0503ReqLangLocale" by MasakiItagaki

From: <w3t-archive+esw-wiki@w3.org>
Date: Tue, 07 Jun 2005 07:04:27 -0000
To: w3t-archive+esw-wiki@w3.org
Message-ID: <20050607070427.3060.98089@localhost.localdomain>
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 MasakiItagaki:
http://esw.w3.org/topic/its0503ReqLangLocale


------------------------------------------------------------------------------
  
  Identifying languages (such as French and Spanish) and locales (such as Canadian French and Ecuadorian Spanish) is very important in rendering and processing document text and content properly since they provide specifications of language-dependent properties, such as 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 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, 
+ In order to simplify parsing process by documentation and localization tools, there should be declaration of a 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.  
- 
- '''[CL] Shouldn't we already here advice against truly multilingual documents? '''
- 
- '''[AZ] Avoid holding parallel source and target PCDATA in the same document. '''
- 
- <para>
-  <text xml:lang="en">
-    My hovercraft is full of eels.
-  </text>
-  <text xml:lang="fr">
-    Mon aéroglisseur est plein d'anguilles.
-  </text>
-  <text xml:lang="hu">
-    Légpárnás hajóm tele van angolnákkal.
-  </text>
-  <text xml:lang="ja">
-    私のホバークラフトは鰻で一杯です。
-  </text>
-  <text xml:lang="pl">
-    Mój poduszkowiec jest pełen węgorzy.
-  </text>
-  <text xml:lang="es">
-    Mi aerodeslizador está lleno de anguilas.
-  </text>
-  <text xml:lang="zh-CH">
-    我隻氣墊船裝滿晒鱔.
-  </text>
-  <text xml:lang="zh-TW">
-    我的氣墊船充滿了鱔魚 [我的气垫船充满了鳝鱼]
-  </text>
- </para>    
-    
- 
- 
- ''' Unless your document requires mixed language content use a separate document instance to store each target language version. If you store both source and target data in the same document it will become unwieldy, overly large and cumbersome to process.'''
- 
- 
- subsets of the document needs a language/locale attribute. Such a local language/locale specification should be declared against an element or a span.  
  
  == Notes ==
- 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]. XML 1.0 prescribes a langauge identification attribute "xml:lang" [http://www.w3.org/TR/REC-xml/#sec-lang-tag]/[http://www.w3.org/XML/xml-V10-3e-errata]. ITS should carefully review these existing industry standards and clearly define what is a language/locale and its purpose in order to successfully meet this requirement. '''[[FS''' You might want to add a reference to the locale data markup language, see [http://www.unicode.org/reports/tr35/]. ''']]''
+ 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]. XML 1.0 prescribes a langauge identification attribute "xml:lang" [http://www.w3.org/TR/REC-xml/#sec-lang-tag]/[http://www.w3.org/XML/xml-V10-3e-errata]. There is also a technical standard from Unicode regarding the locale data markup language (LDML) [http://www.unicode.org/reports/tr35/]. ITS should carefully review these existing industry standards and clearly define what is a language/locale and its purpose in order to successfully meet this requirement. 
+ 
  == Quick Guideline Thoughts ==
  N/A
  
Received on Tuesday, 7 June 2005 08:01:51 GMT

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