On Wednesday 08 April 2009 12:40:16 pm David Naylor wrote:
> Yes, I think it is more important to get Qt 4.5 into ports ASAP then waste
> time fixing this problem. This problem could be fixed later?
>
> Please see the attached patch that fixes devel/qt4-corelib (and thus Qt4.5
> and libiconv). Th
On Tuesday 07 April 2009 21:41:28 David Johnson wrote:
> > SOLUTION 2:
> > ...
> > The attached files restore the behaviour of the previous code. This
> > probably will result in a performance loss (but remain par with Qt4.4.3).
> > Since the changes are isolated to those two files and the API has
> SOLUTION 1:
> Disable libiconv support altogether. This, I believe, is a viable solution
> since Windows does not have iconv and we should be using whatever fallback
> it does. This should result in no loss of functionality.
This is what I am doing for non-port builds of 4.5.0. It's also what'
On Tuesday 07 April 2009 07:25:16 David Johnson wrote:
> I played around with this, rebuilding libiconv after gettext, but to no
> effect. Oh well, it was worth a shot...
I've managed to get Qt 4.5 to behave well with libiconv. It was a bit of a
cheat though. There is also another solution.
On Monday 06 April 2009 10:25:16 pm David Johnson wrote:
> I'm attaching a screenshot I just made, to show the behavior.
I always forget to attach my attachments :-(
--
David Johnson
<>___
kde-freebsd mailing list
kde-freebsd@kde.org
https://mail.kde.o
On Monday 06 April 2009 10:54:06 am David Johnson wrote:
> On Monday 06 April 2009 01:06:11 am Adriaan de Groot wrote:
> > So up until recently it did work. You don't say what the nature of
> > "behave" is though -- does it not compile? Not run?
>
> To repeat David Naylor, it builds fine, but all g
On Monday 06 April 2009 01:06:11 am Adriaan de Groot wrote:
> So up until recently it did work. You don't say what the nature of "behave"
> is though -- does it not compile? Not run?
To repeat David Naylor, it builds fine, but all glyphs at runtime are square
boxes.
> > > So which one is impleme
On Monday 06 April 2009 10:06:11 Adriaan de Groot wrote:
> On Thursday 02 April 2009 10:46:24 pm David Naylor wrote:
> > > > I've been trying to get Qt4.5 to behave properly with libiconv and it
> > > > just doesn't. My best understanding is that, under linux, glibc
> > > > provides all the iconv
On Thursday 02 April 2009 10:46:24 pm David Naylor wrote:
> > > I've been trying to get Qt4.5 to behave properly with libiconv and it
> > > just doesn't. My best understanding is that, under linux, glibc
> > > provides all the iconv functionality and that, somehow, libiconv and
> > > glibc differ
On Friday 03 April 2009 20:32:30 David Johnson wrote:
> On Friday 03 April 2009 11:02:20 am David Naylor wrote:
> > What is the course of action from here? Complain to Qt Software, hope
> > someone sorts it out or ignore the problem? Oh and how does one file a
> > bug with Qt Software?
>
> A new
On Friday 03 April 2009 11:02:20 am David Naylor wrote:
> What is the course of action from here? Complain to Qt Software, hope
> someone sorts it out or ignore the problem? Oh and how does one file a bug
> with Qt Software?
A new bug reporting system is being setup, as Qt transitions to a more
On Friday 03 April 2009 18:08:06 David Johnson wrote:
> On Thursday 02 April 2009 01:46:24 pm David Naylor wrote:
> > > I configure Qt with --no-iconv for exactly this reason.
> >
> > Is there any functionality lost? Do you see *any* square blocks after
> > doing this?
>
> I'm not seeing any squar
On Thursday 02 April 2009 01:46:24 pm David Naylor wrote:
> > I configure Qt with --no-iconv for exactly this reason.
>
> Is there any functionality lost? Do you see *any* square blocks after
> doing this?
I'm not seeing any squares. But I don't have a lot of documents in non-latin1
codecs.
--
On Thursday 02 April 2009 21:10:04 David Johnson wrote:
> On Thursday 02 April 2009 07:00:38 am David Naylor wrote:
> > Hi,
> >
> > I've been trying to get Qt4.5 to behave properly with libiconv and it
> > just doesn't. My best understanding is that, under linux, glibc provides
> > all the iconv f
On Thursday 02 April 2009 07:00:38 am David Naylor wrote:
> Hi,
>
> I've been trying to get Qt4.5 to behave properly with libiconv and it just
> doesn't. My best understanding is that, under linux, glibc provides all
> the iconv functionality and that, somehow, libiconv and glibc differ in
> their
Hi,
I've been trying to get Qt4.5 to behave properly with libiconv and it just
doesn't. My best understanding is that, under linux, glibc provides all the
iconv functionality and that, somehow, libiconv and glibc differ in their
implementation and thus it breaks Qt (or Qt handles them differen
16 matches
Mail list logo