Subject | Re: [IBO] Again: Unicode |
---|---|
Author | mircostange |
Post date | 2004-10-22T17:06:49Z |
--- In IBObjects@yahoogroups.com, Helen Borrie <helebor@t...> wrote:
moving to a different record and back "corrupts" the data.
software that supports English/US, European languages, China, Japan.
I will however try to understand whether I could simply switch
between different databases instead.
I will continue to work on this. Anyone contributing to this issue
is welcome. I would be pleased to get replies to the detail
questions I will come up with.
A side question: is there a disadvantage of using the
TDataset/IBOQuery combination with normal Delphi controls as opposed
to the IB_Query/IB_Dataset combination? Slower? fewer features?
Restricted?
> At 02:26 PM 22/10/2004 +0000, you wrote:get
>
>
> >I am still in the situation of finding out, whether it is possible
> >to migrate my existing Delphi/IBO application to unicode support.
> >Some information has been here in the group, but I simply don't
> >anything to work.UNICODE_FSS
> >
> >I created a sample database with default charset none and created
> >the following table:
> >
> >CREATE TABLE PERSON
> >(
> > PERSONID INTEGER NOT NULL,
> > FIRSTNAME CHAR( 40) CHARACTER SET
> >NOT NULL COLLATE UNICODE_FSS,UNICODE_FSS
> > LASTNAME CHAR( 40) CHARACTER SET
> >NOT NULL COLLATE UNICODE_FSS,doesn't
> > GENDER CHAR( 10) NOT NULL COLLATE NONE,
> > AGE SMALLINT,
> > CONSTRAINT PK_PERSON PRIMARY KEY (PERSONID)
> >);
> >
> >firstName and lastName should support unicode, while gender
> >need this.generated
> >
> >I then tried to write a small Delphi app to connect to the db as
> >follows:
> >-created an IB_Connection
> >-created an IB_Query with "select * from person" and auto-
> >update sqljust
> >-created an IB_Datasource, bound to IB_Query
> >-dropped an IB_Grid to show the data
> >
> >Result: everything is fine, but entering unicode (japanese,
> >cyrillic, ...) results in "???"
> >It seems, the IBO controls don't support Unicode, because the
> >default Delphi controls don't.
> >
> >I then tried the following:
> >- use IBOQuery with same select
> >- use standard Delphi TDataset
> >- bind standard Delphi grid (don't expect this to show Unicode
> >for navigation)edit
> >- download, install and bind TNT Edit box with unicode support
> >- set font to Tahoma (otherwise it won't show properly)
> >
> >Result: everything is find, I can enter unicode chars into the
> >box, moving to the next record and back shows "???" .... arghh..it
> >
> >Has anyone got anything to run with Unicode+Firebird+IBObjects?
> >What am I doing wrong here? What could I do or contribute to make
> >work? Who can help? Please....enter
>
> Notice, if the TNT edit is displaying "correct" characters as you
> them, then Delphi is capable of interpreting them.The TNT displays them correctly while entering them. Only after
>
moving to a different record and back "corrupts" the data.
> Don't get into the complication of wide strings unless you findyou
> must.It seems I must. The requirements for the new version are: one
software that supports English/US, European languages, China, Japan.
I will however try to understand whether I could simply switch
between different databases instead.
I will continue to work on this. Anyone contributing to this issue
is welcome. I would be pleased to get replies to the detail
questions I will come up with.
A side question: is there a disadvantage of using the
TDataset/IBOQuery combination with normal Delphi controls as opposed
to the IB_Query/IB_Dataset combination? Slower? fewer features?
Restricted?