Greetings, Markus!

We've upgraded to 1.2 and same behavior is observed. Setting collation of smw_atts2.value_xsd to utf8_general_ci does help to make english search case-insensitive but non-english is case-sensitive. I assume that this is happening because MW does store UTF8 data in latin1_bin columns. What I don't understand is why SMW_refreshData isn't populating SMW value column with proper UTF8 data as PHP strings should be UTF8 internally.

On Fri, Jun 27, 2008 at 9:28 AM, Markus Krötzsch <markus@semantic-mediawiki.org> wrote:
On Mittwoch, 25. Juni 2008, Eugene Mednikov wrote:
> Currently we use SMW 1.1.2 and have some problems with non-english text:
> case-insensitive search don't work and sorting is wrong. Tried to set SMW
> tables collation to utf8_general_ci without success.
>
> Is there better utf8 support in new DB engine in SMW 1.2?

SMW 1.2 has the advantage that all sorting uses a single table column the
collation of which could be set to achieve better sorting. This closely
relates to the new sort key column -- I will check if we can have some
parameter for setting this column's collation internally.

SMW 1.1 uses SMW tables as well as MediaWiki tables for sorting operations. In
general, I guess that you may need to rebuild table contents to make later
collation changes take effect.

Regards,

Markus

P.S.: I recall that the "UTF8" option during MediaWiki installation is
still "experimental" and has nothing to do with the above problem which
refers to SMW tables only. Using Unicode characters in MediaWiki and SMW is
possible in any case without special settings.

--
Markus Krötzsch
Semantic MediaWiki    http://semantic-mediawiki.org
http://korrekt.org    markus@semantic-mediawiki.org



--
Respectfully yours, Eugene Mednikov

Contacts:
phone: +972-54-4520187
email: eugene@mednikov.info
icq: 2014511
skype: eugenem79
msn messenger: eugenem79@gmail.com
livejournal: http://eugenem.livejournal.com
linkedin: http://www.linkedin.com/in/eugenem79
odnoklassniki: http://www.odnoklassniki.ru/user/334468507