On 2008.04.17, Rajesh Nair [EMAIL PROTECTED] wrote:
Here are the steps to replicate the problem
This is great, thanks!
1. you need a table with some multibyte characters in it.
You can do this either by
1.1.1 create table multibytetest (value nvarchar(200))
I just came across this
On 2008.04.17, Dossy Shiobara [EMAIL PROTECTED] wrote:
1.1.2 Pasting some Chinese characters via SQL Server Management
Studio Express
I used this, which I hope is equivalent to your Java program:
INSERT INTO multibytetest (value)
SELECT CHAR(230) + CHAR(144) + CHAR(156)
Darren,
The Content-Type is set to *text/html; charset=utf-8*.
Though the way I have done is
/*ns_set put [ns_conn outputheaders] Content-Type text/html;
charset=utf-8
*/I tried the meta tag equivalent too but no luck!
/*
*/-- Rajesh Nair/*
*/
Darren Ferguson wrote:
I had similar issues and
Found the problem cause and the solution
Firing the following mysql command lets me get the right result from mysql
/*set character_set_results = NULL
*/That is after firing use fresh /*
** set sql1 set character_set_results = NULL;
ns_db exec $db $sql1
*/
This is what mysql JDBC driver
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
On Thu, Apr 3, 2008 at 4:14 PM, Cynthia Kiser [EMAIL PROTECTED] wrote:
H 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 never occurred to me to try
On 04/04/2008, at 8:44 AM, Cynthia Kiser wrote:
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'?
Tcl lib has a
I echo Bas here. The only issue I've ever had is when writing to or reading
from files. You have to specify the encoding.
Jade
On Thu, Apr 3, 2008 at 3:14 PM, Cynthia Kiser [EMAIL PROTECTED]
wrote:
On Apr 2, 2008, at 5:42 PM, Bas Scheffers wrote:
The only issues I ever faced was (CSV)
Some questions to help us, and maybe give you some hints as to what
might be wrong.
How did you determine the fact that the value isn't a correct Tcl
string?
What encoding is the database in? (UTF-8?) Are you 100% sure the data
in the database is actually correct?
I wouldn't think you
Just to back up what Bas said, AOLserver has been, and probably still is,
light years ahead of most systems when handling encoding issues.
Tcl is essentially UTF-8, which is multi-byte. But there are so many issues
involved, you have to become something of an expert. The good news is that
My own special recipe is to not worry about it! :)
If you have a green-fields project with no existing database, all you
do is:
- Make sure the database is UTF-8
- Set the encoding to UTF-8 for any page returned to the client. (if
you have a form on a page and the page was set to UTF-8,
11 matches
Mail list logo
