View Issue Details

IDProjectCategoryView StatusLast Update
0000780SOGoBackend Calendarpublic2010-08-27 01:26
Reporterhiro Assigned To 
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionno change required 
Product Version1.3.1 
Summary0000780: Can't handle multibyte string in SOGo
Description

Hello

When I try to add some events that contains multybyte string (Chinese/Japanses/Korean string like ?????),
multibyte strings always become "?".

I tried from CalDav client (iCal),
But it's same error.

Thanks

TagsNo tags attached.

Activities

ludovic

ludovic

2010-08-26 22:51

administrator   ~0001372

That depends on the underlying database encoding.

SOGo handles everything in UTF-8. So if it comes back broken, the DB broke it.

hiro

hiro

2010-08-26 23:28

reporter   ~0001373

I confirmed settings of DB.
Database Collation is utf8-bin.

I also tried to change some "?" strings on sogo****_quick table.
After changing, I can see multibyte strings on SOGo web interface.
But after make some modification on web interface, string is back to "?" again.

Thanks.

ludovic

ludovic

2010-08-26 23:37

administrator   ~0001374

Please show all database related parameters with regard to encoding.

Also, please test on sogo-demo.inverse.ca and report.

ludovic

ludovic

2010-08-26 23:53

administrator   ~0001375

Also, make sure you have those defaults in your SOGo configuration:

WOParsersUseUTF8 YES
WOMessageUseUTF8 YES
NGUseUTF8AsURLEncoding YES

hiro

hiro

2010-08-27 00:01

reporter   ~0001376

I tried on sogo-demo.inverse.ca. And it works there.
So something is wrong on our configuration.

I'll check configurations.

Thanks

ludovic

ludovic

2010-08-27 00:32

administrator   ~0001377

Make sure in your my.cnf file you have:

[mysqld]
...
character_set_server=utf8
character_set_client=utf8

[client]
default-character-set=utf8

[mysql]
default-character-set=utf8

and when you created the sogo database, you did:

create database sogo CHARSET='UTF8';

ludovic

ludovic

2010-08-27 01:26

administrator   ~0001379

Configuration issue.

Issue History

Date Modified Username Field Change
2010-08-26 22:50 hiro New Issue
2010-08-26 22:51 ludovic Note Added: 0001372
2010-08-26 23:28 hiro Note Added: 0001373
2010-08-26 23:37 ludovic Note Added: 0001374
2010-08-26 23:53 ludovic Note Added: 0001375
2010-08-27 00:01 hiro Note Added: 0001376
2010-08-27 00:32 ludovic Note Added: 0001377
2010-08-27 01:26 ludovic Note Added: 0001379
2010-08-27 01:26 ludovic Status new => closed
2010-08-27 01:26 ludovic Resolution open => no change required