What is the best option for smooth performing of SMW: utf8 or binary?
Why this problem is important? http://www.semantic-mediawiki.org/wiki/Help:Troubleshooting#Database_errors:_illegal_collation recommends... Your database tables for MediaWiki and SMW have been generated with different settings. To fix the problem... We understand that is better to syncronize the collation/character set of default installation with extensions.

Arguments...
Pro binary
1. Mediawiki Default installation recommends binary.

Pro utf8
1. Wikia is using utf8 http://www.wikia.com/index.php?title=Forum:Wikia_MySql_Character_Set:_Binary_of_UTF-8%3F
2. http://www.semantic-mediawiki.org/wiki/Programmer%27s_guide_to_SMW  All files need to be stored as UTF8! This is absolutely crucial.... Maybe this is about smw files only.
3. The database cluster must have been initialized with UTF-8 encoding with PostgreSQL. http://www.semantic-mediawiki.org/wiki/PostgreSQL. Is this valid for Mysql too( as a recommendation only)?
4. We are using wikia extensions like http://www.mediawiki.org/wiki/Extension:SocialProfile, that explicitly use utf8 http://svn.wikimedia.org/viewvc/mediawiki/trunk/extensions/SocialProfile/UserProfile/user_profile.sql?view=markup. In this case could SMW binary conflict with SocialProfile utf8 ?

or is just does not matter the encoding we are using for SMW ?

P.S. Semantic Mediawiki does not use  $wgDBTableOptions in order to synchronize the collation/character set with mediawiki default installation. In order to do this, we must set up it manually.

Kind Regards,
Julian