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

Re: Datacat for inline element

From: Martin Duerst <duerst@it.aoyama.ac.jp>
Date: Fri, 27 Jan 2006 10:53:32 +0900
Message-Id: <6.0.0.20.2.20060127105040.06e38e70@localhost>
To: "Yves Savourel" <yves@opentag.com>, <public-i18n-its@w3.org>

Hello Yves,

I'm wordering what you think the inline vs. block distinction
is needed for. This distinction is to some extent a stylesheet
issue, i.e. it may differ for different presentations of the
same content.

If this is relevant to internationalization and/or translation
(I'm guessing something to do with segmenting?), it would be
better maybe to talk about this in terms that are closer to
our area and clearly identify the relevance to i18n or l10n.

Regards,   Martin.

At 11:08 06/01/26, Yves Savourel wrote:

>Hi,
>
>Here are a few ideas for the "inline" data category 9or whatever it will 
>be called).
>
>The idea is to identify element like <b>, <span>, etc. that should be 
>included in the text runs, contrary to elements like <para>, <li>, etc. 
>that are often used as delimiter for blocks of text.
>
>1- we could use something akin to the translatibility datacat:
>
><its:documentRule inline='yes' inlineSelector="//b|//span"/>
>
>However there are several aspects to take in account:
>
>- Is this datacat is inheritable?
>
>- Do we need it in situ? (or just dislocated and in schema)
>
>If not, maybe the mechanism to use it would be different. A simple 
>enumeration could do it maybe?
>
>...just thinkin aloud agin.
>-yves
>
Received on Saturday, 28 January 2006 02:42:01 UTC

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