Stories
Slash Boxes
Comments

Dev.SN ♥ developers

posted by NCommander on Sunday February 16 2014, @06:13PM   Printer-friendly
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.
Display Options Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 1) by c0lo on Tuesday February 18 2014, @10:58PM

    by c0lo (156) on Tuesday February 18 2014, @10:58PM (#2111)

    A character beyond what UNICODE restricts itself: &amp#x20FFFF; - shows like
    Something below the max limit, valid, but unassigned 𰀁 - shows like
    Something that's an invalid UNICODE character -  - shows like
    The REPLACEMENT CHARACTER i.e. � - shows like �

    Now, what the above will do inside the storage, I don't know, I'm just trying to go forth and BREAK those minions!

    (hmmm, the "preview" looks like they are totally kicked out, not replaced by the replacement character [wikipedia.org] - won't cry over the loss of it)