Hi Andreas.
It thinks that it will be seen variously from now.
Conditions are explained.
1) pgAdmin3-1.0.1 Release + wxWindows-20031010+patch
This works well.
2) pgAdmin3-1.1.0 Developer + wxWindows-20031010+patch
This can't do input of Japanese in IME.!!
It can't be used.
It seemed to call more problem, and a problem became very difficult.
regards,
Hiroshi Saito
----- Original Message -----
From: "Andreas Pflug" <[EMAIL PROTECTED]>
To: "Hiroshi Saito" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Friday, October 17, 2003 2:03 AM
Subject: Re: [pgadmin-hackers] Font debugging code
> Hiroshi Saito wrote:
>
> >Hi Andreas.
> >
> >It is FreeBSD.
> >2003-10-16 23:57:25 INFO : Using fontmetrics 12/13, 10 Point
> >2003-10-16 23:57:25 INFO : Native Description 'Sans 10'
> >2003-10-16 23:57:25 INFO : Draw size of 'M': w=12, h=13, descent 0, external lead
> >0.
> >2003-10-16 23:57:25 INFO : Draw size of 'g': w=12, h=13, descent 0, external lead
> >0.
> >2003-10-16 23:57:25 INFO : Draw size of 'Mg': w=24, h=13, descent 0, external
> >
> >
> Very strange, with of g is the same as M, while sans shouldn't be fixed
> font...
> However, calculated font metrics match the calculated sizes, so display
> should be ok.
>
> >However,
> >It is wrong in something.:-(
> >This occurs only in today's cvs.
> >
> >bsd5% LANG=ja_JP.UTF8 src/pgadmin3
> >(process:80785): Gdk-WARNING **: locale not supported by C library
> >(process:80785): Gtk-WARNING **: Locale not supported by C library.
> > Using the fallback 'C' locale.
> >...
> >connecting to ...crash!
> >
> >
>
> Did we have any locale changes in the last days I don't know of?
> This is a crash while trying to log an sql statement. Maybe you can
> catch it in the debugger, to inspect why it crashes?
>
> Regards,
> Andreas
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if your
> joining column's datatypes do not match
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?
http://archives.postgresql.org
