| RE: [cosmos-dev] Globalization considerations for the COSMOS DC |
|
Jimmy,
As Valentina pointed out, the code is expected to be
internationalized with external strings to permit localization but it is
not necessary to provide translations of these strings for specific
locales. If you intend to ship localized versions of your products that
incorporate Eclipse components, the community would appreciate your donation of
the translations of the strings that are associated with Eclipse
components. Of course, what you do with your own "value added" application
code is an internal matter.
The multi-language situation isn't much of an issue
for user interface components (Java or browser-based) because each
user can configure their own preferred locale. When the database needs to
store strings that are entered and displayed in a variety of languages, the
information can stored as UTF8 strings. You could have cases
where some users might not be able to view some of the stored information
because their preferred language doesn't support the proper characters.
Web browsers deal with this fairly effectively, but that doesn't really help
very much. I don't find it very useful when I see a properly
rendered page covered with symbols that I don't understand.
Regards,
Don
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it. From:
cosmos-dev-bounces@xxxxxxxxxxx [mailto:cosmos-dev-bounces@xxxxxxxxxxx] On
Behalf Of Mohsin, Jimmy
Sent: Friday, August 17, 2007 2:36 PM To: Cosmos Dev Subject: [cosmos-dev] Globalization considerations for the COSMOS DC Hi
Valentina, Yes, I did mean
globalization support….. And my question was more so from the perspective
of the Management Domain / Broker / other non-corporate
components. Stated another way,
what are the implementation implications for the non-corporate components? Is it
as simple as isolating all messages/labels such that multiple languages may be
supported further down the line? Or is there more to it than
that? Another convoluted
slant on the situation is this: what about a single COSMOS DC based solution
supporting a MUTLI-country deployment at a SINGLE enterprise customer
site? In that case, do we say this is up to the corporate implementation
to deal with? Thanks, Jimmy
Mohsin +1-609-635-1703 From:
cosmos-dev-bounces@xxxxxxxxxxx [mailto:cosmos-dev-bounces@xxxxxxxxxxx] On Behalf Of Valentina Popescu
|