- From: Lieske, Christian <christian.lieske@sap.com>
- Date: Tue, 22 Aug 2006 10:03:00 +0200
- To: <public-i18n-its@w3.org>
- Cc: "Yves Savourel" <ysavourel@translate.com>
Hi Yves, I guess you may need this "overriding" in situations like the following: === You are would like to work with an external rules file. Unfortunately, the "termRule" in that file does not suit your needs. Thus, you want to get rid of it/cancel it. === I wonder if we really should provide an explicit cancellation mechanism and shouldn't just tell people that in cases like this, the need to create a separate "itsRules". Cheers, Christian -----Ursprüngliche Nachricht----- Von: public-i18n-its-request@w3.org [mailto:public-i18n-its-request@w3.org] Im Auftrag von Yves Savourel Gesendet: Monday, August 21, 2006 5:50 PM An: public-i18n-its@w3.org Betreff: Missing term="yes|no" attribute for <termRule> Hi everyone, I've noticed a possible over-simplification in <termRule>: At some point after the WD of February we decided to remove the term="yes|no" attribute in the global terminology rule, thinking it was not needed because it was always used as term="yes". I think it was a mistake: One should be able to override a previous rule that says a given element is a term. Or am I missing something? So, I would propose to re-instate the term="yes|no" in <termRule>. I've entered a corresponding new bug in our issues list: http://www.w3.org/Bugs/Public/show_bug.cgi?id=3612 Cheers, -yves
Received on Tuesday, 22 August 2006 08:12:12 UTC