Codepage ? Differences between character editor and GUI edit

Posted by Admin on 10-Jan-2011 05:03

Hello,

I have a problem with character conversions.

Maybe it's a very simple question but I didn't find any answer.

My database is running under unix.

When I work with both Windows / Unix clients, special characters are displayed correctly but once I go through the Windows GUI editor, it shows unreadable squares etc...

Characters inserted vi GUI client are also unreadable under Character clients.

I checked the -cpinternal and -cpstream parameters but they are all set as ISO8859-1.

The codepage configuration doesn't seems to be forced, so all parameters should be by default.

I started the db with -cpinternal and -cpstream to ISO8859-1.

I'm running clients with these parameters too.

The "Session info" of Windows GUI client also display these parameters with "ISO8859-1" value.

Does anyone know how I could solve this problem?

Regards.

All Replies

Posted by Admin on 10-Jan-2011 08:16

Hello,

After some tests,

I added the degree sign " ° "  to my database via character client.

This symbol corresponds to

IBM850 : 0xF8

ISO8859-1 : 0xB0.

I ran the DBCODEPAGE function which returns ISO8859-1 to be my database codepage.

So, normally, the " ° " should have the 0xB0 value

but I get 0xF8 value which is from IBM850 codepage.

If I read it via Windows GUI, it displays " ø " character which is in fact the 0xF8 value in ISO-8859-1.

I tried to force -cp* parameters to ISO8859-1 but it didn't change anything.

Any idea?

Regards.

Posted by Admin on 11-Jan-2011 07:38

Still investigating...

Display session:cpinternal -> ISO8859-1

Display session:cpterm -> ISO8859-1

Display session:cpstream -> ISO8859-1

Display session:charset -> ISO8859-1

Display ASC("°"). -> 248 (= F8 = IBM850 value).

Display CHR(248) -> "°"

Via the GUI, the first line returns 176 which is the good value of ISO8859-1.

Could it be due to a PROTERMCAP config or something?

Posted by Admin on 11-Jan-2011 08:47

Ok this was a terminal config problem.

This thread is closed