Hi,

I think Joel Rees wrote an interesting message as well. Hope you read
it. 

I run MySQL on Windows, SuSE 7.3 (Linux) and FreeBSD. Access it through
ASP/PHP/JSP/Perl DBI. There is no problem as far as I am concerned, it
works without a hitch. 

If your default locale is EN, then you may see junk text in your MS DOS
prompt but rest assured, it is most likely the correct data -- it just
appears that way to you. Try dumping the same data onto a web page with
the following META tags: 


    <%@ Language=VBScript %>
    <% 

    ' Some OLEDB/ODBC code comes here 
    ' to initialize a variable with your JP text 

    %>

    <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
    <html lang="ja">
        <head>
        <meta http-equiv="Content-Type" content="text/html;
charset=Shift_JIS">
        ....
        </head>

    <body>
                 <% Response.Write ("-----YOUR JP TEXT COMES HERE-----")
%>
    </body>
    </html>



That should do it. 

Cheers,
Shanx


Shashank Tripathi 
www.shanx.com 




    | -----Original Message-----
    | From: Dawn Friedland [mailto:[EMAIL PROTECTED]] 
    | Sent: Wednesday, September 18, 2002 7:46 AM
    | To: Shashank Tripathi; [EMAIL PROTECTED]
    | Subject: RE: Japanese Characters in MySQL & Win2k
    | 
    | 
    | Thank you Thank you. 
    | 
    | Are you running MySQL on Windows and using ASP on the web 
    | server?  
    | 
    | When I display the data after pulling it out, I use Shift_Jis. 
    | 
    | Yes, I mean the DOS prompt. My default language is 
    | English. I fear changing my locale because I wouldn't be 
    | able to change it back without a deepfry (I can't read 
    | Japanese!)  
    | 
    | -----Original Message-----
    | From: Shashank Tripathi [mailto:[EMAIL PROTECTED]] 
    | Sent: Tuesday, September 17, 2002 3:36 PM
    | To: Dawn Friedland; [EMAIL PROTECTED]
    | Subject: RE: Japanese Characters in MySQL & Win2k
    | 
    | 
    | Storing JP and EN data in the same table has worked for 
    | me ever since I started using MySQL. Unlike Oracle, you 
    | don't need any specific charset configs (I may stand 
    | corrected). The idea is to use the correct character 
    | encodings when you *display* the data after pulling it 
    | out. In your case, I'd think Shift_JIS. 
    | 
    | You mention displaying on the command line...u mean DOS 
    | prompt? If not, and if you meant some software, it shd be 
    | easy. If you meant DOS prompt, I guess it depends on what 
    | the default language in your windows box is. Do you have 
    | Japan set as your default locale and as the default 
    | language (Regional Options in Control Panel)?  If so, the 
    | data shd display correctly without any additional effort. 
    | 
    | You can store EUC, Shift, ISO2022, and for that matter, 
    | Chinese in the same table in diff rows as well. During 
    | presentation time (display), just display using the 
    | appropriate encoding and it shd be ok. 
    | 
    | Holler if you need more help.  
    | 
    | Cheers,
    | Shashank
    | 
    | 
    | 
    | 
    | 
    | 


---------------------------------------------------------------------
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/           (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Reply via email to