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

[ESW Wiki] Update of "its0504ReqTechWriter" by YvesSavourel

From: <w3t-archive+esw-wiki@w3.org>
Date: Thu, 21 Apr 2005 16:09:26 -0000
To: w3t-archive+esw-wiki@w3.org
Message-ID: <20050421160926.10198.47453@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/its0504ReqTechWriter


------------------------------------------------------------------------------
  
  Author: Yves Savourel
  
+ = Usage Scenario: Content Authoring =
- = Usage Scenario: Technical Writer Using an Authoring Tool =
- 
- '''[CL] How about sth. more generic like "Usage Scenario: Content Authoring"? This would also cover e.g. a product manager writing a specification (and marking up terms), or a programmer writing raw documentation (and inserting code snippets). To me, this more generic usage also would have the advantage of fitting better with some of the activities described below (it might for example not be authors who decide that certain sections should not be translated; rather it might be something like a localization engineer).'''
  
  '''[AZ] For technical documents the use of standard 'stock' phrases are very often desirable both from th point of view of consistency, but also for increasing the amount of leveraged memory that can be located in TM systems. Is is desirable to provide technical authors with a facility to easily access and reuse previously authored or stock phrases.'''
  
@@ -21, +19 @@

  
  == Description ==
  
- As a technical writer develops a content that is meant to be localized, he or she may need to label specific parts of the text for various purposes, such as:
+ As an author develops a content that is meant to be localized, he or she may need to label specific parts of the text for various purposes, such as:
  
   - terms that should not be translated or translated using a pre-existing terminology list.
  
@@ -36, +34 @@

  
  == Stakeholders ==
  
- This scenario relates to the technical writers developping localizable content, to the developers of authoring systems, and to the translators.
+ This scenario relates to the technical writers developping localizable content, to the developers of authoring systems, as well as the localizers and the translators.
  
Received on Thursday, 21 April 2005 16:09:28 GMT

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