Re: OOC Library and Locales

["Eric W. Nikitin" <enikitin@apk.net>]

Hi,

Tim Teulings <tim@edge.ping.de> wrote:
> >     components.  Each component should have a "locale attribute," which,
> >     if not set directly, should match the locale of its parent object.
> >     An object with no parent has its locale set to the default, when not
> >     set directly.
> 
> That does mean  every visible object and perhaps even some more
> (DateModel with print method for example). 

Yes.  That's what is proposed.


> While this is possible
> (implement a memeber and access methods in the apropiate base classes),
> isn't it a bit oversized? 

Maybe.  The experience I've had with internationalized Java
applications didn't require this.  I only needed to display one
locale/language at a time, so I could set the default locale and rely
on that for constructing components.


> Will you have dialogs where every objects
> will not have the same locale?

I think the reason for doing it this way is that, for example, a
program might have to manage several windows, each displaying a
different language.  You can set the locale for each parent window
individually, and all child components appearing in that window
display things appropriately based on the parent's locale.  You
shouldn't have to set a locale for each component separately.  Does
that make sense?


> >     Developers of visual components may also have to create ``Input
> >     Methods''.  The reason for this is that some languages (e.g.,
> 
> Yes, X has such concept and emacs (based on X?) has one, too. However I
> have neither experience nor documentation for this. 

Unfortunately, neither do I.


Eric