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

Re: Default attributes

From: Felix Sasaki <fsasaki@w3.org>
Date: Thu, 02 Feb 2006 13:41:37 +0900
To: "Yves Savourel" <ysavourel@translate.com>, public-i18n-its@w3.org
Message-ID: <op.s4bwnnttx1753t@ibm-60d333fc0ec.mag.keio.ac.jp>

Hi Yves,

On Thu, 02 Feb 2006 07:50:13 +0900, Yves Savourel  
<ysavourel@translate.com> wrote:

> Hi everyone,
>
> I run into an example with some default attributes in my ITS processor  
> tests and it occurred to me that we never talked abou them.
>
> I assume the following:
>
> When attributes are generated automatically from the DTD:
>
> - They should participate to the selection (e.g. if a DITA DTD has a set  
> translate="yes")
>
> - If the selector include them as transltable, then I'm not sure what we  
> should do? Treat them as translatable or treat them as
> read-only?

Sorry, I don't understand what you mean by read-only. But my proposal  
would be to say:

- if there is a default attribute for a data category(e.g.  
dita:translate="yes" ), it should be included in the mapping.
- other default attributes should be selected if their "realized"  
counterparts are selected as well.

> This is a bit off-topic since ITS simply points to the attributes, but I  
> wonder if we should not have some text somewhere
> about i18n/localizability and default attributes.

Good idea. How about having a "health warning" subsection or note e.g. in  
sec. 3. "Selection of ITS information" or sec. 3.5 "Mapping of ITS Data  
Categories to Existing Markup" which describes the problem and our  
solution suggestion.

Cheers,

Felix
Received on Thursday, 2 February 2006 04:41:44 UTC

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