I has forgotten to tell that SAT@Home uses  Boinc Server package ver. 6.11.0 
and DC-API from SZTAKI http://www.desktopgrid.hu/index.php?page=7

---
Nikolay


19 ноября 2011, 00:48 от Nikolay Saharov <[email protected]>:
> Thanks, and I'm sorry, I don't know what to say because my knowledge of MySQL 
> is small.
> 
> I confirm that cyrillic works in test project.
> 
> I wrote to developers of russian projects (OPTIMA@Home - 
> http://boinc.isa.ru/dcsdg/, SAT@Home - http://sat.isa.ru/pdsat/) 
> where was this problem. May be they can comment this.
> But they fixed the problem using some of the scripts below (for forum and 
> private messages tables).
> 
> ---
> Nikolay
> 
> 19 ноября 2011, 00:12 от David Anderson <[email protected]>:
> > I'm confused, because on our server, without the modifications below,
> > we're able to create message board postings with various non-ASCII 
> > characters,
> > including cyrillic, and they display correctly.
> > See, for example:
> > http://isaac.ssl.berkeley.edu/test/forum_thread.php?id=57#132
> >
> > Our MySQL version:
> > Server version: 5.5.14 MySQL Community Server (GPL)
> >
> > Character set info:
> > mysql> show variables like 'character_set%';
> > *************************** 1. row ***************************
> > Variable_name: character_set_client
> > Value: latin1
> > *************************** 2. row ***************************
> > Variable_name: character_set_connection
> > Value: latin1
> > *************************** 3. row ***************************
> > Variable_name: character_set_database
> > Value: latin1
> > *************************** 4. row ***************************
> > Variable_name: character_set_filesystem
> > Value: binary
> > *************************** 5. row ***************************
> > Variable_name: character_set_results
> > Value: latin1
> > *************************** 6. row ***************************
> > Variable_name: character_set_server
> > Value: latin1
> > *************************** 7. row ***************************
> > Variable_name: character_set_system
> > Value: utf8
> > *************************** 8. row ***************************
> > Variable_name: character_sets_dir
> > Value: /usr/share/mysql/charsets/
> > 8 rows in set (0.00 sec)
> >
> > Anyway, if the problem can be fixed without changing the BOINC code
> > (e.g., by upgrading to the current MySQL)
> > I'd rather do it that way.
> >
> > -- David
> >
> > On 13-Nov-2011 10:48 AM, Nikolay Saharov wrote:
> > > Hi,
> > >
> > > There is a problem with encoding in the BOINC database for forum and 
> > > private
> > > messages.
> > >
> > > When users write their messages on the native languages (for example in
> > > Russian, in cyrillic charset), these messages are shown as question marks
> > > (?????).
> > >
> > > The problem is because of BOINC DB tables are non-UTF8 encoded by default.
> > >
> > >
> > > There is a small patch ;-)
> > >
> > > alter database boinc_db default character set = utf8;
> > >
> > > alter table user convert to character set utf8; alter table team convert 
> > > to
> > > character set utf8; alter table profile convert to character set utf8; 
> > > alter
> > > table category convert to character set utf8; alter table forum convert to
> > > character set utf8; alter table thread convert to character set utf8; 
> > > alter
> > > table post convert to character set utf8; alter table private_messages
> > > convert to character set utf8; alter table friend convert to character set
> > > utf8;
> > >
> > >
> > > May be there are other tables too.
> > >
> > > --- Nikolay
> > >
> > > _______________________________________________ boinc_dev mailing list
> > > [email protected]
> > > http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe,
> > > visit the above URL and (near bottom of page) enter your email address.
> >
> --
> 
> 
--

_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

Reply via email to