Unless I've misunderstood, I think what you are looking for is the
Model Translate behaviour, a related part of the new
internationalisation features of 1.2.
On Sep 10, 6:11 pm, francky06l <[EMAIL PROTECTED]> wrote:
> Well you can use the current language ('Config.language') to set it in
> your DB and then use the current language as a condition when
> querying. In anyway that will force the user to enter his post in the
> language he decided to display the page ...Unless you can detect the
> language from the fields in the post ...but that's another story.
>
> On Sep 10, 8:56 pm, cakeFreak <[EMAIL PROTECTED]> wrote:
>
> > hey guys, sorry for my late replay, and cheers for your help.
>
> > I'll try to be less cryptic.
>
> > Let's take a multilingual website with a specular section in language
> > 1 (italian), and language 2 (english). When in other circumstances I
> > was in this kind of situation I used to add an extra "language field"
> > in the DB, that was "it" when I was posting in Italian, and "en" when
> > posting in English.
>
> > When an user was surfing the API in english, the system was retrieving
> > posts marked with the language field "en", while it was retrieving
> > posts marked with "it" when the user was broasing the API clicking the
> > italian flag.
>
> > Has the "i18n" library been set in order to handle the problem I
> > described above?
>
> > cheers Dan
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Cake
PHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~----------~----~----~----~------~----~------~--~---
