Adriano dos Santos Fernandes wrote:

>
> Why choose one side if all can be satisfied?
> Some people are inteligent enough to set the character set of your
> fields. ;-)
>

One of the assumptions in this discussion is that a future ODS will
store exactly one character set, probably ODS-8. Fields and connections
can specify other character sets and data will be converted on input and
output to the specified representation. At the moment, we're facing
an m * n problem of character sets and collations, which shows every
sign of getting worse. Choosing one character set for storage reduces
that to an m + n problem - m = supported character sets, n = collations.


Since the database on disk uses the operating system rules for data
representation (including endian-ness) perhaps a compromise on the UTF-8
UTF-16 issue would be to use UTF-16 for storage and UTF-8 for transport.


Regards,


Ann