Hi,
I'm using i18n inside a xsl to translate the options of a html selector (combo-box). The individual options are generated by a user-defined cocoon action (in java) as i18n keys. The same action also processes the client response. Unfortunatly the parameter with the user selected item now contains the translated text, so I can't compare it with my i18n keys.
The options have a key and a value. While you should translate the value (= the displayed entry) you should of course not translate the key. The key is sent back to the server after the client made it choice. I18n should make no problem using it this way.
Joerg
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
