[ESW Wiki] Update of "its0504ReqTechWriter" by YvesSavourel

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


------------------------------------------------------------------------------
  
  = Usage Scenario: Content Authoring =
  
- [[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.]]
+ '''[[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.''']]'''
  
- [[CL  Could you give an example, how the ITS tag set or the guidelines could facilitate this? The usage scenarios from my understanding describe how our deliverables could/should be used in order to better accomodate localization-related processes. Aside concerning the relationship between stock phrases and memories: Isn't it the case that the number of source occurrances is almost irrelevant once you have a translation in the memory? Thus, the argument for stock phrases looses some weight.]]
+ '''[[CL'''  Could you give an example, how the ITS tag set or the guidelines could facilitate this? The usage scenarios from my understanding describe how our deliverables could/should be used in order to better accomodate localization-related processes. Aside concerning the relationship between stock phrases and memories: Isn't it the case that the number of source occurrances is almost irrelevant once you have a translation in the memory? Thus, the argument for stock phrases looses some weight.''']]'''
  
- [[AZ The ITS tag set could include an identifier to state that this is a 'stock' phrase and associate an identifier with the text. I do not understand the issue with the number of source occurrences. We are dealing here with trying to encourage authors to re-use existing sentences for which there will be translations. The number of times that such a phrase is used is not relevant. What is important is that exactly the same text is reused.]]
+ '''[[AZ''' The ITS tag set could include an identifier to state that this is a 'stock' phrase and associate an identifier with the text. I do not understand the issue with the number of source occurrences. We are dealing here with trying to encourage authors to re-use existing sentences for which there will be translations. The number of times that such a phrase is used is not relevant. What is important is that exactly the same text is reused.''']]'''
+ 
+ '''[[YS''' I think Christian means that the re-use of stock phrases, from the viewpoint of translation is less relevant now because TM allow to re-translate the same phrase automatically (correct me if I'm wrong). I half agree with that, but the usage of 'stock' phrases has additional advantages: one doesn't even need to touch the different documents that refer to the stock phrase, just the place where it is defined.
+ 
+ Does the addition below (identifier for re-usable text) addresses this?''']]'''
+ 
  
  == Description ==
  
@@ -28, +33 @@

   - sections of the document that should remain in the source language.
  
   - acronyms or complicated expressions with an explanation note for the translator.
+ 
+  - identifier for re-usable text.
  
  In other cases, the original text itself may need to be labeled for specific information required for correct rendering, such as ruby text in Japanese, or bidirectional overrides in Arabic.

Received on Tuesday, 17 May 2005 22:39:28 UTC