> >> >> I think that text draw problem, not IBO core(or API) problem.
> >> >> This case become correct result with e.g. TMS unicode controls.
> >> >> It will be possible if unicode controls or ExtTextOutW API.. are

used.

> >> >
> >> >However, on VARCHAR it works just fine, so what's the deal here?
> >>
> >> Sorry, i have mistaken. The german umlaute are BMP in UCS2(ansi range).
> >> >Additional Information
> >>
> >> As far as i understanding in IB_components.pas,
> >> The ansi decoding is only string type. (Please see
> >SetAsString/GetAsString)
> >> The transliteraion of BLOB type may be necessity...
> >
> >But how do these characters for VARCHAR get displayed then? I have
> >a test table here, with two columns, one is the varchar and one is the
> >blob subtype text, I insert the same values in both. Varchar is displayed
> >just fine, while the blob isn't.
>
> if your environment as bellow,
>
> - V4.8.7
> - Using IB_Grid
> - UTF8 client connection
>
> I think that specification of IBO...

Are you telling this works for you? In both the varchar and blob?
(do note, I'm using TIBOQuery, not a IB_Grid)

I seems I'm using IBO 4.8.4 here and I cannot download a newer
version because my subscription has expired? I'm not sure if 4.8.7
was available before it expired.


Martijn Tonies
Database Workbench - tool for InterBase, Firebird, MySQL, NexusDB, Sybase
SQL Anywhere, Oracle & MS SQL Server
Upscene Productions
http://www.upscene.com
My thoughts:
http://blog.upscene.com/martijn/
Database development questions? Check the forum!
http://www.databasedevelopmentforum.com