I am watching argument now for busyness.
----- Original Message -----
From: "Max Khon" <fjoe(at)samodelkin(dot)net>
> > Which condenses down to "utffile.cpp is not non-unicode compatible".
> > I've added a #error accordingly. Until utffile is thoroughly reworked
> > for non-unicode, compiling pgadmin in unicode mode is *required*.
> You are correct. The patch I submitted is a workaround and was never supposed
> to fix the root of the problem. But it allows to run pgadmin3 1.2.0 on FreeBSD
> 4.x which lacks proper wchar_t support but is still widely used.
However, I think that your approach is right. Because, An environment had a limitation.
You are the result which becomes stable how and it thought whether it could be supplied.
Unicode edition will probably meet with the trouble with 4.x. I used special magic therefore.
> I removed non-Unicode support in FreeBSD port initially because of the
> problems you described, but the a few users asked me if it is possible to
> add it back.
There must be many users who use the version very much.
Again, your offer was right.:-)
In response to
pgadmin-hackers by date
|Next:||From: cvs||Date: 2005-02-24 15:30:51|
|Subject: CVS Commit by andreas: some Slony-I stuff|
|Previous:||From: Dave Page||Date: 2005-02-24 13:47:07|
|Subject: Re: cron: sh /usr/local/src/pgadmin3/pkg/src/build-tarball;sh /usr/local/src/pgadmin3/pkg/slackware/build-snapshot 91|