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

[ESW Wiki] Update of "its0504ReqCulturalAspects" by MasakiItagaki

From: <w3t-archive+esw-wiki@w3.org>
Date: Tue, 19 Apr 2005 07:44:17 -0000
To: w3t-archive+esw-wiki@w3.org
Message-ID: <20050419074417.24479.36643@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 MasakiItagaki:

   - '''A language/locale cannot perfectly represent orthography''': e.g. "zh-CN" does not stipulate if it's simplified or traditional Chinese. Locale for Yugoslavia does not provide guidance as to whether the language should be writeen in Latin or Cyrillic scripts. 
  '''[CL] Couldn't this be tackled by a specific constraint such as "script"?'''
+ '''[MI] A solution could be through a new way of locale coding or another specification like "script" as you said. The point of this requirement here is that there must be something more than just a language/country information. '''
   - '''Multiple cultural preferences within one locale''': e.g. In Japanese ("ja-JP"), there are two official date formats – Japanese emperor date (Wareki) and a standard numeric date format (Yoreki).
  '''[CL] Couldn't this be tackled by a specific constraint such as "date-format"?'''
+ '''[MI] I'm not sure at this point how you can extend something like a language/country code to cover this issue. But it's not just a Japanese date format. The point is what if there is some cultural variants WITHIN the same locale. Again, this is about what we need more than a language/country code.'''
   - '''Finer language variations''': e.g. how does one indicate that a voice track is in the language spoken in German-speaking Switzerland rather than the language written there, since one is Schwytzertuutsch (Swiss Germen) and the other is very close to but not the same as 'High German'? How does one indicate that a piece of content is in 'International Spanish'? How does one indicate that this is English as spoken in the time of Chaucer?
  '''[CL] To me, we are looking at examples of different nature here. Whereas I can see standards related to Swiss German, I am for example not aware of a standard related to codification of "International Spanish".'''
+ '''[MI] To be honest, this one I carried over from an old requirement. I should have done some research on this by myself, but if either Richard or Yves could comment on this, I would appreciate it.'''
   - '''Different writing styles and tones in one language''': e.g. Japanese uses a polite style ("Desu/masu" tone) for user guides and a formal style ("Da/dearu" tone) for academic and legal content. Italian uses an informal style for software help content and a formal style for user guides.   
  '''[CL] Couldn't this be tackled by a note to a localizer or a specific constraint such as "style"?'''
+ '''[MI] This issue is more than a comment to localizers. Especially when a content management system reuses language content units, translation style is always an issue. Without style information, it could pull out contents with different styles and make up a new document. Actually styles are dependent on context (like a target audience or a target document), so a solution may come from tagging context information. But setting such possible soutions aside here, this requirement should just show the need of "mechanism" to indicate style information for content.'''
  Identifying these variations is very important especially for content reusability. For example, the same source-language content could be translated into two different target-language content units depending on context that leads to different writing styles (e.g. formal and informal in Italian). When the content is reused both in source and target languages, context information (such as whether the content is for a user guide or a user help) must be provided in order to reuse content with an appropriate writing style.   
Received on Tuesday, 19 April 2005 07:44:18 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:04:04 UTC