List:General Discussion« Previous MessageNext Message »
From:Gleb Paharenko Date:March 8 2005 9:05pm
Subject:Re: Hebrew
View as plain text  
Hello.

In most encodings english letters remain unchanged, but to be sure
you may execute set NAMES latin1 before quering tables with English
data.




"John Berman" <john_berman@stripped> wrote:
> Thanks will do this.
> 
> In the same dBase there a lots of tables were the data is in English - I
> assume they will be ok ?
> 
> John B
> 
> -----Original Message-----
> From: Gleb Paharenko [mailto:gleb.paharenko@stripped] 
> Sent: 07 March 2005 21:12
> To: mysql@stripped
> Subject: Re: Hebrew
> 
> Hello.
> 
> Put all your character_set_xxx variables to hebrew. See:
> 
>  http://dev.mysql.com/doc/mysql/en/charset-connection.html
> 
>  
> 
> "John Berman" <john_berman@stripped> wrote:
>> How's this
>> 
>> 
>> +--------------------------+-----------------------------------+
>> | Variable_name            | Value                             |
>> +--------------------------+-----------------------------------+
>> | character_set_client     | latin1                            |
>> | character_set_connection | latin1                            |
>> | character_set_database   | hebrew                            |
>> | character_set_results    | latin1                            |
>> | character_set_server     | latin1                            |
>> | character_set_system     | utf8                              |
>> | character_sets_dir       | /usr/mysql4/share/mysql/charsets/ |
>> +--------------------------+-----------------------------------+
>> 
>> 
>> John B
>> 
>> -----Original Message-----
>> From: Gleb Paharenko [mailto:gleb.paharenko@stripped] 
>> Sent: 07 March 2005 12:28
>> To: mysql@stripped
>> Subject: Re: Hebrew
>> 
>> Hello.
>> 
>>> Pointers were I went wrong would be appreciated
>> 
>> What's the default character set for your server? Please, send
>> us an output of the following statement:
>> 
>>  show variables like '%char%';
>> 
>> Please, use mysql command line client.
>> 
>> 
>> 
>> "John Berman" <john_berman@stripped> wrote:
>>> Using 4.1
>>> 
>>> Though I had it cracked ?
>>> 
>>> I created a new table and set the Charset to Hebrew and the field =
>>> =A0Collation
>>> to hebrew_general_ci=A0
>>> 
>>> I then uploaded data to the database using MS Acess (with an ODBC
>>> connection)
>>> 
>>> In MSAccess on my PC the Hebrew comes through fine.
>>> 
>>> However when I open the newly created table using MSAccess or phpMyAdmin
>>> the Hebrew is represented with question marks.
>>> 
>>> Pointers were I went wrong would be appreciated
>>> 
>>> Regards
>>> 
>>> John Berman
>>> 
>>> --=20
>>> No virus found in this outgoing message.
>>> Checked by AVG Anti-Virus.
>>> Version: 7.0.308 / Virus Database: 266.6.2 - Release Date: 04/03/2005
>>> =20
>>> 
>>> 
>> 
>> 
> 
> 


-- 
For technical support contracts, goto https://order.mysql.com/?ref=ensita
This email is sponsored by Ensita.NET http://www.ensita.net/
   __  ___     ___ ____  __
  /  |/  /_ __/ __/ __ \/ /    Gleb Paharenko
 / /|_/ / // /\ \/ /_/ / /__   Gleb.Paharenko@stripped
/_/  /_/\_, /___/\___\_\___/   MySQL AB / Ensita.NET
       <___/   www.mysql.com



Thread
HebrewJohn Berman5 Mar
  • Re: HebrewGleb Paharenko7 Mar
    • RE: HebrewJohn Berman7 Mar
      • Re: HebrewGleb Paharenko8 Mar
        • RE: HebrewJohn Berman8 Mar
          • Re: HebrewGleb Paharenko9 Mar
            • RE: HebrewJohn Berman12 Mar
              • Re: HebrewGleb Paharenko14 Mar