W3C home > Mailing lists > Public > public-i18n-its@w3.org > January to March 2006

RE: Datacat for inline element

From: Richard Ishida <ishida@w3.org>
Date: Mon, 30 Jan 2006 11:51:45 -0000
To: <public-i18n-its@w3.org>
Message-ID: <009601c62593$8b91b480$6401a8c0@w3cishida>

> understanding is  
> that this is the fulfillment of the requirement described by 
> Richard at  
> http://people.w3.org/rishida/localizable-dtds/#inline-elements , in  
> summary:
> 
> "There should be a means of indicating whether an element is 
> equivalent or  
> not to a unit that will be used for automated translation 
> processing. Some  
> elements may contain other elements which are translation 
> units in their  
> own right."
> 


Caution: That section was not thought out thoroughly at the time, as indicated by the note in the text.  

Just some quick thoughts.

I guess one requirement for translation is for translation tools to be able to work out which elements should not constitute segment delimiters.  This applies in HTML to inline elements such as <em>, <strong>, <span>, etc.

Note that this is meta information, and I'm wondering (without a great deal of thought on the matter) whether this is really ITS related or actually pure localization properties stuff.

Another potential requirement is perhaps for an element that indicates translation segment boundaries when they may not otherwise be apparent.  For example, something like XHTML 2's line element, which replaces the <br> element in HTML, or something that can be used to indicate sentence-like units within markup, that can be used for detailed segmentation prior to source matching (eg. translation memory).  This is a very different requirement, and at a very different level, than the previous one.


RI
Received on Monday, 30 January 2006 11:51:49 UTC

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