Using quotation marks/punctuation - Recent glitches on message boards

  • 2
  • Problem
  • Updated 7 years ago
  • Solved
Archived and Closed

This conversation is no longer open for comments or replies and is no longer visible to community members. The community moderator provided the following reason for archiving: IMDb boards

I've noticed a couple of very recent (last few hours, in fact) glitches on the message boards. 1. Quotation marks and apostrophes, originally keyed in Microsoft Word, have now been scrambled, showing up as various combinations of letters, numbers and symbols. Messages posted in earlier days that were okay are now scrambled too. 2. It seems that some movie titles are showing up with their foreign/overseas titles. For example, The Haunting sometimes appears as its Spanish title La Maldicion. It seems to be a random pattern, but I can't be sure. Thanks for your help.
Photo of Paul DiMaria

Paul DiMaria

  • 1 Post
  • 0 Reply Likes
  • frustrated

Posted 7 years ago

  • 2
Photo of Paul DiMaria

Paul DiMaria

  • 1 Post
  • 0 Reply Likes
To be more specific, smart quotes are no longer working on the message boards, although they were until yesterday.
Photo of DrakeStraw

DrakeStraw

  • 286 Posts
  • 132 Reply Likes
Special characters seem to be in a death spiral on the boards. Every time they fix something they break something elsewhere. They must be trying hard to find a way out of the problem, because the cursor bugs in the åÁâ tool that creates them haven't been fixed in the last couple of days. Successive åÁâ Previews compound the corruption:

åÁâ
åÁâ
åÁâ
åÁâ

When previews do this on each successive pass, they really aren't previews at all.
Photo of Paul DiMaria

Paul DiMaria

  • 1 Post
  • 0 Reply Likes
Although, this didn't start immediately after the new design went into effect. Well, I need to qualify that - messages that already existed on "D-Day" did have problems. All the smart quotes turned into little black diamond shapes with question marks inside.

And, oddly enough, those older messages (or at least the ones I know about) now appear to be fixed. New messages continue to have problems.
Photo of DrakeStraw

DrakeStraw

  • 286 Posts
  • 132 Reply Likes
They can't seem to fix the new ones without breaking the old ones and vice versa. If I had to choose it would be the new ones fixed as it was late last week.
Photo of Murray Chapman

Murray Chapman, Employee

  • 111 Posts
  • 74 Reply Likes
Yup, there's an encoding bug in the message preview when you create/reply/edit. That'll be fixed ASAP. And it's the same problem that screws up "smart" quotes from MS Word... so that will be fixed at the same time.
Photo of DrakeStraw

DrakeStraw

  • 286 Posts
  • 132 Reply Likes
That would seem to be a priority over the multiple cursor bugs in the åÁâ tool. Programmers should keep in mind that all of those characters work in the subject line as well.
Photo of Paul DiMaria

Paul DiMaria

  • 1 Post
  • 0 Reply Likes
What is the aAa tool? Is that something within IMDb.com that allows the use of special characters?
Photo of DrakeStraw

DrakeStraw

  • 286 Posts
  • 132 Reply Likes
The åÁâ tool appears above the text body area when you compose or edit a board post. It's still buggy because the cursor is all over the place after an insert, but the main problem is that it's output isn't rendered properly once you Preview or Post.
Photo of Murray Chapman

Murray Chapman, Employee

  • 111 Posts
  • 74 Reply Likes
I think you will find that the problem is only with the preview; despite how it looks, it will post fine. The preview issue should be fixed by the end of Monday.
Photo of DrakeStraw

DrakeStraw

  • 286 Posts
  • 132 Reply Likes
Post fine? Not even avoiding the preview! And if I post from the preview it compounds the corruption. Your staff needs to learn the definition of a preview and also avoid tainting the underlying text. You can't add more text processing between preview and post. It then ceases to be a preview.
Photo of Branais

Branais

  • 7 Posts
  • 1 Reply Like
This problem is still occurring. Anything outside the basic ASCII set, such as an em dash or characters with diacritic marks like accents or tildes, seems to display as character codes rather than the character itself.

What's it going to take to fix this?
Photo of DrakeStraw

DrakeStraw

  • 286 Posts
  • 132 Reply Likes
Competent programmers. I'm a retired programmer and I've never seen a worse rollout of any new system.
Photo of Murray Chapman

Murray Chapman, Employee

  • 111 Posts
  • 74 Reply Likes
I've confirmed that on the post confirmation page the encoding is not correct, however when viewed in a thread the encoding is fine.

Here is an example.

Will look at fixing this up ASAP. Thanks for the report.
Photo of Branais

Branais

  • 7 Posts
  • 1 Reply Like
Hi Murray,

Many thanks for the response.

I just tried a reply to your sandbox post. Please see that thread for examples of the issue I was raising.

These characters were created on a PC, running Windows 7, with the Alt-key and the numeric keypad. These should generate direct ASCII characters.

The examples looked fine in the editing window. It's only once they're posted that they no longer show correctly.

I'd be grateful for any feedback. If the site no longer supports standard coding, and requires everything to be entered via the mouse, then I presonally think that's a significant shortcoming of the new format.

regards,
Bran
Photo of Murray Chapman

Murray Chapman, Employee

  • 111 Posts
  • 74 Reply Likes
I'm seeing them post correctly -- the n-tilde and the emdash both render correctly for me in Firefox, Chrome, Internet Explorer, and Safari:



If you're seeing something different, please post a screenshot as well as information on your browser name, vendor, and operating system.

Note: as stated above there is a bug on the post-confirmation page -- the encoding won't look correct there -- but when viewed in the thread the encoding should be fine. I've just found/fixed this bug and hope to roll it out in the next few days.
Photo of Branais

Branais

  • 7 Posts
  • 1 Reply Like
Ahh, Murray, thanks for checking. I think perhaps I simply misunderstood when you wrote:
> I've confirmed that on the post confirmation page the encoding is not correct, however when viewed in a thread the encoding is fine.

Yes, I see the same. When I refresh the page and load the thread anew, the characters show correctly for me as well. Apologies for the concern.

Thanks again,
Bran
Photo of DrakeStraw

DrakeStraw

  • 286 Posts
  • 132 Reply Likes
How did the concept of PREVIEW become lost to the programmers? If it's not WYSIWYG the preview is not valid. I believe I see the problem, separate encoding for previews and live posts. That should never have been allowed to happen.
Photo of DrakeStraw

DrakeStraw

  • 286 Posts
  • 132 Reply Likes
BTW, It's still not working for me. Here's a post that defies correction. It now has compounded corruption of the letter "é":

http://www.imdb.com/title/tt0043859/b...
Photo of Murray Chapman

Murray Chapman, Employee

  • 111 Posts
  • 74 Reply Likes
Just posted a followup to that message with the encoding working fine. If the message has been corrupted then you'll have to manually fix it up.

Note: there is still an encoding bug in the post-confirmation page, but when viewed in the thread the message will be fine. I'm hoping to have that fixed today.
Photo of DrakeStraw

DrakeStraw

  • 286 Posts
  • 132 Reply Likes
Sorry, the corruption is still there at the first level in muzzle's reply. The original has compound corruption due to being previewed twice. Using IE 10. Codepage is Unicode-8. Changing it to Western European compounds the corruption in the reply also.
Photo of DrakeStraw

DrakeStraw

  • 286 Posts
  • 132 Reply Likes
BTW, I have been trying to manually fix it for over two weeks.
Photo of Murray Chapman

Murray Chapman, Employee

  • 111 Posts
  • 74 Reply Likes
Can you please post a screenshot?
Photo of Murray Chapman

Murray Chapman, Employee

  • 111 Posts
  • 74 Reply Likes
The encoding issue on the post-confirmation page has been fixed on the website.
Photo of DrakeStraw

DrakeStraw

  • 286 Posts
  • 132 Reply Likes
It still doesn't work for me. It corrupts once in the Preview and again in the posted message. Can you fix muzzie's post or does it look OK to you?
Photo of Murray Chapman

Murray Chapman, Employee

  • 111 Posts
  • 74 Reply Likes
It all looks fine to me, sorry. Do you have access to another computer/OS? We're trying to find a way to reproduce the issue but are so far unable to.
Photo of DrakeStraw

DrakeStraw

  • 286 Posts
  • 132 Reply Likes
Actually there are three levels of corruption that lead to é, one when you preview é, another when the preview shows you your posted message é and a third when you view the posted message. é
Photo of DrakeStraw

DrakeStraw

  • 286 Posts
  • 132 Reply Likes
I have the same problem in IE and Firefox on two different Windows 7 machines.
Photo of DrakeStraw

DrakeStraw

  • 286 Posts
  • 132 Reply Likes
Photo of DrakeStraw

DrakeStraw

  • 286 Posts
  • 132 Reply Likes
This is an automatic notification from the Internet Movie Database message
boards!

The user 'muzzle' just replied to your post:

'Mrs. Mel Tormé'

in the 'No Highway (1951)' board using a subject of:

'Re: Mrs. Mel Tormé'

You may read their reply here:

http://www.imdb.com/rg/e/bt/title/tt0...
Photo of DrakeStraw

DrakeStraw

  • 286 Posts
  • 132 Reply Likes
So, even a plain-text message is corrupted in Windows Live Mail.
Photo of Branais

Branais

  • 7 Posts
  • 1 Reply Like
Is it corrupted, or merely quoting the existing miscode as a text string?

For instance, "Mrs. Mel Tormé" is what I see in my browser as the title of the thread, and I copied-and-pasted it here. Can we assume Windows Live Mail does the same?
Photo of Murray Chapman

Murray Chapman, Employee

  • 111 Posts
  • 74 Reply Likes
There are a number of issues here.

The original posting was corrupted upon edit due to a bug. Fixing it requires re-editing the message, however DrakeStraw is reporting a bug in IE10 trying to do that. We are attempting to reproduce this bug, but have so far been unsuccessful. We'll continue to try.

The page title is taken from the first post on the thread, so if that's corrupted then so is the page title. Once the original thread's title is fixed then the title should show the same fix.

The software that mails out the notification also seems to have a (different) bug where the subject lines aren't being properly encoded. We'll also look into that one.
Photo of DrakeStraw

DrakeStraw

  • 286 Posts
  • 132 Reply Likes
I should have mentioned that the same corruption shows in IE-10 and Firefox 21 on Windows 7. Codepage is Unicode UTF-8. I even looked at the message source on the notification. The first reply looks OK because they eventually broke new activity in favor of existing posts. Never have they been able to get both right on my computer.
Photo of Murray Chapman

Murray Chapman, Employee

  • 111 Posts
  • 74 Reply Likes
Thanks. The more information we have, the better. BTW, the browser's report of the encoding can be unreliable if fallback behavior is triggered.
Photo of Murray Chapman

Murray Chapman, Employee

  • 111 Posts
  • 74 Reply Likes
We've found and fixed the bug that causes mangled characters in email notifications of posts/PMs. The fix should be live on the site early next week.
Photo of DrakeStraw

DrakeStraw

  • 286 Posts
  • 132 Reply Likes
I found a workaround and fixed my posts in the Mel Tormé thread. In order to avoid the garbage, I have to change the encoding on the posting page from Unicode UTF-8 to Western European (Windows) before making any corrections.

http://www.imdb.com/title/tt0043859/b...
Photo of DrakeStraw

DrakeStraw

  • 286 Posts
  • 132 Reply Likes
Murray,

How can you say you've fixed the notification bug when those garbage characters are legitimate high-end ASCII? The only way to fix it is at the source, so the bad characters are never generated.
Photo of Murray Chapman

Murray Chapman, Employee

  • 111 Posts
  • 74 Reply Likes
It's not quite that simple :-)

ASCII is a simple encoding mechanism where every character is mapped 1:1 to an (8-bit) byte -- one character is always one byte. This is very simple, but only allows for 256 (2^8) different characters. UTF-8 is used on the web, and it's a variable-width encoding mechanism in which characters can be represented by anywhere between 1 and 4 bytes. By design, UTF-8-encoded characters that have ASCII equivalents map to the same exact byte that they do in ASCII -- this makes things very easy. Most other encoding systems (Windows, etc) do the same thing.

The difficulties start when you try to map an "exotic" character -- for example, an "n" with an tilde (ñ). UTF-8 encodes this as two bytes: 0xC3 followed by 0xB1. That's how it's stored in the database on the server, and that's how it sent to the client.

If the browser is expecting UTF-8 then it recognizes the 0xC30xB1sequence as a UTF-8 encoded n-tilde and displays the two bytes as one character -- everyone's happy. If, however, the browser is expecting ISO-8819-1 encoding then it decodes 0xC30xB1 as two characters: 0xC3 (A tilde; Ã) and 0xB1 (plus-minus; ±). UTF-8 often uses 0xC3 as a way of signifying a multi-byte sequence, so the presence of an A-tilde is a dead giveaway of mangled UTF-8 encoding.

The problem we're seeing isn't that the data is incorrectly stored on the server (at least, not yet), or the way the server delivers the data to the browser -- it's the fact that the server and the browser disagree about what the encoding is.

How can that happen? The server instructs the browser what encoding it's using, but the browser sometimes ignores it. Why? Because sometimes the browser thinks it knows better than the server -- it's trying to compensate for buggy servers. If it gets a sequence of bytes which convinces it that it should be in a different encoding than that which the server claims (because that's the only encoding that this sequence of bytes makes sense in), it will ignore the server's instruction and flip to that encoding. This triggering character sequence could be on any part of the page; it doesn't have to come from the boards system. So any other system -- navbar, footer, ads, etc -- outside of changes to the boards code -- has the potential to mangle the content.

Now add in a plethora of operating systems, browsers, and versions -- some of which are buggy -- it's extremely difficult to cover every single possible contingency 100% of the time, given that servers and browsers are attempting to second-guess each other.

There are other complications: the old boards system was designed to use ISO-8859-1 whereas the rest of IMDb has moved to UTF-8 -- which allows us to support many, many more characters. The new boards front-end uses UTF-8. The legacy code in the boards system has been causing us problems for years in maintaining consistency, which you're now seeing as we're attempting to bring it into the current millennium. Far from being a stable system, the boards engine has been causing more and more problems that we're only now starting to see because we're actually changing it.

On top of all of this, the boards engine is written in Perl which has legendarily-bad UTF-8 support -- it's an inconsistent bolt-on hack that can change out from under you when you least expect it. As the boards engine didn't have to worry about UTF-8 encoding, it's riddled with places where the encoding can get mangled. By shifting the boards front-end to UTF-8 we're exposing all the places where encoding wasn't being handled properly in the old boards system. This is very much a case of having to break eggs to make an omelet.

So now, if you edit a post in a browser that decodes the characters as something other than UTF-8, it splits the one-character n-tilde into two characters. It looks like the server has mangled content, when it's the browser that's decoding it "incorrectly". When you post it back to the server, it thinks you intentionally changed the one character into two (it sent it as one, and now it's two), so dutifully records it. And yes, they are legitimate ASCII characters. It just assumes that's what you want.

When it sends it back to you as a preview, the two characters may become four because you're encountering the same bug. Each time you repeat, the data gets mangled further and the original information is lost.

We're not seeing widespread (indeed any other) reports of this encoding problem, but we will continue to investigate, at least for now. Please understand that if we can't reproduce the problem then we can't fix it -- and that at some point other priorities make force us to abandon our research.
Photo of DrakeStraw

DrakeStraw

  • 286 Posts
  • 132 Reply Likes
I should have mentioned that my workaround must avoid the "Preview," which I still contend is not a true preview. I can change the encoding to ISO-8859-1, type the message or correct an existing one and post from the text box.

Is there an advanced browser setting in either IE or Firefox that would enforce the unicode setting of the posting page? I still think there are more people out there with this problem that haven't come forward. The ultimate solution may be what you allow to appear on the posting page.
Photo of DrakeStraw

DrakeStraw

  • 286 Posts
  • 132 Reply Likes
I tested Greek also by setting encoding to ISO-8859-7. It looks fine in the text box but posts the ISO-8859-1 equivalents. Can you post Greek also?

Ουρανός (πλανήτης) = Uranus (Planet)
Photo of DavidAH_Ca

DavidAH_Ca, Champion

  • 3263 Posts
  • 2925 Reply Likes
Is there an advanced browser setting in either IE or Firefox that would enforce the unicode setting of the posting page?
Not sure how well this will work, but in FireFox if you look at the Options, select the Contact tab, then click on the Advanced button beside Default Font, it brings up another menu. This one has the option (near the bottom) to select Fallback Character Encoding. If you choose Unicode (UTF-8), it may help.

No guarantee, but it is worth a try, I think.
Photo of Murray Chapman

Murray Chapman, Employee

  • 111 Posts
  • 74 Reply Likes
I posted a reply to your "greek" test from IE10 on Windows 7 -- without getting any encoding issues. I left the subject line unchanged, which remains mangled from when you first posted.
Photo of DrakeStraw

DrakeStraw

  • 286 Posts
  • 132 Reply Likes
This is a reply from Internet Explorer 10 under Windows 7.

This is a quotation mark: "

This is an apostrophe: '

This is an A acute: Á

This is an o with an umlaut: ö

This is a Unicode smiley: â˜o (may not show up on all systems)

˙ʇxǝʇ uʍop ǝpısdn ÇÉ ̄os ǝʌɐɥ ǝʍ ǝÉ1ǝɥ pu∀

Bonus greek: ÎμÎ ̄Î1⁄2αÎ1 απλά έÎ1⁄2α ÎoÎμÎ ̄Î1⁄4ÎμÎ1⁄2ο χωρΠ̄ς

It shows up like this in Firefox also.
Photo of DrakeStraw

DrakeStraw

  • 286 Posts
  • 132 Reply Likes
Changing the default encoding didn't help. I replied with the Uranus string and got this:

Please Fix These Problems

A server error prevented the message from being sent

Preview:
Re: Greek test: à ̄¿Â1⁄2à ̄¿Â1⁄2à ̄¿Â1⁄2à ̄ ¿Â1⁄2à ̄¿Â1⁄2à ̄¿Â1⁄2à ̄¿Â1⁄2 (à ̄¿Â1⁄2à ̄¿Â1⁄2à ̄¿Â1⁄2à ̄ ¿Â1⁄2à ̄¿Â1⁄2à ̄¿Â1⁄2à ̄¿ Â1⁄2à ̄¿Â1⁄2 à ̄¿Â1⁄2à ̄¿Â1⁄2)
image for user DrakeStraw
by
DrakeStraw
» just now
IMDb member since November 2006
ΟυραÎ1⁄2ός (πλαÎ1⁄2ήτης) = Uranus (Planet)
Photo of DrakeStraw

DrakeStraw

  • 286 Posts
  • 132 Reply Likes
Is there only one server? If it works for you and not for me it would seem that I am reaching a buggy one. This problem never occurs on any other website.
Photo of DrakeStraw

DrakeStraw

  • 286 Posts
  • 132 Reply Likes
The error showed up as too long a subject which I halved and then posted.
Photo of Murray Chapman

Murray Chapman, Employee

  • 111 Posts
  • 74 Reply Likes
There are dozens of servers and the code is rebuilt, redeployed, and tested each day. Servers are randomly assigned per-request; it's extraordinarily unlikely that you're consistently getting a buggy one and I'm not.
Photo of gromit82

gromit82, Champion

  • 7584 Posts
  • 9768 Reply Likes
The image linked below illustrates a problem in using accented letters:

http://postimg.org/image/8jxjbm4pz/

Near the top of the image, in my response, I refer to a movie titled Totò, lascia o raddoppia? where the first word ends with an accented character -- the letter o with a grave accent. Near the bottom of the image, Marhleet refers to the same movie, yet in his response, the accented character is substituted with a diamond with a question mark in it.

What causes this situation, where the same character is displayed both correctly and incorrectly on the same page?
Photo of DrakeStraw

DrakeStraw

  • 286 Posts
  • 132 Reply Likes
I used to get that <?> symbol, but haven't seen it in a while. Did you try the workaround I described earler? Change the encoding to Western European before responding without a preview.
Photo of DrakeStraw

DrakeStraw

  • 286 Posts
  • 132 Reply Likes
gromit82,

I found your post and it looks OK to me.

http://www.imdb.com/board/bd0000042/n...
Photo of gromit82

gromit82, Champion

  • 7584 Posts
  • 9768 Reply Likes
Drake: Just to be clear, when my post looked OK to you, did Marhleet's also look OK at the same time?

I did try switching the encoding on my browser from Unicode (UTF-8) as it was before, to Western (ISO-8859-1). Here's what I got:

http://postimg.org/image/ng1ye2245/

As you can see, when the encoding is changed, the character appears correctly in Marhleet's post, but not in my post -- in my post, the "o with grave accent" is substituted with a "capital A with tilde" and "superscript 2".

Hence, both Marhleet and I posted the character in a way that could be recognized in some encoding -- but the encoding that displays the character correctly for one of our postings doesn't display the character correctly for the other one's posting.
Photo of DrakeStraw

DrakeStraw

  • 286 Posts
  • 132 Reply Likes
I replied to your post using the encoding switch with no preview. Marhleet's post looked OK to me, but this line from a prior post of yours did not:

Also, for clarity, your submission should say that "Lascia o raddoppia?" (1955) is referenced in TotÃ2, lascia o raddoppia? (1956).
Photo of DrakeStraw

DrakeStraw

  • 286 Posts
  • 132 Reply Likes
The "2" appears as superscript there but not here.
Photo of Murray Chapman

Murray Chapman, Employee

  • 111 Posts
  • 74 Reply Likes
gromit82: It depends on what you mean by the "same character". They are both an "o with grave accent", but since one is using UTF-8 encoding and the other one is using ISO-8859-1 encoding, they're not showing up the same on a page that's declared to be UTF-8 encoded. As you then point out, when you force the page into ISO-8859-1 encoding, the one that's UTF-8 encoded looks bad. This is what I'd expect.

The issue is: how did Marhleet manage to post something in ISO-8859-1 encoding? I've done some research and discovered that our mobile boards interface has numerous encoding issues -- it's likely that this user posted from there. I'll be looking into that this week.
Photo of Murray Chapman

Murray Chapman, Employee

  • 111 Posts
  • 74 Reply Likes
DrakeStraw: the first issue we need to figure out is why your browser isn't rendering how we expect it to. I'd like set aside the issues with editing/replying/composing for now until will solve this more fundamental problem.

So, just to confirm, can you please reset your browser back to "default" or "UTF-8" encoding and post a screenshot of what this reply of mine looks like to you. Thx.
Photo of DrakeStraw

DrakeStraw

  • 286 Posts
  • 132 Reply Likes
Same garbage as before. I'm having trouble saving the screenshot.
Photo of DrakeStraw

DrakeStraw

  • 286 Posts
  • 132 Reply Likes
It looks the same in IE 10 as in the following Firefox screenshot. I can't find the encoding in IE 10.
Photo of Murray Chapman

Murray Chapman, Employee

  • 111 Posts
  • 74 Reply Likes
I have found and fixed the bug!

The issue was the encoding of titles with diacritics in "Favorites" list. Fix will hopefully roll out tomorrow.

Thanks for your help tracking this down!
Photo of DrakeStraw

DrakeStraw

  • 286 Posts
  • 132 Reply Likes
Is that why my favorites page has been blank all afternoon? I believe I only have one with a diacritic--"Le jour se lève" and it has never appeared corrupted. Does the bug only affect those with diacritics in their favorites?
Photo of Murray Chapman

Murray Chapman, Employee

  • 111 Posts
  • 74 Reply Likes
When you browser saw that title with ISO-8859-1 encoding, it assumed that the entire page was ISO-8859-1 because the byte sequence that makes up the e-grave only makes sense in ISO-8859-1 -- it's considered an error in UTF-8.

Anyone with a diacritic in their favorites list is affected by this bug. You can wait for the fix, or if you want to try it out now, remove that title from your favorites and the encoding should work perfectly.
Photo of DrakeStraw

DrakeStraw

  • 286 Posts
  • 132 Reply Likes
You nailed it Murray. I was able to delete the title because the dropdown is still working and I counted the boxes down on the blank favorites page. Here's what the Greek looks like now:

This is a reply from Internet Explorer 10 under Windows 7.

This is a quotation mark: "

This is an apostrophe: '

This is an A acute: Á

This is an o with an umlaut: ö

This is a Unicode smiley: ☺ (may not show up on all systems)

̇ʇxǝʇ uʍop ǝpısdn ǝɯos ǝʌɐɥ ǝʍ ǝɹǝɥ pu∀

Bonus greek: είναι απλά ένα κείμενο χωρίς
Re: Greek test: ï¿1⁄2ï¿1⁄2ï¿1⁄2ï� �1⁄2ï¿1⁄2ï¿1⁄2ï¿1⁄2 image for user DrakeStraw DrakeStraw 20 hours ago
Re: Greek test: ï¿1⁄2ï¿1⁄2ï¿1⁄2ï� �1⁄2ï¿1⁄2ï¿1⁄2ï¿1⁄2 image for user DrakeStraw
by DrakeStraw» 20 hours ago (Sat Aug 3 2013 20:12:30) Flag ▼ Permalink
| Edit ▼ Edit

Delete
| Reply
IMDb member since November 2006Ουρανός (πλανήτης) = Uranus (Planet)
==========================================================
Gromit82: I see your posts now as in your screen shot.
Photo of DrakeStraw

DrakeStraw

  • 286 Posts
  • 132 Reply Likes
I noticed today after fixing my problems that there are inconsistencies in thread titles. Those on the boards surface have �'s that aren't present inside the thread.

Wing's board (�You weren't even going to come after me?!?�):

http://www.imdb.com/title/tt0098948/b...

Titanic board(Was Cal really that bad of a fianc�?):

http://www.imdb.com/title/tt0120338/b...
Photo of Murray Chapman

Murray Chapman, Employee

  • 111 Posts
  • 74 Reply Likes
Yup, I noticed the same yesterday when I was investigating the other encoding issue. There's a fix for this in the pipeline that will hopefully roll out today along with the other ones.
Photo of DrakeStraw

DrakeStraw

  • 286 Posts
  • 132 Reply Likes
I couldn't see those �'s before because the encoding bug made them look normal to me!

The next bug I hope you guys work on is the wayward cursor in the åÁâ tool. It's still all over the place and it's action should put the cursor in the same place as if the letter were typed, also replacing selected text. All of those characters are also valid in the subject line, but a cursor there results in a character in the body of the message.
Photo of Murray Chapman

Murray Chapman, Employee

  • 111 Posts
  • 74 Reply Likes
There will be some improvements to cursor handling rolling out soon. It's a tricky fix because some browsers are buggy and/or don't support the mechanisms necessary to achieve this.

The change will also allow åÁâ to be inserted into the title.
Photo of DrakeStraw

DrakeStraw

  • 286 Posts
  • 132 Reply Likes
Please let me know when it's fixed. I rarely use åÁâ due to its quirkiness and prefer my US International keyboard. Unfortunately, even that keyboard sometimes loses to conflicts in menu shortcuts. ø for example loses to Tools when keying Alt+l. I assume there is a registry setting to set the precedence, but I haven't had the conflict often enough to seek it out.
Photo of Murray Chapman

Murray Chapman, Employee

  • 111 Posts
  • 74 Reply Likes
The fixes for the "favorites" issue are now online.
Photo of DrakeStraw

DrakeStraw

  • 286 Posts
  • 132 Reply Likes
Yes, "Le jour se lève" is back and to no effect. Looks like you also fixed the thread title bug. Thanks Murray.
Photo of DrakeStraw

DrakeStraw

  • 286 Posts
  • 132 Reply Likes
I found the thread title bug fix broke something else. I now see "Mrs. Mel Torm�" on my profile page, but it is still "Mrs. Mel Tormé" on the board listing and within the thread itself.
Photo of Murray Chapman

Murray Chapman, Employee

  • 111 Posts
  • 74 Reply Likes
Uggh. This bug we're going to have to live with. The underlying engine is returning the wrong timestamp in that view, so it's impossible to know how to correctly encode the title. This will only affect posts that were originally made before the new boards interface but edited afterwards -- and whose titles contain characters with diacritics. Hopefully that's relatively few, and the problem won't reoccur for new posts.
Photo of DrakeStraw

DrakeStraw

  • 286 Posts
  • 132 Reply Likes
There is no timestamp consistency among boards, favorites and profile. Some times it drives me nuts. Favorites should not report a change unless it's a new post. Many times it reports a change that is nearly impossible to track down.
Photo of Murray Chapman

Murray Chapman, Employee

  • 111 Posts
  • 74 Reply Likes
Yup, it's frustrating. This is deep inside the engine, which we're deliberately not touching as part of the interface changes.
Photo of DrakeStraw

DrakeStraw

  • 286 Posts
  • 132 Reply Likes
BTW, Favorites appear to be sorted randomly. Someone suggested sorting them by timestamp (which is flawed). I suggested user choices in the sort.
Photo of DrakeStraw

DrakeStraw

  • 286 Posts
  • 132 Reply Likes
There was a definite retro encoding error in the "Mrs. Mel Tormé" post in my profile, no doubt caused by my old workaround. An Edit fixed the profile page. BTW here are those timestamp inconsistencies I have observed:

Board - Last new post
Profile - Last edit
Favorites - Last change of any kind, including deleted post.
Photo of DrakeStraw

DrakeStraw

  • 286 Posts
  • 132 Reply Likes
Someone fixed the inconsistency that existed in favorites for a long time. It is now the same as the board.
Photo of DrakeStraw

DrakeStraw

  • 286 Posts
  • 132 Reply Likes
Sorry to report that Mel Tormé is back and I can't edit the garbage out!

http://www.imdb.com/title/tt0043859/b...
Photo of DrakeStraw

DrakeStraw

  • 286 Posts
  • 132 Reply Likes
I tried my old workaround and it worked without producing any �'s. I have a theory of what's going on and it may be related to the fix I described in Favorites. Apparently there's a routine that translates the encoding in old posts that until today went by the Last Edit timestamp and now goes by the original post date. If that's the case it explains perfectly what I saw in this important test thread.

This conversation is no longer open for comments or replies.