Not correct multibyte-character in remote

[casti]

how to correctly display the multibyte characters in remote database?

Below is the information:

//consolidated db
select property('defaultCollation') = 936ZHO
select property('Charset') = cp936
select property('language')= us_english

select db_property('charset')=utf8
select db_property('collation') =utf8
SELECT DB_PROPERTY( 'MultiByteCharSet' ) = ON

select connection_property('charset') = utf8
select connection_property('language') = us_english

//remote db

select property('defaultCollation') = 1252LATIN1
select property('charset') = cp1252
select property('language') = us_english

select db_property('charset') = utf8
select db_property('collation') = UTF8
SELECT DB_PROPERTY( 'MultiByteCharSet' )= ON

select connection_property('charset') = utf8
select connection_property('language') = us_english

//Connection string
//consolidated
-c "eng=maindb;uid=dba;pwd=sql;charset=utf8"

//remote
-c "eng=maindb;uid=dba;pwd=sql;charset=utf8"

The display characters in remote db is not correct or garbage.

Please help on how correctly display the multibyte characters.

Thanks in advance.

[Unknown]

Ah yes. Mixed character sets and replication!
*Always a great way to confuse yourself. *
:'-( great fun that stuff )-':

I believe your issue is that the two message agents
involved are working from different assumptions.
One is generating messages with SQL using an
assumption of CP1252 and the other is interpreting
those same messages assuming they were written
using CP936. [and vice-versa]

If all else fails creating all databases to use the same
character and disabling charset conversion (by setting
'...CS=none;...' or to the charset of the database)
may avoid all possible conversion issue.

"casti" <w2c...@gmail.com> wrote in message
news:ee314be8-626c-4976...@g1g2000pra.googlegroups.com...

[casti]

On Aug 7, 10:04 pm, "Nick Elson [Sybase iAnywhere]"

<@nick@.@elson@@sybase@.@com@> wrote:
>   Ah yes.  Mixed character sets and replication!
>   *Always a great way to confuse yourself. *
>      :'-( great fun that stuff )-':
>
> I believe your issue is that the two message agents
> involved are working from different assumptions.
> One is generating messages with SQL using an
> assumption of CP1252 and the other is interpreting
> those same messages assuming they were written
> using CP936. [and vice-versa]
>
> If all else fails creating all databases to use the same
> character and disabling charset conversion (by setting
> '...CS=none;...' or to the charset of the database)
> may avoid all possible conversion issue.
>

> "casti" <w2ca...@gmail.com> wrote in message

> > Thanks in advance.- Hide quoted text -
>
> - Show quoted text -

This suggestion works!!!

Thank you very much