Max Khon wrote:
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.
That hotfix didn't allow reading a file, so disabling the non-working file operations would have been better.
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.
While we removed non-unicode builds for win32 a long time ago, I'm not opposed to supporting it in general. If you contribute some working code (which would either mean adding a utf handling portion for non-unicode in utffile or disable unicode file operations throughout the app), you're welcome.
Regards, Andreas
---------------------------(end of broadcast)--------------------------- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
