Re: [ADMIN] Bad character data

2004-05-04 Thread douglas morrison
EMAIL PROTECTED] On Behalf Of douglas morrison Sent: Monday, May 03, 2004 7:11 PM To: Noah Davis Cc: [EMAIL PROTECTED] Subject: Re: [ADMIN] Bad character data no problem noah, been there inheriting bad data, suXX0r. wish i could be of more help. if all else fails look at the translate() functi

Re: [ADMIN] Bad character data

2004-05-04 Thread Noah Davis
EMAIL PROTECTED] On Behalf Of douglas morrison Sent: Monday, May 03, 2004 7:11 PM To: Noah Davis Cc: [EMAIL PROTECTED] Subject: Re: [ADMIN] Bad character data no problem noah, been there inheriting bad data, suXX0r. wish i could be of more help. if all else fails look at the translate() function to re

Re: [ADMIN] Bad character data

2004-05-03 Thread douglas morrison
The lack of responses is prolly because this sort of thing is usually handled by the client... The client for input should be stripping/converting to ASCII/unicode whichever chars are unwanted and notifying the user if anything is removed/unusable. The client for display should then be able to

Re: [ADMIN] Bad character data

2004-05-03 Thread Noah Davis
cters. Not sure. -Original Message- From: douglas morrison [mailto:[EMAIL PROTECTED] Sent: Monday, May 03, 2004 4:38 PM To: Noah Davis Cc: [EMAIL PROTECTED] Subject: Re: [ADMIN] Bad character data The lack of responses is prolly because this sort of thing is usually handled by the client... The c

[ADMIN] Bad character data

2004-05-03 Thread Noah Davis
I posted this to the pgsql general list, but alas, I did not get any responses. Perhaps someone here could be of assistance? I have a database with some bad characters in it -- some users had entered MS Word smart quotes, em dashes, foreign characters, and they look like gibberish coming out of th