Subject | Re: Problem with TMemoField and ISO8859_1 charset blob field in RAD Studio XE / IBX |
---|---|
Author | ipai1 |
Post date | 2010-12-23T02:17:13Z |
Thanks again, Woody!
Looks like it's definitely a Delphi issue rather than a Firebird one. Setting the lc_type parameter to UTF8 (or anything else, for that matter) had no effect.
On further investigation, I managed to narrow the problem down to a TClientDataSet creating a TMemoField instead of a TWideMemoField. One would have thought that the TMemoField would be correct for non-unicode data, but the TIBQuery feeding the TClientDataset has a TWideMemoField and displays the data correctly.
I have reported this to Embarcadero at:
http://qc.embarcadero.com/wc/qcmain.aspx?d=90484
I am not sure whether this is an IBX or a ClientDataSet issue, but Firebird itself would appear not to be the culprit. Sorry to take up forum space with this one - the ball is now in Embarcadero's court.
Regards,
Alex.
Looks like it's definitely a Delphi issue rather than a Firebird one. Setting the lc_type parameter to UTF8 (or anything else, for that matter) had no effect.
On further investigation, I managed to narrow the problem down to a TClientDataSet creating a TMemoField instead of a TWideMemoField. One would have thought that the TMemoField would be correct for non-unicode data, but the TIBQuery feeding the TClientDataset has a TWideMemoField and displays the data correctly.
I have reported this to Embarcadero at:
http://qc.embarcadero.com/wc/qcmain.aspx?d=90484
I am not sure whether this is an IBX or a ClientDataSet issue, but Firebird itself would appear not to be the culprit. Sorry to take up forum space with this one - the ball is now in Embarcadero's court.
Regards,
Alex.
--- In firebird-support@yahoogroups.com, "Woody" <woody-tmw@...> wrote:
>
> From: "ipai1" <user001@...>
> > Thanks, Woody.
> >
> > I tried setting "LC_CTYPE=ISO8859_1" in the params property of the
> > TIBDatabase but it made no difference. That was the only vaguely relevant
> > param option I could find - is that what you meant?
> >
> > I haven't been able to find the relevant post from Peter Below. Still
> > looking...
>
> According to the post I read, the setting was something like this:
>
> lc_ctype=UTF8
>
> I don't think you actually have to specify the code name, just that it's
> unicode compatible. Here is the link to the post by Peter Below.
>
> http://codenewsfast.com/isapi/isapi.dll/article?id=0F2EB3F8&article=7278709
>
> Woody (TMW)
>