W3C home > Mailing lists > Public > www-international@w3.org > April to June 1999

Re: [nelocsig] Internationalization--the next generation

From: Suzanne Topping <stopping@rochester.rr.com>
Date: Fri, 28 May 1999 15:58:58 -0400
Message-ID: <02bd01bea944$86d30840$a11d5d18@fwbm8.rochester.rr.com>
To: "Andre Pellet" <apellet@m2ltd.com>, "nelocsig" <nelocsig@egroups.com>, "i18n" <i18n-prog@acoin.com>, "swI18N" <sw-i18n-l10n@topica.com>, "Unicode List" <unicode@unicode.org>, "w3c" <www-international@w3.org>
>
>We envision a central code engine that is "smart" enough to serve localized
>interfaces, features, etc. as needed.  This provides the flexibility, with
>the controlled code-maintenance.  It would be possible then that certain
>features may not even be available for certain regions...
>

COOL!!! Do you mean that the code base would not be modified or customized,
that
there would be one code base for all the loclized UIs? That's what it sounds
like, and
is exactly what I was picturing.

Interesting concept.

Just out of curiosity, why did your client decide to invest in this?

>One of the problems with such a system is that it needs a robust help
system
>(data driven), that can also change to meet the "locale" reguirements.


Hmmmn, I'll bet there are lots of similar implications... printed
documentation for example. Lets say that for one locale a function is
accessed through a button, and for another locale the same function is
accessed through a list box. The documentation would have to be pretty
significantly modified during localization.

Of course, many people want to get rid of documentation anyway...
Received on Friday, 28 May 1999 16:01:41 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 19:16:54 GMT