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

AW: Features at risk

From: Lieske, Christian <christian.lieske@sap.com>
Date: Mon, 25 Sep 2006 11:24:52 +0200
Message-ID: <544FBEB6875DAA46A08323B58D26B8011E7A3E@dewdfe14.wdf.sap.corp>
To: "Felix Sasaki" <fsasaki@w3.org>, <public-i18n-its@w3.org>

Hi Felix,

So "feature at risk" is everything for which we do not get two implementations? Are there other criteria? 

-----Ursprüngliche Nachricht-----
Von: public-i18n-its-request@w3.org [mailto:public-i18n-its-request@w3.org] Im Auftrag von Felix Sasaki
Gesendet: Saturday, September 23, 2006 3:01 AM
An: public-i18n-its@w3.org
Betreff: Features at risk

Hi all,

Yves and me had a discussion on what we will implement or not. Yves wrote:

[[I'm planning on implementing with (for real application)
- Translate
- Localization Note
- Element Within Text

- Terminology is also implemeneted but that not have a real application
so far.

Maybe (not not sure at all):
- Language Information
- Directionality

- Ruby

>From what I think, it seems Ruby, Directionality, and Language
Information are the features the most at risk.]]

I will implement everything, but if we don't have somebody who promises
to make another implementation for Ruby, Directionality, and Language
Information, these need to be marked as features at risk.

Note that "implementation" means not necessarily to do something useful,
but to generate a result format like :
<nodeList datacat="languageInformation">
  <node path="/Manual" outputType="no-value">
  <node path="/Manual/Section[1]/Ltitle[1]/Mtitle[1]/MultiCol[1]"
   <output myLangAttr="en"/>
   <output myLangAttr="en"/>

Sebastian, others: who could do that for Ruby, Directionality, and
Language Information?


Received on Monday, 25 September 2006 09:25:25 UTC

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