Nico Klasens <[EMAIL PROTECTED]> wrote:
> > I don't understand why it would be a dirty hack something
> > similar to the xml:lang attributes on title-tags can be
> > supported, isn't it?
>
> <optionlist name="tonen">
> <option id="1" xml:lang="nl">Tonen (volgens embargo)</option>
> <option id="0" xml:lang="nl">Niet tonen</option>
> <option id="1" xml:lang="en">Show (according to embargo)</option>
> </optionlist>
>
> Now when a dutch person has selected "Niet tonen" what should happen when an
> english person wants to open the wizard? The xsl-code will be a nice piece
> of art.
I would perhaps go for:
<optionlist name="tonen" xml:lang="nl">
<option id="1">Tonen (volgens embargo)</option>
<option id="0">Niet tonen</option>
</optionlist>
<optionlist name="tonen" xml:lang="en">
<option id="1">Show (embargo)</option>
<option id="0">Don't show</option>
</optionlist>
to enforce, or at least suggest, that the complete list is translated, or
not at all. What should happen if an option is not present in one language,
but is in another I don't know. Nicest would be falling back to the default
language's option indeed, but if that would too arty to do in XSL I would
simply not do it. But it is done for titles, so I suppose it can also be
done for options...
Muichiel
--
Michiel Meeuwissen
Mediapark C101 Hilversum
+31 (0)35 6772979
nl_NL eo_XX en_US
mihxil'
[] ()
