News for hackers. Stuff that matters.
Re:Bacon Ipsum, because Unicode is hard by jhawthorn on Monday June 25, 2012 @04:27AM (#4155615)
I've been using fullwidth characters. Due to their simplicity to convert to and read. This page of course has the advantage of more variety in characters.

Fullwidth conversion code in ruby:

  "string".tr(' !-~', "\u3000" + (0xFF01...0xFF5f).to_a.pack('U*'))
Re:Bacon Ipsum, because Unicode is hard by geon on Monday June 25, 2012 @05:14AM (#4155734)
I wondered what was up with the weird kerning.

    Nam
    Nam
(By the way, they seem to break tab-indentation for pre formatted text in the markdown.)
Re:Bacon Ipsum, because Unicode is hard by Danieru on Monday June 25, 2012 @10:22AM (#4156602)
Full width characters have a fun habit of breaking most things. Even more so than unicode.

Since they are only used in CJK languages the majority of programmers are unaware of them. The seperate code points between half-width and full-width mean that you need a decent unicode library. Otherwise a user could spoof another user.

One cool feature is it lets you write monospaced even if you do not control the font. Since there are full-width codepoints for most programming symbols.