Hi Francis,
Unicode is a character encoding standard, and thus has no impact on the
other data types you mention... except...
Some of these data "types" contain identifiers that could be defined using
text fields. For example, a "currency" type will have a float and a
currency type (US dollars, for example) and the currency type could be
an enumerated text string (it should be from the ISO standard for currency
identifiers, if at all possible). With that (unimportant) aside, you're
correct. Unicode is not internationalization.
The other types *ARE* locale affected, when it comes to human readable
display and such human readable formatting works best using Unicode.
Best Regards,
Addison
===========================================================
Addison P. Phillips Principal Consultant
Inter-Locale LLC http://www.inter-locale.com
Los Gatos, CA, USA mailto:addison@inter-locale.com
+1 408.210.3569 (mobile) +1 408.904.4762 (fax)
===========================================================
Globalization Engineering & Consulting Services
On Mon, 21 Aug 2000, Magda Danish (Unicode) wrote:
>
>
> -----Original Message-----
> From: Hsu, Francis (GEP) [mailto:hsufr@exchange.ml.com]
> Sent: Monday, August 21, 2000 8:29 AM
> To: 'info@unicode.org'
> Subject: Impact of Unicode
>
>
> Having read the Unicode standard, it seems that it only impacts 'Text'
> fields.
> Is this a correct assessment?
>
> In particular the size and use of the following DATA TYPES does NOT have
> to change on ANY platform:
>
> 1) Integer
> 2) Float
> 3) Date and/or Time
> 4) Boolean
> 5) Currency or Money
> 6) Audio, Video or graphics (bit strings)
> 7) ..
>
> Sincerely,
>
> Francis Hsu
>
>
This archive was generated by hypermail 2.1.2 : Tue Jul 10 2001 - 17:21:07 EDT