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

[ESW Wiki] Update of "its0601ReqInlineElements" by YvesSavourel

From: <w3t-archive+esw-wiki@w3.org>
Date: Wed, 25 Jan 2006 17:17:17 -0000
To: w3t-archive+esw-wiki@w3.org
Message-ID: <20060125171717.16197.19399@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:

  '''[http://esw.w3.org/topic/its0505WikiProcess  Status: Initial Draft]''' (Req Doc)
  ie. please focus on technical content, rather than wordsmithing at this stage.
- Author: Andrzej Zydron
  = Indentifying inline elements =
  Initial input: [http://people.w3.org/rishida/localizable-dtds/#inline-elements]
  == Summary ==
- [R025] ...
+ [R025] Methods must exist to allow to distinguish in a document the element that are "inline" (i.e. part of a mixed content) and the ones that are not.
+ '''[YS]- Andrzej, because we want to move forward quickly on this topic, and we were not sure if you would have the time to work on it, I've taken the action item to get it started. Obviously, feel free to edit it as needed.'''
  == Challenges ==
- ...
+ Knowing which elements are inline and which ones are not is important for most linguistic-related process:
+  * The segmentation of the document into sentences has to be in part driven from the structural elements.
+  * Inline elements must remain withing the text so they can be modified if necessary.
+  * Infering which elements are inline only from the document context is always enough. For example in the following code:
+  {{{<p><em>Special text</em></p>
+ <p>Less special text</p>}}}
+  there is no programatic way of guessing that <para> is structural, but <em> is an inline element.
Received on Wednesday, 25 January 2006 23:01:58 UTC

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