### FreeBSD Notes

First, there is a limitation in the contents which can move by the fundamental version.

FreeBSD Version 4.x

The use of UNICODE can't be expected with Version 4.x. libc lacks the wchar wide character routines required. It is difficult work to fix this. This problem will be seen when building wxWindows. The following message will be output.
...
implicit declaration of function `inttowupper (...) '
...
In this case, build wxWindows without UNICODE support - wxWindows may be configured with the following command.
./configure --disable-shared --enable-static --with-gtk --enable-gtk2

FreeBSD Version 5.1 higher

UNICODE is supported, and pgAdmin3 should work well. There is a UTF-8 locales support package in misc of the ports collection.
Be careful in the establishment of locale. WxWindows has the locale check of the language with dot.
For example, when it is LANG=ja_JP.UTF-8
/usr/share/locale
ex.) locheck.c
#include <stdlib.h>
#include <locale.h>
int main(int argc,char *argv[])
{
if (argc > 1)
printf("setlocale=%s\n",setlocale(LC_ALL,argv[1]));
return 0;
}
cc -o locheck locheck.c
#FreeBSD running...
locheck ja_JP
(null) <--- bad locale.
ln -s /usr/share/locale/ja_JP.UTF-8 /usr/share/locale/ja_JP
locheck ja_JP
ja_JP <--- it is OK.
wxWindows may be configured with the following command.
../configure --disable-shared --enable-static --enable-unicode --with-gtk --enable-gtk2 --enable-debug
Configured wxWindows 2.5.0 for `i386-unknown-freebsd5.1'
Which GUI toolkit should wxWindows use? GTK
Should wxWindows be compiled in debug mode? yes
Should wxWindows be linked as a shared library? no
Should wxWindows be compiled in Unicode mode? yes
What level of wxWindows compatibility should be enabled?
wxWindows 2.0 no
wxWindows 2.2 no
wxWindows 2.4 yes
Which libraries should wxWindows use?
jpeg sys
png sys
regex sys
tiff sys
zlib sys
odbc no