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

[ESW Wiki] Update of "its0505ReqLocNotes" by ChristianLieske

From: <w3t-archive+esw-wiki@w3.org>
Date: Tue, 28 Jun 2005 07:49:58 -0000
To: w3t-archive+esw-wiki@w3.org
Message-ID: <20050628074958.964.86798@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 ChristianLieske:
http://esw.w3.org/topic/its0505ReqLocNotes


------------------------------------------------------------------------------
  
   * indicate why a piece of text is emphasized (important, sarcastic, etc.)
  
- This can help translators avoid mistakes or avoid spending time searching for information. Two types of developer's note are needed:
+ This can help translators avoid mistakes or avoid spending time searching for information. Two types of informative notes are needed:
  
-  1. An alert contains information that the translator MUST read before translating a piece of text. The translation environment must bring this type of note to the attention of the translator before they begin to translate. (For example, an instruction to the translator to leave parts of the text in the source language.)
+  1. An alert contains information that the translator MUST read before translating a piece of text. Example: an instruction to the translator to leave parts of the text in the source language.
  
-  2. A description provides useful background information that the translator will refer to only if they wish. (For example, a clarification of ambiguity in the source text). The translation tool would still make this available to the translator, but would not force them to read it before attempting a translation. The translator may only receive an indication that such a note exists and have to take action to view the text.
+  2. A description provides useful background information that the translator will refer to only if they wish. Example: a clarification of ambiguity in the source text. 
  
-  3. The relationship between a note and the data to which the note pertains, should be unambiguous.
+ The relationship between a note and the data to which the note pertains, should be unambiguous.
  
+ === Quick Guideline Thoughts ===
  
- [[CL-- Concerning processing expectations: I guess we will have to cover processing expectations substantially when we create the actual specification for the tag set.]]
+ This requirement is related to the following processing expections:
  
+  1. Alert: The note is brought to the attention of the translators before they begin to translate. The translator cannot start/continue his translation without reading the note.
+ 
+  2. Description: The note is brought to the attention of the translators before they begin to translate. However, the translator is not forced to read the note before attempting a translation. The translator may only receive an indication that such a note exists and have to take action to view the text.
+ 
Received on Tuesday, 28 June 2005 09:33:32 GMT

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