Serguei A. Mokhov wrote:
>Indeed, no one has forbidden extended-ASCII chars :) Though these would be
>interpreted differntly. My 256 char ASCII table is different from yours
>presentation-wise. But you can't control it uniformly unless you
>explicitly tell how to enterpret. I wanna see my Cyrillic chars and not
>the diacritics of Latin chars, for example. An Indian friedn of mind would
>like to see their Hindi chars there instead, so... You are lucky because
>your accented chars are the deault representation.
>
:-)
>There could potentially
>be a need to tell the UI which ASCII it is, not sure how it is.
>
*NO*, we discussed this.
Data encoding is unknown if SQL_ASCII is selected, so we have to leave
it up to the gui to display whatever it means. Hopefully it is what the
user expected (it probably will, if using the same language settings as
he used when inserting the data).
For other encodings, all 256 chars are well-known, so the server knows
how to recode to UNICODE, and we know how to display.
Regards,
Andreas
