Re: I18N in seperate files

List for Users of Carlsbad Cubes' Technologies and Products <[email protected]> schrieb am 14.09.05 07:49:29:
> 
> 
> 
> List for Users of Carlsbad Cubes' Technologies and Products <[email protected]> schrieb am 13.09.05 18:18:40:
> > 
> > Hi,
> > 
> > We have the same issue. We've got quite a big application so to keep
> > it maintainable
> > we split it in logical modules and we have one locale file per module like
> > module1_en.properties, module2_en.properties ... etc. 
> > To make a reuse of common translations (like "ok", "cancel" ) we have
> > common_en.properties.
> > So what we tried to do with swixml was something like this
> > 
> > <frame bundle="module1">
> >     <panel it="mainPanel">
> >         ...
> >     </panel>
> >     <panel it="okCancelPanel" bundle="common">
> >         ...
> >     </panel>
> > </frame>
> > 
> > But it didn't work.
> > So I wonder if swixml supports this construction at all.
> 
> I looked into the Parser-class of swixml and this attribute is only supported for the root-Element:
>     getSwing( processCustomAttributes( jdoc.getRootElement() ), container );
> 
> It is not that easy to change this because the localizer (responsible
> to localize attributes) is a static one, which is not easy changable either.
> 

Ok, it was about one hours work -- it works for a simple example but has to be cleaned up. Perhaps I get completed this week... To assign multiple bundle files (separated by "," or whatever) seems to be a good idea too, what do you think?

Frank