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

ITS Teleconf - Friday Sep-08-2006 15:00 UTC

From: Yves Savourel <ysavourel@translate.com>
Date: Thu, 7 Sep 2006 17:37:15 -0600
To: <public-i18n-its@w3.org>
Message-ID: <009c01c6d2d6$8d914520$9b05a8c0@Breizh>

I18N ITS Teleconference: 

Friday, Sep-08-2006 

14:00 UTC (Usual time)

Bridge               : +1-617-761-6200 (Zakim) 
Conference code      : 4186 (spells "I18N") 
Duration             : 60 to 120 minutes 
Zakim information    : http://www.w3.org/2002/01/UsingZakim
Zakim bridge monitor : http://www.w3.org/1998/12/bridge/Zakim.html
Zakim IRC bot        : http://www.w3.org/2001/12/zakim-irc-bot.html
W3C IRC Web Client   : http://www.w3.org/2001/01/cgi-irc
IRC channel          : #i18nits on irc.w3.org:6665 


1) === Changes status

We went through all the changes to see if we could find any substantive one. We did not. However, we found that the status of the
following major changes should be discussed:

- http://www.w3.org/Bugs/Public/show_bug.cgi?id=3459 We changed content model of <locNote> element, to allow for e.g. its:dir or
its:ruby. No substantive change, it was not forbidden before. Rather a bugfix.

- http://www.w3.org/Bugs/Public/show_bug.cgi?id=3464 We added termInfoPointer. Not substantive, it is not a new mechanism, we have
it for other data categories already. Bugfix.

- http://www.w3.org/Bugs/Public/show_bug.cgi?id=3466 On "Existing ruby markup": We changed the reference to ruby and XHTML (or CSS)
from "normative" to "informative". Rationale: We made explicit that the border of conformance to ITS are the ITS basic features, not
s.t. which is built on top of them. For example in the case of ruby, the Ruby TR is only *one* way to use ruby markup. Extracting
ruby markup using global rules does not deploy the Ruby TR, but is another usage scenario. The same is true for directionality.

- http://www.w3.org/Bugs/Public/show_bug.cgi?id=3467 We changed rubyText to be an element, rather than an attribute. It is a
correction, we did that for locNote already (i.e. to use an element globally). Not in this list: renaming for clarification.

- http://www.w3.org/Bugs/Public/show_bug.cgi?id=3612 We added the term attribute globally, and gave the term attribute the values
"yes" and "no" (it had only "yes" before). Bugfix.

- http://www.w3.org/Bugs/Public/show_bug.cgi?id=3640 Made clarification of what is meant by default values, inheritance and

2) === Implemented changes:

We implemented the following changes. Please look at the new Editor's WD

- http://www.w3.org/Bugs/Public/show_bug.cgi?id=3287 done

- http://www.w3.org/Bugs/Public/show_bug.cgi?id=3456 done, see the new note below EX-locInfo-selector-2.xml

- http://www.w3.org/Bugs/Public/show_bug.cgi?id=3458 done in implementation sec. for translatability.

- http://www.w3.org/Bugs/Public/show_bug.cgi?id=3460 done

- http://www.w3.org/Bugs/Public/show_bug.cgi?id=3612 done, for examples EX-term-selector-1.xml , EX-link-external-rules-1.xml ,
EX-link-external-rules-2.xml, EX-link-external-rules-3.xml , EX-selection-global-1.xml, EX-selection-global-2.xml

- http://www.w3.org/Bugs/Public/show_bug.cgi?id=3640 done, see sec. 6.1

Received on Thursday, 7 September 2006 23:38:07 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:04:11 UTC