Hi!
Sorry, I was not notified about comments on this post. If you want to
contact me drop a comment on the web site.
Yes, my idea is to keep translations in the same table as additional
fields, e.g we have a name property to be localizable, then we add
name_eng, name_rus etc. fields to the table
ros, this looks great! I was just in the past few days struggling to
sort out how to use the core Translate and/or some of the suggestions
made by other, in my own project. Nothing was working very well
(probably because of my own misunderstandings, but anyway ...) I went
to sleep last night plann
On Apr 16, 11:54 am, ros <[EMAIL PROTECTED]> wrote:
> Take a look as alternative to core CakePHP translate behavior - i18n
> model
> behaviorhttp://www.palivoda.eu/2008/04/i18n-in-cakephp-12-database-content-tr...
> It supports translation of related models (recursive is unlimited)
> during cotro
Hi!
Take a look as alternative to core CakePHP translate behavior - i18n
model behavior
http://www.palivoda.eu/2008/04/i18n-in-cakephp-12-database-content-translation-part-2/
It supports translation of related models (recursive is unlimited)
during cotroller find operation.
Regards,
ros
--~--~
