UTF-8 is indeed the characterset you want to use for the page encoding;
although some browsers will support UTF-16, etc., not all will.
But the real issue has to do with what technology you are using to connect
to the db. Is it ASP on the server side? Or something else? And what is the
server?
michka
----- Original Message -----
From: "Stephen Toner" <toners5@hotmail.com>
To: "Unicode List" <unicode@unicode.org>
Sent: Monday, September 04, 2000 4:21 AM
Subject: Unicode in web pages
> Hi,
> I'm fairly new to unicode and have a few problems trying to input it from
a
> brower.
> I need to take input from a web-page, and store it in a database. Web
pages
> are then driven from this database. We want to use unicode to allow
> multi-lingual support. I was wondering if anyone could tell me of any
> issues likely to be faced in this process.
> Our database is capable of storing unicode, but I'm not sure if what is
> reaching the database is actually unicode. Using IE 5.5, a textarea in a
> form is submitted containing any entered text. I have tried specifying
the
> page's character set as UTF-8. What then reaches the database is a series
> of ASCII values with foreign characters such as Japanese, or accented
> characters, converted to a few symbols. I don't know if this is unicode,
> where when I look at it in the database the multi-byte characters can be
> seen as a combination of single byte (gibberish) characters.
> If this isn't unicode do I need to put in some sort of converter to change
> to &#xxxx; format? Some web sites seem to say that for html, unicode must
> be changed to this numeric character reference format.
> I would appreciate any advice.
> Thanks in advance,
> Stephen
> _________________________________________________________________________
> Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
>
> Share information about yourself, create your own public profile at
> http://profiles.msn.com.
>
>
This archive was generated by hypermail 2.1.2 : Tue Jul 10 2001 - 17:21:13 EDT