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

Re: Elements within text

From: Felix Sasaki <fsasaki@w3.org>
Date: Fri, 28 Apr 2006 20:44:22 +0900
Message-ID: <44520016.3030606@w3.org>
To: Yves Savourel <yves@opentag.com>
Cc: public-i18n-its@w3.org
Yves Savourel wrote:
>> just for clarification: What about the (I think) docbook case:
>> <para><term>Palouse horses</term><ftnote><para>A palouse horse 
>> is the same as an Appaloosa.</para></ftnote> have spotted coats.</para>
>> are both <para> to be indicated as withinText="no"?
> Yes, I suppose. <ftnote> would be declared as subflow, then normal segmenting would occure for its content.
> DocBook is a going to be difficult to work out for withinText, no matter what we do: it's packed with elements of the same name used
> in different context. That's where the selector with XPath will be helpful (vs. a simple list of element names).

here is another case: in the TEI schema, these two variants are possible:

1) <p> some text .. <li><item>...</item></li> more text ...</p>

2) <p> some text .. </p><li><item>...</item></li> more text ...</p>

without thinking about the markup structure, both means: "there is a
paragraph, a list, and another paragraph". But in 2), the list is inside
the <p> element, so it looks like "there is a paragraph, it contains
some text, a list, and more text".

what would be the appropriate usage of withinText for such cases?

Sorry, these questions repeat many discussions we had already, but my
impression is that for withinText it would be beneficial to have many
examples in the tag set draft, both for 1) versus 2), and for
<ftnote><para>bla</para></ftnote> versus <ft>bla</ft>. What do you
think? Also, it might be useful to have a reference to TMX, since it
seems to me (without really knowing it) a use case for sub flow.



Received on Friday, 28 April 2006 11:44:52 UTC

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