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

[ESW Wiki] Update of "its0505ReqNamingScheme" by YvesSavourel

From: <w3t-archive+esw-wiki@w3.org>
Date: Mon, 12 Sep 2005 08:32:56 -0000
To: w3t-archive+esw-wiki@w3.org
Message-ID: <20050912083256.28656.78469@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 YvesSavourel:

  <button id="cancel">Cancel</button>
  <message id="001">Cannot open the file</message>}}}
- [[MI One issue we might need to consider regarding this is specifying translatability. Translation tools usually specify either an element or an attribute as translatable/non-translatable. For example, you can specify <OK> as non-translatable, while <Cancel> is translatable. But if you do as <button id="OK".. or <button id="Cancel", then you cannot just disable translatability only for OK (unless otherwise a translation tool has some conditional mechanism in specifying translatability. This naming scheme may need to be considered only when translatablility doesn't matter.]]
- '''[[YS-''' I'm not sure I agree: we could have <button translate="no">OK</button> and <button translate="yes">Cancel</button>. And tools should be able to make the distinction no? I think the translatability should be independant from the element name. It's true that many current tools have that problem, but I would say it's a tool problem, not an XML issue. --- Masaki, did my comment make sense? For example, the problem you described was truie in Trados-6 bur is not true in Trados-7 anymore where you can specify parts that are translatation on attribute values (hence, demonstrating that it's a tool issue).''']]'''
Received on Monday, 12 September 2005 14:45:25 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:43:05 UTC