Hot answers tagged

60

I've been meaning to make this change for a while, so this was a good nudge to finally do it: From the next build on, if a comment thread contains a comment by a user whose name starts with a non-ASCII letter, then just typing @ will bring the tab completer up with that name: If all reply candidates start with "normal" letters (or numbers), then the tab ...


29

Unicode magic is inserted in comments (not just in `code`) whenever no whitespace was seen for about 80 characters, to enforce line wrapping. Without that the layout can really be messed up. Jeff once explained why this magic is needed: The word-wrap:break-word suggestion is a good one. Works fine on posts, which are fixed width, and that is ...


27

This is something that has been bothering me for a while. I designed the anti-spam / anti-abuse layer that's been keeping most of this crap out for the last couple of years, and it was designed with 'snow shoe' spammers in mind. For those of you unfamiliar with the term 'snow shoe' when it comes to spamming, well, consider a snow shoe: What this ...


26

If someone uses a user name that breaks site functionality, moderators will simply change that username and ask the user to rename to something harmless. If a user intentionally continues to break the site that way, they'll be suspended. Given how rare this is likely to come up, I think handling it manually is the best choice.


25

Since comments have to be stored in the database as nvarchar(600) the current behavior accurately measures the remaining number of . . . something. Thanks to UCS-2 and SQL Server's definition of the len() function, 300 bananas has a length of 600, so the count is accurate in terms of what we'll be able to store. The problem here is terminology and the ...


19

Focussing on bananas and related monkey-business serves only to distract from the real issue here, which is that tags are restricted to only a few possible characters, the letters and digits from old-school 7-bit ASCII. Bananas are symbols, not alphanumerics, and tags are a sort of identifier. So it makes reasonable sense to restrict tags to identifier ...


15

Such measures are pointless. Someone finding obscure Unicode characters to bypass filters won't be stopped by banning of any specific character. Even if you ban every non-ASCII character, there's good old underscore. Serves same purpose, just isn't as pretty. Unicode is constantly updated. It's incredibly tedious to keep up with it. Hint: there're already ...


14

Steps reproduce this behavior with Firefox: Open the chat in a new tab. (There can't be any history in the tab, since pressing backspace would abandon the page.) Remove the focus from the <textarea>. (Pressing tab when there's nothing to autocomplete does this.) Press backspace. I also think that I've isolated the faulty code in master-chat.js: $(...


14

I'm against filtering this. Not because that it can be abused, but because it's unnecessary and an unnecessary additional technical restraint. The team stated in the past that filtering out Unicode is a little bit...well, not exactly worth the hassle. I think this is not different. I can also impersonate Moderators and Developers by changing my Username and ...


13

As of about a month ago, these characters are no longer inserted, since comments are no longer laid out with a <table> (and the table layout algorithm was what prevented fixing overflow in any other way).


13

I followed your link to Lawrence's profile and from there to an answer of his. I clicked Add Comment and typed @l whereupon the autocomplete offered me his whole name. For Ωmega I couldn't find a letter to type that triggered the autocomplete - I expect copy and paste would work.


13

You need to provide a valid URL; your browser is a lot more tolerant about what characters it accepts, but when I copy the URL from the Chrome location bar I get the real URL: https://plus.google.com/+Rub%C3%A9nRivera Note the %C3 and %A9 parts; those are UTF-8 bytes encoded using URL percent encoding. The C3 A9 bytes encode a é character. Using the URL ...


13

I'm not sure how you expect SE to implement this? The Unicode characters are stored and served back, it is the fonts used that lack support. SE uses the stock fonts Arial, "Helvetica Neue", Helvetica, sans-serif so it is up to browser and OS maintainers to get their stuff updated. Once they do the new chars will show. One possible way for SE to be ...


12

Well, since comments won't allow the ordinary strike formatting, someone there tried (and succeeded!) to trick the system by combining Unicode characters resembling English letters with a strike through them. This results in one long stream of characters without any blank space, no different than: sincecommentswon'tallowtheordinary<strike>strike<...


12

Apparently, the link has a special character that cannot be chosen. What I mean by that is that if you try to highlight or delete this special letter, it will simply not disappear. To me, this means that this is a valid character but would not be able to be linked by the system. The special character: Seemingly, SOUP has already has this fixed so a quick ...


12

Yup, you found something that is definitely annoying but it's not worth it to fix it. In the words of Jeff: The short answer is "don't do that", and the longer answer is "if you keep doing that, there will be consequences." I'll just reiterate what he said with this:


12

Stack Exchange has full Unicode support. This means you just need to type the character into the post body, or copy it from somewhere. In Windows, you can use Alt + Num2 + Num2 + Num5, or using the character map. In macOS, you can long press S to get it.


12

Chinese characters are blocked in posts network-wide, with the exception of a few sites (including this one), because of persistent spam posts that use them. The error message is intentionally kept nondescript to prevent spammers from catching on to the real cause why their posts are being blocked. tl;dr: spammers prevent us from having nice things...


11

By Mark Gravel comment this is to be considered as now by-design and as such won't be modified unless problems emerge that make the fix worth the effort. In the meantime abuses of the system shall be dealt manually.


11

That is caused by the spam prevention rules that got implemented on some sites due to the amount of spam with CJK characters. You could work around the limitation to only use @CiroSantilli and remove the non-latin characters.


11

You can use the HTML entity: &szlig; produces ß. Or just copy it over from other posts, since it's part of Unicode.


10

The Stack Exchange Title-to-URL-slug converter cannot handle characters outside the BMP (the Basic Multilingual Plane), running from U+0000 through to U+FFFF. The character in question, U+1F60B, is encoded to UTF-16 using a surrogate pair instead, so you get U+D83D U+DE0B, and those are not 'displayable' (not valid Unicode) and get replaced by two U+FFFD ...


10

There’s been a lot of CJK spam on SU and Meta lately; probably that’s why it’s Forbidden. Zap! If it had let me enter it, this posting would have looked something like this: That character is: U+4EC0 CJK UNIFIED IDEOGRAPH-4EC0 Mandarin SHI2 SHEN2 Cantonese sam6 sap6 zaap6 JapaneseKun KUMI TOU MAJIRU JapaneseOn SHUU JUU Korean ...


9

This is not a bug. Those are characters in the the Burmese script — or more technically, characters with the Unicode Script=Mymr character property. The actual string he uses, “ကစၥပ နဒီ”, when rendered with hex escapes is: "\x{1000}\x{1005}\x{1065}\x{1015} \x{1014}\x{1012}\x{102E}" And with the far superior named escapes is: "\N{MYANMAR LETTER KA}\N{...


9

Unicode support is enabled on a per-site basis. The language sites that need it have it turned on already, it is not enabled on Stack Overflow. We haven't seen a large need for them there with nearly 5 million questions asked...to change the tag rules and introduce them at this point we'd have to see a very convincing argument.


9

As of now, the HTML sanitizer will no longer remove links that can be made conforming to its whitelist by percent-encoding the illegal characters instead. In other words: This will work as expected. In a related but different change, free-form link recognition now allows any word characters, not just A to Z. So http://en.wikipedia.org/wiki/Möbius_strip will ...


9

This is just how Android has displayed unknown characters for a long time, by just displaying an empty space instead of the usual empty box that we've come to know from most operating systems. There's absolutely nothing Stack Exchange can do about it. However, the most recent releases of Android do fix this problem (at least the Lollipop update on my HTC ...


9

As far as I can tell this has been fixed with the new version of the separator code. However this does not apply to chat, yet. (*) no kittens were harmed in the making of this patch. (**) unfortunately, we cannot guarantee not to have invoked Cthulhu, the ancient, in the process.


9

Unicode is vast and growing. And while the actual diamond character we use is blocked I suspect a regex to block anything that remotely looks like a mod diamond would be long and growing. I also have no idea if we have any users who speak the vai language, and might choose to use that for their username, If someone is pretending to be a moderator, or there'...


Only top voted, non community-wiki answers of a minimum length are eligible