From: Mark Davis (firstname.lastname@example.org)
Date: Tue Oct 11 2005 - 19:14:12 CST
Definitions vary: we go by something like:
1. A localized product is one that is adapted to meet the language,
cultural and other requirements of a specific target market (a "locale").
2. An internationalized software product is one that can be localized to
any single locale without code changes.
3. A globalized software product is one that is internationalized, and
also supports multiple data locales at runtime. It may also support a
runtime choice among UI locales.
One thing that is very important to make clear is the distinction
between a program that can handle localized *data* vs one that *is
translated* -- that is, has a localized UI. Many people mix these up,
and they have different implications.
Eduardo Mendez wrote:
>Mark Davis said:
>>I'm preparing a presentation for the next Unicode conference in March, and
>>have been thinking about doing one on the pitfalls that people stumble into
>>when using Unicode in globalizing software.
>>I have the following initial draft list, and would like to collect others. If you
>>have any suggestions for additions or improvements, I would appreciate them.
>If I can help. I am no specialist. But I am a consultant for top management.
>I think the pitfalls they may stumble into is to make their boss/client to
>I explained we work on a new sign. I was helped over that. We have now
>a problem: to explain what we propose. I read a few things and now your
>page. I am confuse. What you name "globalizing" is like "internationalizing"
>and "localizing"? I started a part on "multilingualizing" our proposistion.
>But is not "globalizing" more correct?
>I hope this helps, and you will help me.
This archive was generated by hypermail 2.1.5 : Tue Oct 11 2005 - 19:16:12 CST