Hi peper Your situation is similar to mine. My solution is for a product would be, store a reference to the appropriate text string instead of a field of text in the product record.
So you have one "description" field that holds a key for the string (and all of its translations) Store the translated text in on table that has four fields: - id - key - language reference - text string Combine the reference with the language identifier and select the appropriate text string from the i18n table. This means that I have: - One table to store all of the text - Can implement as many languages as you like - Don't have a bloated product table. The down side of course is performance, however view caching can eliminate that. Regards, Langdon > I read about i18n and PEAR::Translation2 packages, and I even found a > cake component to use it. But it's not what I need. <snip> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" 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 -~----------~----~----~----~------~----~------~--~---
