leifw

The EcmaScript 5 standard (section 15.1.3.4) and the Mozilla Developer Network page on encodeURIComponent both say that the string will be encoded to UTF-8, regardless of the underlying page's character set. That seemed entirely too convenient to believe, so I wrote a page that would let me exercise it. I hit it with modern browsers as well as Firefox 2 and Internet Explorer 5.5 and 6. Amazingly, they handled it correctly, even for pages in obscure character sets like GBK.

 Sleep well tonight in the knowledge that your characters are safe in hands of encodeURIComponent.

Backpacking!

• Stillwater Valley (4 days, 26 miles)
• Granite Peak Attempt (2 days, 20 miles)
• Glacier National Park Transit (6 days, 70 miles)
• Lava Lake Family Trip (2 days, 7 miles)
• Garnet Peak Lookout (2 days, 8 miles)

Total: 16 days, ~120 miles

It was a good summer. (Apologies for the painfully white guy in the pictures.)

I recently gave a tech talk reflecting on some of the highlights of GlueCon. It covered the failure of SOAP, a survey of NoSQL data models, and a brief introduction to node.js.