On Apr 2, 2008, at 5:42 PM, Bas Scheffers wrote:
The only issues I ever faced was (CSV) file uploads, where the data needed to be extracted and put into the database. This could contain any encoding without me knowing. In practice it only ever contained stupid Windows encoding, so I assumed that to be the case and used Tcl's convert functions.
Hmmmm CSV + "stupid Windows encoding". Bas perhaps you have just what I need for a character set issue. I have a data file - actually delimited by upsidedown exclamation points, not commas. It comes from a Windows box - apparently with the Windows 1252 character set. I am trying to load that data into Oracle. I was trying to use SQLLDR to do that but am having debugging issues. I *think* I have the correct character set info and octal representation for ¡. But something is funky.
It never occurred to me to try parsing this with Tcl instead. Is there an AOLserver or straight Tcl module I should be using to parse pseudo-CSV? Or is the answer keep it simple and just read lines and split on ¡ with 'split'?
-- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
