Simon,
To give you some background:
The sql adapter will be based on the Zend_Db classes.
It will support dynamical tables. Actually most implementations I've seen
are fixed to a structure like "orig" -> "translation" or can only be
configured in a fixed config file. The sql adapter will be configurable in a
way where you can have all languages in one table, in different tables, in
different databases, named free and some more and at creation time. As the
implementation of the datastructure behind the adapter is highly
configurable it has the benefit to fit in any environment.
And this dynamic way is the reason why it's not finished for now. Because
there is some pre-work to the base class which has to be done before and
which affects all existing adapters.
The pre-work will be integrated with 2.0 because it will break BC which is
ONLY allowed for main releases.
We are now heading towards 1.6. I will integrate the new implementation in
the user space or incubator... have not decide for now as both would fit.
I hope you will stay and enjoy.
Greetings
Thomas Weidner, I18N Team Leader, Zend Framework
http://www.thomasweidner.com
----- Original Message -----
From: "Simon R Jones" <[EMAIL PROTECTED]>
To: <fw-general@lists.zend.com>
Sent: Thursday, June 05, 2008 11:07 AM
Subject: Re: [fw-general] Zend_Translate DB support
Thomas,
not at all - please don't take any offence! I haven't used Zend_Translate
a whole lot yet. I'm just asking a general question to see if there is
any work on support for managing translated strings within a database
(for a model rather than just messages) because I am tackling that as
part of a current project.
If that's what the SQL adapter is intended to do, that's great. I'll
restrict my further comments to that ZF issue.
best wishes,
Simon
On 5 Jun 2008, at 09:32, Thomas Weidner wrote:
So you know how I18N works in ZF better than me ?
You know how the ZF SQL adapter is designed ?
Why did you then ask ?
Greetings
Thomas Weidner, I18N Team Leader, Zend Framework
http://www.thomasweidner.com
