RE: Two questions concerning i18n

Hello developers

I investigated further into the problem of translations of custom metadatasets. I found out, that I'm able to display my translated labels on the metadata tab if I change the i18n:domain in the page template Silva/views/edit/macro_edit_metadata.pt from 'silva' to 'my_domain'.
I guess that I've to provide explicitely the domain of my i18n somewhere in my metadata sets, for that this setting overrides the implicite 'silva' domain. How can I achieve this? I tried '<i18n_domain>my_domain</i18n_domain>' as child of the 'metadata_set' node in my metadata set, but this didn't work.

Any ideas?

Regards,
Benno


> -----Original Message-----
> From: eric casteleijn [mailto:[email protected]]
> Sent: Montag, 31. Oktober 2005 18:25
> To: eric casteleijn
> Cc: Luthiger Stoll Benno; [email protected]
> Subject: Re: [silva-dev] Two questions concerning i18n
> 
> 
> eric casteleijn wrote:
> > Luthiger Stoll Benno wrote:
> > 
> >> Dear Eric
> >>
> >> Thanks for the "on hold" feedback.
> >>
> >> Concerning my second question I read an interesting hint 
> titled "Zope, 
> >> Formulator, Localization, and the Solution to Translating Option 
> >> Values" while I was surfing through the Google world and 
> passed by the 
> >> blog on 
> http://betabug.ch/blogs/ch-athens/categorylist_html?cat_id=9.
> >>
> >> What do you think? Is this a/the solution?
> > 
> > 
> > Yes, it's basically what I proposed (perhaps somewhat 
> unclearly) in my 
> > first reply. It's not a beautiful solution, as noted on 
> that page, but 
> > it will work and it isn't *too* horrible either.
> 
> Also I would choose an even simpler solution, just to make 
> the code more 
> readable, and just have a script called something like 
> getMyFormOptionList for each list you need and return a the 
> correct list 
> of translated strings from that. No need IMO to make this workaround 
> very generic, unless you have hundreds of static option-lists 
> in your forms.
> 
> eric
>