tjelvar eriksson wrote:

> Possible solution:
> create db with utf8
> on char/varchar, CHARACTER SET WIN1252 COLLATE PXW_SWEDFIN
>
> fb reports back what seems like utf8 to client.
> sorting is CI and localized. Tested with flamerobin and over odbc/ms-
> access.

This would limit your data to the character set WIN1252, but I assume
you're aware of that and that you've concluded that it's ok.

You will get a lot of transliteration between fixed-width 8 bit WIN1252
and variable-width 1-6 byte UTF8 when storing and retrieving data
into/from that column. Might be a performance issue - only you can judge.

Kjell
--
--------------------------------------
Kjell Rilbe
DataDIA AB
E-post: kjell@...
Telefon: 08-761 06 55
Mobil: 0733-44 24 64