Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Site upgrade complete; new features active' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Site upgrade complete; new features active
Authored by: robg on Oct 17, '09 02:53:00PM

Trust me, if you're horrified, I'm several levels beyond that. I changed nothing in the settings, but the upgrade made some changes that munged things. We're working on it, obviously.

The good news is that we will be able to mass replace characters once we figure out what's going on, so this should be a temporary problem.

-rob.



[ # ]
Unicode in posts
Authored by: MJCube on Oct 17, '09 06:26:14PM
I was going to say I hoped that, instead of having to change the stored text, you could just make the system read it properly as is. But in the course of editing this post (this time in HTML) I’ve discovered some things, and now I’m not sure what’s best.

In HTML mode I can type ⌘⌥⇧ and they are not lost. When I preview, my text in the box comes back as entities. (This reminds me of the old-old text engine, back when I wrote “How to post those special glyphs” in a comment to this hint 4 years ago.) But there’s a difference: Now when I’ve got entites in the text box and I preview again, they are correctly interpreted as characters. So at least I don’t lose my characters when I post in HTML.

I preferred the recent text engine that let us just type anything we want and it showed in Unicode everywhere. But I can live with the current way as long as the text of old posts can be restored. Thanks, Rob and others, for all your hard work to make this site better.

[ # ]

Unicode in posts
Authored by: robg on Oct 17, '09 06:56:44PM

I've posted the input form character set issues as a priority bug for the Geeklog team -- an improved engine was one of the reasons we were upgrading. To me, the input you type should never be changed; the system can do what it needs to the display, but your input should always be left untouched.

It's quite confusing the way it's working now.

-rob.



[ # ]