Slashdot Mirror

Probably because it was known years ago. Just look at U+0391 U+0410 and U+0041. Or at U+0430 and U+0061 and if you find a word that would use such a letter, you can make serious bÐnk.

(Luckily it does not work on /.)

Some "smart" word processors insert one of these when you type an apostrophe. They tend to pick some other "smart" punctuation that is similarly corrupt when transfered to an ASCII plaintext format.

"â(TM)" is Slashdot's attempt at salvaging the the two bytes of character data that make up an exotic apostrophe.

So, to call you completely wrong, the original word is "can't" rather than "cannot."

So have individuals who create Twitter accounts that look like companies & tweet all about the Olympics (hashtags owned by the IOC!). Bring on the massive work by the IOC for nothing.

Heck use all the supported unicode!

http://unicode-table.com/en/#l...

@cke

Here's some help as to how:
https://metacpan.org/pod/Acme:...
Acme::Unicodify - Convert ASCII text into look-somewhat-alike unicode

LOL at Slashdot not supporting unicode. There's a unicode 'o' between the c and the k so it looks like @coke.

Thank you for ninjaing me. I often chime in about this issue when someone complains about Slashdot's lack of support for Unicode. Most of the time, after I explain the code point whitelist and the reason for it, someone complains that a blacklist of dangerous code points would work better. My usual reply is that new versions of Unicode may insert new control code points that get activated before the Slashdot admins have the chance to add them to the blacklist. And besides, many characters outside the current whitelist are far more useful for what used to be called "ASCII art" than for readable text in the English language. For example, Oriya letter ii (U+0B08) looks to English speakers more like the head of a Smurf. And ASCII Goatse and ASCII Jack Off are why Slashdot had to add a lameness filter in the first place.

But apparently, Slashdot doesn't strip bad characters on display, only on post. This post, for example, still contains a bidirectionality override.

But in English those things are symbolically different and used in different contexts. In Cantonese (in its data model, so to speak) lights, windows and mirrors are the same things.

Cantonese is my native tongue and you are either being badly misled, or you are sprouting from you ass.

Too bad /. cannot handle unicode, the characters for them are:

light: http://unicode-table.com/en/5149/

window: http://unicode-table.com/en/7A97/

mirror: http://unicode-table.com/en/93E1/

Perhaps you can share which character you meant that have Cantonese speaking mixing up these 3 things?

But in English those things are symbolically different and used in different contexts. In Cantonese (in its data model, so to speak) lights, windows and mirrors are the same things.

Cantonese is my native tongue and you are either being badly misled, or you are sprouting from you ass.

Too bad /. cannot handle unicode, the characters for them are:

light: http://unicode-table.com/en/5149/

window: http://unicode-table.com/en/7A97/

mirror: http://unicode-table.com/en/93E1/

Perhaps you can share which character you meant that have Cantonese speaking mixing up these 3 things?

But in English those things are symbolically different and used in different contexts. In Cantonese (in its data model, so to speak) lights, windows and mirrors are the same things.

Cantonese is my native tongue and you are either being badly misled, or you are sprouting from you ass.

Too bad /. cannot handle unicode, the characters for them are:

light: http://unicode-table.com/en/5149/

window: http://unicode-table.com/en/7A97/

mirror: http://unicode-table.com/en/93E1/

Perhaps you can share which character you meant that have Cantonese speaking mixing up these 3 things?