For clarity, we could print out a warning message stating that content-translator is "deprecated" and will be removed. We could remove it after a few release cycles, maybe.
-----Original Message----- From: Achim Hügen [mailto:[EMAIL PROTECTED] Sent: Monday, September 25, 2006 5:05 AM To: [email protected] Subject: Re: translator vs. content-tranlator A simple change would mean breaking the backward compatibility. So we had to support both namings and I fear that's not worth it, sorry. Achim Am Tue, 19 Sep 2006 21:26:55 +0200 schrieb [EMAIL PROTECTED] <[EMAIL PROTECTED]>: > Hi, > > i'm getting deeper and deeper into hivemind and i must > admit i like it very much. but what bothers me are some > minor details like naming of elements and attributes. > > would someone agree with me, that <element> should > have a "translator"-attribute instead of a > "content-translator"-attribute? wouldn't it be > more concise? Could that be changed in the next > release? > > g, > kris >
