mysql_enable_utf8 results from the CPAN

Net-Z3950-DBIServer

Received-SPF: neutral (google.com: 78.47.209.209 is neither permitted nor denied by best guess record for domain of mike@lists.indexdata.dk) client-ip=78.47.209.209;
MIME-Version: 1.0
Content-Transfer-Encoding: binary
Content-Type: multipart/alternative; boundary="_----------=_1324430131990324"
In-Reply-To: <CACnMvBbdHNMwAhOsPRjtmSY3ZYSoYKmDGfnsq6k+gQ=PJzfzqw@mail.gmail.com>
References: <CACnMvBbdHNMwAhOsPRjtmSY3ZYSoYKmDGfnsq6k+gQ=PJzfzqw@mail.gmail.com>
 	 <CACnMvBbVoE58KPJ+o=GUvPee9WKu7YYhEfSzQ7NyVOnSh3nShw@mail.gmail.com> <77750.1324427016.15259758259483377664@ffe16.ukr.net>
 	 <26175.1324424434.17165909531854962688@ffe1.ukr.net>
To: "Mike Taylor" <mike@indexdata.com>
From: "Presich Oleksandr" <sendel@ukr.net>
Message-Id: <99032.1324430131.3977309154687057920@ffe16.ukr.net>
Date: Wed, 21 Dec 2011 03:15:31 +0200
Subject: Re: [zSQLgate] Broken cyrillic symbols

This is a multi-part message in MIME format.

--_----------=_1324430131990324
MIME-Version: 1.0
Content-Disposition: inline
Content-Length: 3313
Content-Transfer-Encoding: binary
Content-Type: text/plain; charset="windows-1251"

I've found the solution on this issue. Look into comments on this page: 
http://dev.mysql.com/doc/refman/5.0/en/charset-general.html
I've just tested it and adding one of these lines has resolved the
encoding problem:  - $dbh->do("SET character_set_results='utf8'");  - my
$dbh = DBI->connect($dsn, $user, $pass, {mysql_enable_utf8 => 1});  - $dbh->prepare("SET
NAMES 'utf8'")->execute();
So, the problem is with Perl - MySQL communication through DBD:MySQL.
I'm not sure for now if this is universal one and if it is needed to add
to the major version.

Anyway thanks for your responses and of course for the whole module.
>

> I guess I would start at the bottom of the stack and work up.  So:

1. Does your terminal print the characters correctly when fed them directly?
2. Does MySQL's own command-line client print the chars correctly?
3. Can you write a very simple Perl program using DBD::mysql that
fetches this data and properly prints it?
4a. If not, are you at least getting back the correct sequence of
octets?  So, is the problem with Perl's interpretation of those octets
as UTF-8?
4b. If your program works, what is zSQLgate doing differently?

I hope this is enough to be at least slightly helpful.  Best of luck
as you track this down -- do let me know how it turns out.

-- Mike.

2011/12/21 Presich Oleksandr <sendel@ukr.net>:
> Hi Mike,
> thanks for the quick response on that but unfortunately I'm not ready to
> spent funds on consultancy.
>
> So, for now i'm looking for any advise what and where could i dig to find
> out the reason of broken symbols.
>
>
>
> Hi, Presich.  I'll be happy to look into this for you if you wish, but
> because I am not using non-ASCII characters in zSQLgate myself this
> would be work I wouldn't otherwise undertake, which would mean I'd
> have to do it on a consultancy basis.  Do you have any funds that
> could be used for this?
>
> -- Mike.
>
>
>
> 2011/12/20 Presich Oleksandr <sendel@ukr.net>:
>> Hi all,
>> i'm trying to follow the zSQLgate Tutorial but can't read cyrillic symbols
>> from mysql database.
>>
>> MySQL default character set is utf8, text is saved in utf8_general_ci
>> collation but here is what i receive on the client:
>>
>> Listing 1: client
>>
>> Z> [presich@test ~]$ yaz-client @:3950
>> Connecting...OK.
>> Sent initrequest.

README.UTF8-FIX view on Meta::CPAN

>> Options: search present triggerResourceCtrl namedResultSets
>> Elapsed: 0.034328
>> Z> base mydb
>> Z> find @attr 1=12 @attr 2=3 29
>> Sent searchRequest.
>> Received SearchResponse.
>> Search was a success.
>> Number of hits: 1, setno 1
>> records returned: 0
>> Elapsed: 0.004471
>> Z> format xml
>> Z> show 1
>> Sent presentRequest (1+1).
>> Records: 1
>> []Record type: XML
>> <catalog_product_entity_text>
>>  <authorId>29</authorId>
>>  <authorName>??????? SDF</authorName>
>> </catalog_product_entity_text>
>> nextResultSetPosition = 2
>> Elapsed: 0.001676
>>
>> Please advise where and what else can I check that can broke the encoding.
>>
>> Thanks.
>>
>> _______________________________________________
>> zSQLgate mailing list
>> zSQLgate@lists.indexdata.dk>> http://lists.indexdata.dk/cgi-bin/mailman/listinfo/zsqlgate>>
>


--_----------=_1324430131990324
Content-Disposition: inline
Content-Length: 5279
Content-Transfer-Encoding: binary
Content-Type: text/html; charset="windows-1251"

<html>
<body>


  



  I've found the solution on this issue. Look into comments on this page:&#160; <a href="http://dev.mysql.com/doc/refman/5.0/en/charset-general.html">http://dev.mysql.com/doc/refman/5.0/en/charset-general.html</a>

  <div>
    <br>

    <div>
      I've just tested it and adding one of these lines has resolved the encoding problem:
    </div>

    <div>
      &#160;-&#160;<span style="font-family: Helvetica, Arial, sans-serif; font-size: 13px; line-height: 23px; text-align: -webkit-auto;">$dbh-&gt;do("SET character_set_results='utf8'");</span>
    </div>

    <div>
      <span style="font-family: Helvetica, Arial, sans-serif; font-size: 13px; line-height: 23px; text-align: -webkit-auto;">&#160;-&#160;</span><span style="font-family: Helvetica, Arial, sans-serif; font-size: 13px; line-height: 23px; text-align: -...
    </div>

    <div>
      <span style="font-family: Helvetica, Arial, sans-serif; font-size: 13px; line-height: 23px; text-align: -webkit-auto;">&#160;-&#160;</span><span style="font-family: Helvetica, Arial, sans-serif; font-size: 13px; line-height: 23px; text-align: -...
    </div>

    <div>
      <br>

      <div>
        So, the problem is with Perl - MySQL communication through DBD:MySQL.
      </div>

      <div>
        <br>
      </div>

      <div>
        I'm not sure for now if this is universal one and if it is needed to add to the major version.<br>

        <div>
          <br>
        </div>

        <div>
          Anyway thanks for your responses and of course for the whole module.<br>

          <blockquote class="ukr_editor_quotation" style="border-left: 1px solid rgb(204, 204, 204); margin: 0px 0px 0px 0.8ex; padding-left: 1ex;">
            <pre>
<br>I guess I would start at the bottom of the stack and work up.  So:

1. Does your terminal print the characters correctly when fed them directly?
2. Does MySQL's own command-line client print the chars correctly?
3. Can you write a very simple Perl program using DBD::mysql that
fetches this data and properly prints it?
4a. If not, are you at least getting back the correct sequence of
octets?  So, is the problem with Perl's interpretation of those octets
as UTF-8?
4b. If your program works, what is zSQLgate doing differently?

I hope this is enough to be at least slightly helpful.  Best of luck
as you track this down -- do let me know how it turns out.

-- Mike.



2011/12/21 Presich Oleksandr &lt;<a href="mailto:sendel@ukr.net">sendel@ukr.net</a>&gt;:
&gt; Hi Mike,
&gt; thanks for the quick response on that but unfortunately I'm not ready to
&gt; spent funds on consultancy.
&gt;
&gt; So, for now i'm looking for any advise what and where could i dig to find
&gt; out the reason of broken symbols.
&gt;
&gt;
&gt;
&gt; Hi, Presich.  I'll be happy to look into this for you if you wish, but
&gt; because I am not using non-ASCII characters in zSQLgate myself this
&gt; would be work I wouldn't otherwise undertake, which would mean I'd

( run in 0.629 second using v1.01-cache-2.11-cpan-39bf76dae61 )