Bug #949
closed
Non asci characters in data input mishandled
Added by Gabriel Farrell over 21 years ago.
Updated over 19 years ago.
Description
There are a number of problems in the system when data is loaded containing non
asci characters eg. è,ù,ö
1) The database throws errors when queried using a string containing one these
characters.
2) XML is transformations fail on XML containing these values.
This is going to take some investigation to overcome. I hate these kind of
problems.
Shouldn't there be a simple setup option for character set. I used to use
simple ASCII on my pine email and had all these problems, so switched to the
ISO-8859-1 character set and it all works fine.
The database doesn't have a problem with the characters ... it has a problem
when data contains single or double quotes as part of a string.
This should be fixable by filtering out these before writing to the database and
reconsituting them when reading from the database.
No longer blocks bug956 since the single quotes and other postgres special
characters $ and ^ and escaped before going into the database.
Leaving the bug open as I need to impliment the removal of the escape character
upon read the data from the database (hoped this would happen automatically) and
the xml problem with special characters remains.
characters seem to be handled well now, with UNICODE db. Leaving this open, as
I'm not sure if this is handled across the board for dealing with SQL that has '
in it.
UTF-8 Unicode takes care of this
changed from components that are to be deleted to "misc" so that bugs don't get
deleted with component. Sorry for all the email.
Original Bugzilla ID was 949
Also available in: Atom
PDF