[bt-devel] problem

[Martin Gruner]

I have 2.2.0
Configure has no --disable-unicode or similar argument.
Now what to do?

Martin

On Mittwoch,  8. November 2000 20:49, you wrote:
> Hm, I do also have a normal build of Qt.
> For me it works.
> I'm using 2.2.1.
> --Joachim
>
> > Hi!
> >
> > maybe you should change it, because i just did a normal build like many
> > other people would do also. So the error would be there also.
> >
> > Martin
> >
> > On Mittwoch,  8. November 2000 17:10, you wrote:
> > > Hi!
> > >
> > > Probably it's a problem with the i18n and unicode support of Qt. We use
> > > often the (const char*) operator of QString, maybe you have disabled
> > > uncicode in Qt?
> > >
> > > I'm not so sure if the merge of Sword and e-sword would make us guving
> > > up the port. AFAIK e-swords interface is like swords, so a port would
> > > be useful.
> > >
> > > --Joachim
> > >
> > > > Hi,
> > > >
> > > > now I found out why sword didn't work. It works now, so it can't be a
> > > > reason anymore.
> > > > The "umlaut" problem is still here. Why could it be?
> > > > (I do not use the latest qt [2.2.0], i have the one before, but IMO
> > > > that can't be the issue)
> > > >
> > > > If e-sword and sword merge, we would'nt need to port. e-sword is good
> > > > enough.
> > > >
> > > > Martin