Dimitry Sibiryakov wrote:

>> I totally fail to see why the client library knows nothing about this? Isn't
>> it the client library that is the "glue" between the network protocol and
>> the client application? Yes, it is, so it should present properly encoded
>> character strings to the client application.
>
> It is "glue", right, but network protocol does not include actual
> data length in characters, only in bytes.

But you *do* get info about charset id, right? And from that you
(fbclient) can determine the actual field size in characters using the
method Milan described. From that, you would have to be able to parse
the data in the encoding used to find the byte size of the actual data.
This last step would probably require a lot of "knowledge" in fbclient
of all possible character encodings, which I expect would bloat that dll
a bit more than anyone would like. Or would it?

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


[Non-text portions of this message have been removed]