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

[ESW Wiki] Update of "its0504ReqLinkedText" by ChristianLieske

From: <w3t-archive+esw-wiki@w3.org>
Date: Wed, 20 Apr 2005 12:32:14 -0000
To: w3t-archive+esw-wiki@w3.org
Message-ID: <20050420123214.19104.29250@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 ChristianLieske:
http://esw.w3.org/topic/its0504ReqLinkedText


------------------------------------------------------------------------------
  
  Any text references to internal and external content, such as references to section titles and software UI items, should be implemented and identified in such a way that it is possible for localisation tools to automatically retrieve the actual text from original text places. 
  
+ '''[CL] Isn't "text references" too restricted? Wouldn't we also like to ensure for example that a screenshot/graphics which appears in a document, corresponds to a certain GUI element?'''
+ 
+ '''[CL] "retrieve the actual text" seems too ambitious from my point of view. Example: I might need a certain user and password in order to connect to the development repository. This information (user id and password) is not sth. I would like to code in the XML content. Suggested alternate formulation: Identify corresponding development object/referenced object uniquely.'''
+ 
  == Background ==
  
  Direct text references could occur as in the following examples:
@@ -28, +32 @@

   ...See also Work with Voucher for more information about this process. 
  
   Translation for “Work with Voucher” could have many variations depending on context, translation styles and target audience. If a chapter title, in the example above, is referenced in exactly the same format, the text should be represented as some sort of linkage in order to carry over the original text. This way, translators could avoid translating the same text repeatedly, which is very beneficial from the point of translation consistency as well as productivity.  
+ 
+ '''[CL] I am not sure about the "carrying over". In XML vocabularies I am familiar with, link often allows you to have a link text in the link source/origin that is different from the text of the link target. Example: <a>point to</a>, where the a element allows you to use arbitrary text. You are not restricted to the text in the link target. I guess there's a reason behind the provision for this mechanism.'''
  
   [Sample]
   <chapter id=”c18”>Work with Voucher</chapter> ...
Received on Wednesday, 20 April 2005 12:32:16 GMT

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