On 3 Aug 2009, at 20:32, Andreas Kalsch wrote:
> Problem: Users will enter _any_ characters in my application and an
> error really doesn't help in this case.
I think the real problem is: Where do you lose the original encoding
the users input their data with? If you specify that encoding on the
connection and send it to a database that can handle UTF-8 then you
shouldn't be getting any conversion problems in the first place.
Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll see there is no forest.
!DSPAM:737,4a77688810131526383955!