To: Dawn Friedland
Cc: [EMAIL PROTECTED]
Subject: Re: Japanese Charset
...
Say, do you want a little utility program in Java or C that will print
the hexadecimal values of the characters in a string? Basically, it
would be a command-line utility, so you would copy the text and then
paste
I was not aware that you were running VB.
In perl and PHP we have a function do do this for us.
in perl:
$qtext=$dbh-quote($text);
$dbh-execute(insert into mytable set myvariable = $qtext);
The above quote() function will put a \ in fronnt of all the special
characters listed in the manual.
gerald_clark wrote:
$qtext=$dbh-quote($text);
$dbh-execute(insert into mytable set myvariable = $qtext);
The above quote() function will put a \ in fronnt of all the special
characters listed in the manual.
These in clude '\ and the hex 00 character.
FWIW, before anyone copies and pastes
It is already quoted. That's the point.
Michael T. Babcock wrote:
gerald_clark wrote:
$qtext=$dbh-quote($text);
$dbh-execute(insert into mytable set myvariable = $qtext);
The above quote() function will put a \ in fronnt of all the special
characters listed in the manual.
These in
Joel Rees wrote:
If I compile MySQL using --with-charset=sjis , how will it handle the
Latin, Chinese, and Korean characters?
Multiple databases on multiple servers?
Try this one on for size:
CREATE TABLE Customers ( Name VARCHAR(100) );
Now ... if your customers have names in
PROTECTED]]
Sent: Sunday, September 29, 2002 7:24 PM
To: Dawn Friedland
Cc: [EMAIL PROTECTED]
Subject: Re: Japanese Charset
Dawn, I'm going to give in to the temptation to be pedantic.
Apologies in advance.
Kirk Samuelson wrote:
I've read lots of similar posts in the archives
, September 30, 2002 5:35 AM
To: Joel Rees
Cc: Dawn Friedland; [EMAIL PROTECTED]
Subject: Re: Japanese Charset
Joel Rees wrote:
If I compile MySQL using --with-charset=sjis , how will it
handle the
Latin, Chinese, and Korean characters?
Multiple databases on multiple servers
. Perhaps I am
missing something (likely).
Dawn
-Original Message-
From: Michael T. Babcock [mailto:[EMAIL PROTECTED]]
Sent: Monday, September 30, 2002 5:35 AM
To: Joel Rees
Cc: Dawn Friedland; [EMAIL PROTECTED]
Subject: Re: Japanese Charset
Joel Rees wrote:
If I compile MySQL
Friedland
[EMAIL PROTECTED]
-Original Message-
From: gerald_clark [mailto:[EMAIL PROTECTED]]
Sent: Monday, September 30, 2002 1:16 PM
To: Dawn Friedland
Cc: Michael T. Babcock; [EMAIL PROTECTED]
Subject: Re: Japanese Charset
Your webform application must call the appropriate
Multiple databases on multiple servers?
That is what I thought...which I assume means multiple machines (not an
option).
For future reference, MySQL can actually run multiple servers with
different configurations on a single machine in Linux. (*BSD and Mac OS
X, too, I think.) They are
I found a solution!!!
Hooray!
***Replace all backlashes with two backslashes.***
You probably want to consider whether you want to replace all quotes
with backslash-quote, as well. Backslashes in the English text would
only show up for something like file paths on MS OSses, but your
customer
Dawn, I'm going to give in to the temptation to be pedantic. Apologies
in advance.
Kirk Samuelson wrote:
I've read lots of similar posts in the archives at
http://lists.mysql.com/. Many suggestions to use a BLOB
instead of a
text field. But MySQL supports double-byte languages. Why
On Friday, September 27, 2002, at 01:12 PM, Michael T. Babcock wrote:
Dawn Friedland wrote:
Prior to my client requesting that I add Japanese content to the
content
tool database, I had zero experience with characters sets other than
Latin. I always used notepad to filter out any weird
, 2002 2:03 PM
To: Michael T. Babcock
Cc: [EMAIL PROTECTED]
Subject: Re: Japanese Charset
On Friday, September 27, 2002, at 01:12 PM, Michael T. Babcock wrote:
Dawn Friedland wrote:
Prior to my client requesting that I add Japanese content to the
content
tool database, I had zero
Lastly, I am convinced that this is a problem with MySQL.
I have some time again, let me try again. It's a tortuous tale, but bear
with me.
Background in brief:
Shift-JIS is a real pain in the neck to parse. When you look at a byte,
it's often impossible to tell whether you're looking at the
Joel Rees wrote:
Shift-JIS is a real pain in the neck to parse. When you look at a byte,
it's often impossible to tell whether you're looking at the first byte
or the second byte of the character.
Can I make a minor recommendation that doesn't help your current
situation at all?
Use UTF-8.
Dawn Friedland wrote:
Prior to my client requesting that I add Japanese content to the content
tool database, I had zero experience with characters sets other than
Latin. I always used notepad to filter out any weird MS Word formattings
and left the default as ANSI.
I had that problem a year
Here's an update on this issue: The problem is when copy/pasting
Japanese characters into MySQL, certain characters are being corrupted.
I've ruled out Word as the problem.
I've ruled out my content tool as the problem.
I've ruled out the ASP display page as the problem.
I've configured my
Here's a brief summary of where we are:
I trying to store Japanese text (Shift_Jis) in MySQL and view it from a
web page. The content is provided to me in Word format. I convert it to
plain text, copy/paste into a web form in an ASP-based CMS on a Windows
box. When viewed from a web page,
are using jsp, I can send you
the bean.
Best of luck
- Original Message -
From: Dawn Friedland [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: Joel Rees [EMAIL PROTECTED]; Shashank Tripathi [EMAIL PROTECTED]
Sent: Tuesday, September 24, 2002 4:54 PM
Subject: RE: Japanese Charset
Here's
Dawn,
Look at chapter 6.1.1.1 in the MySQL docs:
http://www.mysql.com/documentation/mysql/bychapter/manual_Reference.html#Literals
Practically the first odd thing mentioned is escape sequences. Keep in
mind that the ASCII code for the backslash character, which is used to
initiate escape
...
The problem characters are the ASCII backslash and the ASCII tilde -
Good to know, I will eliminate those, although there are still many more
problem characters.
Well, actually, the one-byte backslash and tilde you can leave alone.
They survive intact, they just display differently over
]
Subject: Re: Japanese Charset
Date: Fri, 20 Sep 2002 16:25:29 +0900
...
The problem characters are the ASCII backslash and the ASCII tilde -
Good to know, I will eliminate those, although there are still many
more
problem characters.
Well, actually, the one-byte backslash and tilde you
Hi Xuefer,
What are you talking about? A lot of people are using MySQL without any
problems with multibyte characters. Please post a reference URL, with
perhaps a detailed explanation of the problem -- you mentioned you have
brought this to the attention of people already, please post a relevant
]
Subject: Re: Japanese Charset
Date: Fri, 20 Sep 2002 16:25:29 +0900
...
The problem characters are the ASCII backslash and the ASCII tilde -
Good to know, I will eliminate those, although there are still many
more
problem characters.
Well, actually, the one-byte backslash and tilde you
DuBois [EMAIL PROTECTED]
To: xuefer tinys [EMAIL PROTECTED],
[EMAIL PROTECTED],[EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
Subject: Re: Japanese Charset
Date: Fri, 20 Sep 2002 08:56:22 -0500
At 9:09 + 9/20/02, xuefer tinys wrote:
i'm sure mysql4.x have wrong algorithm to escape/unescape multibyte
I hope you will recognize that what you stated as a problem is _not_
what this thread was about.
You are talking about --
(a) A new (and as yet non-universal) version of MySQL
(b) Only binary data
(c) Conf done by you, which is not standard
Whereas the thread was about simple
i'm sorry that i've not read through nor understand the whole thread
From: Shashank Tripathi [EMAIL PROTECTED]
To: 'xuefer tinys'
[EMAIL PROTECTED],[EMAIL PROTECTED],[EMAIL PROTECTED],[EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
Subject: RE: Japanese Charset
Date: Sat, 21 Sep 2002 00:22:04 +0900
Thank you for your time and response.
I have checked if the text is surviving the paste buffer - it is. (I did
a character by character comparison of the text one pasted in the web
form, but before hitting submit.)
The problem characters are the ASCII backslash and the ASCII tilde -
Good to
This is for anyone out there storing Japanese characters along with
English characters.
Hi.
SUMMARY:
The client recently requested that Japanese be stored in an otherwise
standard English (Latin) MySQL database. Whereas all rows in the table
used to be Latin only, now some rows store
30 matches
Mail list logo