READ THIS QUICKLY

Acocdrnig to an elgnsih unviesitry sutdy the oredr of letetrs in a wrod dosen't mttaer, the olny thnig thta's iopmrantt is that the frsit and lsat ltteer of eevry word is in the crcreot ptoision. The rset can be jmbueld and one is stlil able to raed the txet wiohtut dclftfuiiy.

Posted by martin on 9/11/03 at 10:29AM


Comments:

Might be true....

I read it quickly, no problems. Read it a second time, paying more attention, and now I feel a little dizzy =). Given we are able to quickly pick up the context, I can read the text without trouble.

Posted by jeff on 9/11/03 at 10:56AM

Messed up, huh?

It's like in movies or whatever, where the main character can read some ancient language without knowing he's doing it. That's NOT ENGLISH, but I understand what it says completely.

I'm going to go lie down now.

Posted by martin on 9/11/03 at 11:06AM

Or like the new version of Time Machine...

where the people millions of years in the future learned English as a plot device. I mean, they learned it as... You know, I forgot the ridiculous reason why they learned English. Regardless, it's like that.

Posted by bryce on 9/11/03 at 4:30PM

...

It's tradition.

I just saw the last half of it on HBO last week, so I know.

And that's way cool. I read it with no problem, either.

Posted by Kim on 9/11/03 at 4:36PM

whoa

.

Posted by matt on 9/11/03 at 5:11PM

Ok,

So why does everyone give me such a hard time on my spelling?

Posted by chris on 9/12/03 at 6:03AM

Obviously,

...you need to at least get the first and last letters correct. ^_^ C'mon, you were asking for it...

Posted by martin on 9/12/03 at 7:28AM

So

how long did it take to write that up? :)

Posted by matt on 9/12/03 at 9:55AM

Not me

I just cut'n'pasted it from another site.

Posted by martin on 9/12/03 at 10:32AM

Actually...

Hmmm... This would actually be a pretty cool code. Native speakers would know it immediately, but computers or non-native speakers would be completely confused. And it's easy for a computer to encode it in the first place, despite the near-impossibility of a computer being able to decode it.

Reminds me of the WWII (WWI?) Navajo code.

Posted by martin on 9/12/03 at 10:34AM

Maybe...

It would actually be interesting to see HOW difficult it would be to decode it with a computer... some words might have many possibilities, but others probably don't have that many possible real words when you are given the first, last, length, and composition of the middle. With a little bit of grammer logic, it might even be possible to narrow down the ambiguity.

Posted by brian on 9/12/03 at 12:27PM

great....

Now that you got me thinking about it, I am tempted to take some code I've already written to solve the newspaper jumbles and adjust it to decode paragraphs like this...
and then make it a web app that you can paste things in like those translation sites...
and provide a way for you to select between possibilities when it isn't sure...
and then get a final version...
and....

... Great... another couple hours down the drain :-)

Posted by brian on 9/12/03 at 12:33PM

Wow, Brian.

What a geek. ;D

Posted by Kim on 9/12/03 at 12:36PM

...

you have no idea.

Posted by brian on 9/12/03 at 12:40PM

Hmmm...

Actually, when I claimed it couldn't be easily read by a computer, I had forgotten that the words were merely jumbled in the middle. I'd guess that choosing one or two letters (based on the length of the word) at random and replacing them with similar sounding variants would still allow a human to read it, but make decoding even tougher.

Posted by martin on 9/12/03 at 1:41PM

interesting...

I wonder if similar looking would make it easier to read, though....

Posted by brian on 9/12/03 at 2:01PM

methinks

you guys have too much time on your hands :)

Posted by matt on 9/12/03 at 11:25PM

seen on slashdot..

" So d__s t__s m__n t__t we d_n't n__d t_e m____e l____s at all?"

Posted by matt on 9/15/03 at 3:28PM


Post comment:

Commenting disabled because this is an archive.

Valid HTML 4.01!

Valid CSS!