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

[ESW Wiki] Update of "its0503ReqSpan"

From: <w3t-archive+esw-wiki@w3.org>
Date: Sat, 02 Apr 2005 08:36:52 -0000
To: public-i18n-its@w3.org
Message-ID: <20050402083652.23408.40391@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 RichardIshida:
http://esw.w3.org/topic/its0503ReqSpan

------------------------------------------------------------------------------
  
+ '''[MD] I think this is clear enough for the moment. We can refine this later if needed.'''
+ 
+ 
  == Background: ==
  
  This allows localisation tools to determine their behaviour on certain sections of text. This could be for sections of text that need to be translated by a domain-expert (as with source code fragments) or need special terminology in order to be properly translated. In particular, a span-like element can be useful to help translation tools determine where to apply sentence-breaks and also to assist word-counting algorithms. Other uses are foreseen, within the scope of the ITS.
+ 
+ '''[MD] This omits a very important use of the <span> element, and the main reason it was added to HTML originally: language information.
+ Language information is important both for internationalization (e.g. different styling according to language) as well as localization (text needs to go to different translator, or not translated, or otherwise treated differently).'''
+ 
  
  One example would be the following sentence, which contains some source code that we would like to treat specially during translation :
  
@@ -49, +56 @@
  
  Are there any more that people can think of that don't directly fall into other sections, that is, I expect we would have particular requirements for dealing with terms, phrases, etc. elsewhere in the requirements document.
  ]''
+ 
+ '''[MD] I think two more aspects should be mentioned shortly:
+ 
+  - Any element that in and by itself doesn't carry specific semantics
+    is fine. If the target schema already has such an element, fine.
+  - Say where the element should be allowed in the target schema:
+    Everywhere where natural language/translatable text can appear.
+ 
+ I'm using the term 'target schema' here to talk about the schema that we are trying to internationalize/localize.'''
Received on Saturday, 2 April 2005 08:54:54 GMT

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