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

RE: Missing term="yes|no" attribute for <termRule>

From: Yves Savourel <yves@opentag.com>
Date: Tue, 22 Aug 2006 05:32:49 -0600
To: "'Lieske, Christian'" <christian.lieske@sap.com>, <public-i18n-its@w3.org>
Message-ID: <005101c6c5de$b3353ca0$0300a8c0@Breizh>

Hi Christian,

Yes, you describe one of the situations I had in mind.

But why would we have a different behavior for termRule? There is nothing different for translatability, for any of the other data
categories.

But you have a good point that we should note in the best practices: in some cases overriding is not the best solution, just making
a new set of rules could be better from the performance viewpoint (the less rules the better).

Cheers,
-yves


-----Original Message-----
From: Lieske, Christian [mailto:christian.lieske@sap.com] 
Sent: Tuesday, August 22, 2006 2:03 AM
To: public-i18n-its@w3.org
Cc: Yves Savourel
Subject: AW: Missing term="yes|no" attribute for <termRule>

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 11:35:01 UTC

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