At 06:22 AM 6/21/2002 +0200, you wrote:
>The metainfo ComponentDescript class contains the name, classname,
>implementation version and attributes of a component together with a
>display name. I think we need to consider internationalization
>requirements for both the displayname element and attribute values.
Yep - I forgot about displayname. I planned to add in description as an
attribute so that it could be i18n'ed. The attribute was then going to be
keyed in usual fashion. ie Look for attribute "description-en_au", then
"description-en" and finally "description". However I think I prefer your
approach where the attribute value is key into normal i18n files.
Maybe we should make display name an attribute aswell?
> One approach I could impagine is a reserved leading character in a
> displayname or attribute value that is used to distinguish between a i18n
> resource key and plain text. For example if the value starts with #,
> then an implementation can attempt to resolve the string via the
> component's package i18n resource.
As long as that interpretation is restricted to specific "well known"
attributes or is considered container specific then I would be fine with that.
Cheers,
Peter Donald
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Faced with the choice between changing one's mind,
and proving that there is no need to do so - almost
everyone gets busy on the proof."
- John Kenneth Galbraith
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
