Mysql create database utf8
Regarding the pages UTF8 header meta-tags. The real key is removing any lingering latin1 encoding in the new installs or the users database will degrade. Then you avoid confusion during installation (most people are clueless to this stuff it took me several weeks to develop any appreciation for this stuff). Then the unusual user who wants something else can always directly change it through mysql (i think this is possible). Could always make that the default for the database on install.
Mysql create database utf8 plus#
Plus unicode seems like it pretty much works for everything.
Mysql create database utf8 install#
Even though your gonna force the database to UTF-8, you may still want to consider adding this to end of each table (Then your in effect forcing every install to UTF-8 even if make database shell first I think this will be important since your gonna now be forcing read/writing of UTF8 to the mysql database in the new installs): Agree with getting rid of the bin part(they are using this for numbers, since collation is much simpler), then can get rid of all of that set utf8 collate crap. The current utf8-bin/utf8-unicode separation is sort of clever but is a huge pain to maintain. Figured it would take me like a year to begin to implement this with my limited time. Once the entire database is forced to UTF-8 encoding we are then one step closer to having functional chinese/russian (there is a demand for this) Wouldstill need read/write utf-8 mysql command in library/translator.inc, ensure proper meta header tags on all the pages, and make the phpgacl utf-8 complaint, which will involve making another dumpfile and shortening some key). I suppose could leave the collater up to the database but UTF8-unicode seems to be a good broad shotgun approach collator (again the concept of encoding/collation is not within the grasp of most users until its too late). If possible, agree would be cleaner to set the default UTF-8 encoding during the database creation (but is this possible, and what happens to users who create the shell database themselves?) instead of placing into database.sql. Right now the majority of database is forced to utf-8 encoding with collation of characters strings by utf-8-unicode (values get default collation of utf-8-bin), along with an annoying amount of latin1 mixed in.įorcing complete UTF-8 encoding in database is a good idea since most users have no clue what this is until it’s too late(is a real pain if a user realizes they need to migrate from latin1 to utf-8 lots of horror stories online). This will have direct effects on the translation project.
Bradymiller wrote on Friday, May 01, 2009: