RE: [regrep-cc-review] Core Components and Internationalization

[Diego Ballvé <diego.ballve@republica.fi>]

Currently only RegistryObject.name and RegistryObject.description
are I18N aware. If we start storing I18N-caable strings in Slots,
it means that Slot values must support Internationalization. This
brings some load to Registry specs, but IMO it is desirable.

Diego

> -----Original Message-----
> From: Fuger, Sally [mailto:sfuger@aiag.org]
> Sent: Wednesday, June 11, 2003 5:54 PM
> To: Nikola; CCRev
> Subject: RE: [regrep-cc-review] Core Components and 
> Internationalization
> 
> 
> +1
> Sally
> 
> -----Original Message-----
> From: Nikola [mailto:nikola.stojanovic@acm.org]
> Sent: Wednesday, June 11, 2003 10:50 AM
> To: CCRev
> Subject: Re: [regrep-cc-review] Core Components and 
> Internationalization
> 
> 
> <Joe>
> I would like to recommend that we ensure that we accomodate
> Internationalization in all of the work that we do here. This 
> means that
> when we map from CCTS to the RIM, we ensure that whatever 
> attributes we
> map to are I118N-capable - and if they are not, we consider proposing
> that they are I118N-capable.
> </Joe>
> 
> ++1.
> 
> Nikola
> 
> You may leave a Technical Committee at any time by visiting 
> http://www.oasis-open.org/apps/org/workgroup/regrep-cc-review/
> members/leave_workgroup.php
> 
> 
> You may leave a Technical Committee at any time by visiting 
> http://www.oasis-open.org/apps/org/workgroup/regrep-cc-review/
> members/leave_workgroup.php
> 
>