[ESW Wiki] Update of "its0504ReqCulturalAspects" by ChristianLieske

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 ChristianLieske:
http://esw.w3.org/topic/its0504ReqCulturalAspects


------------------------------------------------------------------------------
  
   - '''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"?'''
+ 
   - '''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"?'''
  
   - '''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".'''
+ 
   - '''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"?'''
  
  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 Monday, 18 April 2005 10:20:40 UTC