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

[ESW Wiki] Update of "its0504ReqCulturalAspects" by YvesSavourel

From: <w3t-archive+esw-wiki@w3.org>
Date: Mon, 29 Aug 2005 05:03:21 -0000
To: w3t-archive+esw-wiki@w3.org
Message-ID: <20050829050321.31877.63329@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 YvesSavourel:
http://esw.w3.org/topic/its0504ReqCulturalAspects


------------------------------------------------------------------------------
  
  Author: Masaki Itagaki
  
+ = Content Styles =
- = Translation Styles =
- 
- '''[[YS-''' Isn't "translation styles" to specific? It seems we are taking about "writing styles". One may imagine to use such information even when not doing translation, for example for different linguistic-related taks, e.g. terminology extraction.''']]'''
- 
- '''[[CL-''' I would suggest to be even more generic and talk about "content styles" since localization isn't just about textual/written content but about non-textual content (such as graphics) as well.''']]'''
  
  == Summary ==
  
- It must be possible to specify writing styles in a target language in order to improve the quality of reused translated contents. The declaration of such an attribute should be done at the beginning of a document.
- 
- '''[[YS-''' Here too it seems we are maybe too specific. Maybe something like: "It must be possible to specify the writing styles in a document in order to better qualify the contents for different linguistic purposes, such as localization."
+ It must be possible to specify content styles in a document in order to better qualify the contents for different linguistic purposes, such as localization.
- 
- Note that if we keep the original sentence, "in order to better quality" would need some re-wording.''']]'''
-   
  
  == Challenge/Issue ==
  
@@ -34, +25 @@

  
  '''Japanese:''' Japanese uses a polite style (です・ます調 [Desu/masu tone]) for user’s guides and a formal style (だ・である調 [Da/dearu tone]) for academic and legal content. 
  
- Writing styles and tones in a target language vary mostly depending on target audience (general users, academic experts, etc) and content’s domain (IT, legal, medical, etc). While a source language does not get affected by such aspects, target content may need to use a specific writing style. 
+ Content styles and tones in a target language vary mostly depending on target audience (general users, academic experts, etc) and content’s domain (IT, legal, medical, etc). While a source language does not get affected by such aspects, target content may need to use a specific content style. 
  
- Information about writing styles is critical in reusability of translation. For example, certain content from a user’s guide in Italian may not be appropriate to be reused in online help content, while corresponding English content has no such issue.
+ Information about content styles is critical in reusability of translation. For example, certain content from a user’s guide in Italian may not be appropriate to be reused in online help content, while corresponding English content has no such issue.
  
  == Quick Guideline Thoughts ==
+ 
- A writing style in translation should be provided as a document metadata. There are no “absolute” values for this type of attribute, and each language and user could have its own values, which should be defined in schema. For example, a user might want to specify generic style guide names to specify writing styles as following: 
+ A content style in translation should be provided as a document metadata. There are no “absolute” values for this type of attribute, and each language and user could have its own values, which should be defined in schema. For example, a user might want to specify generic style guide names to specify writing styles as following: 
  
  '''[[CL-''' If I understood Tim correctly, he suspects that a "non-controlled" set of values for style may not be of great help.''']]'''
  
Received on Monday, 29 August 2005 10:15:18 GMT

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