On Thu, Jun 12, 2008 at 9:58 AM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Ok but what if you don't know what and how many languages a user may > need so rather something like > > shipping_terms_lang1 > shipping_terms_lang2 > shipping_terms_lang3 > shipping_terms_lang4 > > would be required... > > A google search for i18n behavior led to this nice howto which helpt > me a lot: > http://www.palivoda.eu/2008/04/i18n-in-cakephp-12-database-content-translation/ > and the second part > http://www.palivoda.eu/2008/04/i18n-in-cakephp-12-database-content-translation-part-2/ >
Yeah, Rostislav's behavior works really well for my site, which has basic CMS capabilities and is multilingual. I had already been setting up certain tables with separate fields for each language anyway (mostly lookup tables for select lists) and had my own mechanism for setting the correct field. But this behavior both simplifies and extends that (by definition). And he's just updated it. However, I'm not sure how it could help you with your site unless you're willing to offer a discrete set of languages. In fact, I'm not certain what it is you want to save in the DB. What do you mean by "shipping terms"? Could you give an example? Usually, multilingual data involves text that the site developer wishes to display to the user, but it seems that you're talking about user-submitted content. Is that correct? If so, I don't see how this should be a problem. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
