I've been working on something similar. You don't say whether the
select options are dynamic - from a db - or static. I haven't tried it
yet, but can't you just pass the message names wrapped in __(),
possibly with the true parameter, into the options?

On Feb 20, 5:55 pm, Alan Ford <[EMAIL PROTECTED]> wrote:
> I am trying to find out the usage of i10n and i18n with Cake 1.2.
>
> Let's try a simple example: I want to develop an app with
> multilanguage support. For simplicity let's say we have it in English
> and German.
>
> Now, let's pretend we have a form where you are supposed to select
> your gender from a select box. In the desired language, I will need to
> 1) display the label for the select box
> 2) populate the select box with the possible options
>
> Part 1 I will do via l10n and .po files as specified 
> inhttp://tempdocs.cakephp.org/#TOC135299
> This is pretty straight forward and works nicely.
>
> But how do I implement part 2 automagically with the correct gender in
> the desired language?
> How to make Cake retrieve the right content and save it with the
> correct id?
>
> I've taken a look at the proposed i18n table structure but cannot
> figure out how to implement it. From the i18n class description I also
> cannot really learn anything.
> From what I've understood, I will use the l10n class for any content
> that is not database-related, e.g. labels for form elements, error
> messages, titles etc. I'd use i18n as soon as I have data that needs
> to be displayed in different languages AND saved in the database.
>
> Any help, pointers, simple solution would be greatly appreciated!
>
> Thx in advance.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to