Hi Vikram, UTF8 uses more bytes than latin1. Most people in Europe won't need utf8. Therefore, the database size is smaller.
And: The shop templates are coded in latin1. Thorsten > Hi Arvydas, > I was just wondering why 'enable UTF mode' is an option for the user and > not a default setting? Is there any reason for users to NOT 'enable UTF > mode'? > Vikram > Arvydas wrote: >> Yes, you are right, there are some lines which overrides each other, it >> should look like: >> >> ALTER SCHEMA CHARACTER SET utf8 COLLATE utf8_general_ci; >> SET character_set_database=utf8; >> SET character_set_client = latin1; >> SET collation_connection = utf8; >> SET character_set_results = utf8; >> >> -------------------------------------------------- >> From: "Thorsten Albrecht" <[email protected]> >> Sent: Monday, July 20, 2009 4:02 PM >> To: "Arvydas" <[email protected]> >> Subject: Re: [oxid-dev-general] Translating OXID UI to other languages >> >>> Hi Arvydas, >>> >>> just a question concerning the following utf8 statements: >>> >>>> 2. When you mark UTF-8 checkbox setup does this: >>> >>>> ALTER SCHEMA CHARACTER SET utf8 COLLATE utf8_general_ci >>>> set names utf8 >>>> set character_set_database=utf8 >>>> SET CHARACTER SET latin1 >>>> SET CHARACTER_SET_CONNECTION = utf8 >>>> SET character_set_results = utf8 >>>> SET character_set_server = utf8 >>> >>> It seems to me a contradiction to use the following statements with >>> different character sets: >>>> set names utf8 >>>> SET CHARACTER SET latin1 >>> >>> See: http://dev.mysql.com/doc/refman/5.1/en/charset-connection.html : >>> >>> SET CHARACTER SET x means: >>> SET character_set_client = x; >>> SET character_set_results = x; >>> SET collation_connection = @@collation_database; >>> (Setting collation_connection also sets >>> character_set_connection ) >>> >>> whereas >>> SET NAMES x means: >>> SET character_set_client = x; >>> SET character_set_results = x; >>> SET character_set_connection = x; >>> >>> >>> Therefore, shouldn't it be enough to use: >>>> ALTER SCHEMA CHARACTER SET utf8 COLLATE utf8_general_ci >>>> set names utf8 >>> ? >>> >>> >>> BTW >>>> set character_set_database=utf8 >>> should not be necessary after altering the schema? >>> >>> BTW >>>> SET character_set_server = utf8 >>> should not be necessary after definining the default charset of the >>> database. >>> (and it won't be even possible on an managed server...). >>> >>> Thorsten >>> >>> >>> _______________________________________________ >>> dev-general mailing list >>> [email protected] >>> http://dir.gmane.org/gmane.comp.php.oxid.general >>> >> _______________________________________________ >> dev-general mailing list >> [email protected] >> http://dir.gmane.org/gmane.comp.php.oxid.general >> > _______________________________________________ > dev-general mailing list > [email protected] > http://dir.gmane.org/gmane.comp.php.oxid.general _______________________________________________ dev-general mailing list [email protected] http://dir.gmane.org/gmane.comp.php.oxid.general
