posted by
NCommander
on Sunday February 16 2014, @10:13PM
from the ¡sᴉɥʇ-sǝlpuɐɥ-ʍou-ǝʇᴉs-ǝɥʇ dept.
So, after dealing with a bit of monkeying with the database, I'm pleased to announce that Soylent should (in theory) have support for UTF-8 starting immediately. Now obviously this isn't well tested, so this is your chance to break the site in two, consider the comments below to be "open season" so to speak. I know the comment preview has some issues with UTF-8 (and it only works at all in Plain Text or HTML modes)
For purposes of breakage, anything that breaks the site layout/Reply To/Parent/Moderate buttons, or breaks any comments beyond itself is considered bad. We need to stop those. If you can break it (which shouldn't be hard), you earn a cookie, and I'll get you in the CREDITS file as something awesome.
For comments that are just plain unreadable, moderation will take care of them, and that isn't considered a bug. So go forth and BREAK my minions! ()}:o)↺
This discussion has been archived.
No new comments can be posted.
Isn't setting up a UTF-8 capable front-end and database a pretty basic task these days; something do get done after following a few tutorials and articles?
You create your database with the right settings (e.g. utf8_general_ci collation in MySQL) and make sure that your page scripts don't garble the content entered via the form. Recent versions of PHP and Python can do that just fine, never used Perl though.
(Score: 1) by PrinceVince on Monday February 24 2014, @01:27AM
Isn't setting up a UTF-8 capable front-end and database a pretty basic task these days; something do get done after following a few tutorials and articles?
You create your database with the right settings (e.g. utf8_general_ci collation in MySQL) and make sure that your page scripts don't garble the content entered via the form. Recent versions of PHP and Python can do that just fine, never used Perl though.