Re: Encoding conversion problem

> > ...
> > If I save characters outside the range sup****ted by IBM-850 (i.e. the
> > euro currency character EURO) then I read garbage...
>
> Yes, the Euro symbol is not part of the encodings, so your database
> can't contain it.
I've found a strange thing: C and COBOL application can write and read
(using embedded SQL) characters outside the accepted range without
problems... So the database can contain those characters without
loosing any information, but I can't understand how...

> If you need it, you would have to change the databases
> encoding (ISO-8859-15 includes the Euro symbol).
> Otherwise, you have to take care not to try to write unsup****ted
> character into string/character fields.
>
> One solution could be to parse all strings and replace the symbol with
> the shorthand "EUR", but it might not be acceptable to your client.
Actually the EURO character is just an example, I have more complex
strings to handle (and I can't change the encoding of the database).
If my problem has no solution at all then I'd like to understand why
other languages don't have this problem...

Thanks,
Andrea