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

[ESW Wiki] Update of "its0504ReqLinkedText" by MasakiItagaki

From: <w3t-archive+esw-wiki@w3.org>
Date: Thu, 19 May 2005 05:58:55 -0000
To: w3t-archive+esw-wiki@w3.org
Message-ID: <20050519055855.10394.86180@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 MasakiItagaki:

  Author: Masaki Itagaki
  = Links to internal/external text =
+ == Summary ==
  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?'''
@@ -21, +21 @@

  '''[[YS-''' So maybe something like: "...it is possible for localization tools to automatically retrieve the information about how to access the references at their original locations." ''']]'''
- == Background ==
+ '''[[MI-''' However, how to retrieve the linked data should be an seperate issue. It's not just an authentication issue. Accessing to external data may require a specific access parameters, URL, ane even a specific application. How to access to external data should be left to a rendering application or process. When the Linked Tag has something like ''src=/database/formItems/description@pk=123'', how to access to the data in the description field of the formItems table should be taken care of by a rendering tool or a localization tool. ''']]'''
+ == Challenge/Issue ==
  Direct text references could occur as in the following examples:
Received on Thursday, 19 May 2005 06:13:43 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:04:04 UTC