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.
At present, there's nothing stopping someone from writing in German, French, Spanish, or many other languages using Latin letters (more or less). Since it doesn't happen, I don't think we need to worry.
(But if I post in a quote with an em-dash: — or some “proper†‘quotes,’ maybe an arrow → or temperature (0°C) it won't make a mess.)
(Score: 1) by xaxa on Tuesday February 18 2014, @07:49PM
At present, there's nothing stopping someone from writing in German, French, Spanish, or many other languages using Latin letters (more or less). Since it doesn't happen, I don't think we need to worry.
(But if I post in a quote with an em-dash: — or some “proper†‘quotes,’ maybe an arrow → or temperature (0°C) it won't make a mess.)
(Nope, looks like it's going to make a mess.)