LATIN2->UTF8 conversation with dblink

Hi,

The situation:
We've got two machines. The source database (DB) is running on an RHEL
5.x machine
with PSQL 8.1.11. The destination DB is running on SuSE 11.0 with PSQL 8.3.x.
The mechines are relative far away each other and there is a 2Mbps WAN
line between them.

The DB is the same except the character coding. Source is LATIN2 and
the target DB is UTF8.
We wrote a trigger to copy the data from source to target with dblink.
The problem is the
different DB character coding! PGSQL complains about wrong byte order.
It is trivial.

If the trigger is interesting I can copy here, of course.

What could be the solution? Of course I can't change the default
machine char code, easily.

TIA,
Ruzsi

Ps.: I've got an other question about our trigger making dblink
"permanent" but the char coding
is the most interesting for us.