Thanks for the offer. I couldn't resist; sliv's suggestion seemed pretty funny to me.
I'd been forced to put aside the Cake stuff I'd been working on for a while but will be taking another stab at i18n for complete pages stored in the DB. I'm just reviewing Rostislav's i18n behavior now, actually. It looks very good to me. http://www.palivoda.eu/2008/04/i18n-in-cakephp-12-database-content-translation-part-2/ A big problem with i18n is that nobody seemed to have (officially) documented it very well and, meanwhile, several people have come up with various solutions but have only partially explained what it is they did. All of the links on the GG FAQ page, for instance, raise more questions than they answer. That makes it difficult to decide if it's a good solution for one's own project. After carefully going through Rostislav's beavior, I think this is the way I'll be going. But, given that it relies on a 3rd party behavior, I doubt that it would be welcome in the official docs. On Mon, May 5, 2008 at 6:08 PM, John David Anderson <[EMAIL PROTECTED]> wrote: > > > On May 5, 2008, at 4:05 PM, b logica wrote: > > > > > You're suggesting i write the documentation for something i do not > > understand? > > I do. > > It's the best way to learn, and it's the best way for us to get docs > that are targeted to new people. > > If you need help reviewing it, I'm available. :) > > -- John > Docs Monkey > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
