Bug Fixes and Improvements in the Latest Release
Last night we launched an update to myEarthLink Reader that fixes several issues we've heard about in the weeks since our launch. Bug fixes generally aren't as exciting as new feature announcements (don't worry, we'll have some of those coming soon), but there were some basic parts of the product we wanted to solidify. Here's a list:
- Better UTF-8 Support - If you ever saw question marks or other strange characters in the title or text of an article, this is because we weren't properly handling UTF-8 encoded feeds. We've improved our support for this, but please let us know if you continue to see odd characters.
- OPML import fixes - We received a few cases where people had difficulties importing their sources from other news readers. We've made a number of improvements that should make this process smoother.
- Adding feeds when not signed in - This was fixed in a previous release, but I think it's worth mentioning, especially if you use the Add to myReader browser toolbar button.
- Fine-tuning of Recently Updated - We've been refining how we display what's Recently Updated, and for how long, on a continual basis since our initial launch. We think this release is tuned quite nicely.
Sneak Peek: Related to #4 above, one of our upcoming releases will include a way for you to easily manage the volume of new articles you see when you've been away from myEarthLink Reader for a while. (But everyone's using it every day, right?)
Comments
This is the only issue I have with MyReader.
Great work guys.
Posted by: Russell Limprecht | August 14, 2006 10:22 PM
I'm very glad to see the encoding fixes-- no more ? everywhere in my articles!
I would like to encourage you guys to implement the em dash (it's the longer one, about as long as two of the short dashes, see my first sentence). Engadget loves to use em dashes to offset parenthetical comments, and I have a hard time reading them because it looks like they're compounding adjectives.
Thanks, and keep up the good work.
J
Posted by: John Nolt | September 5, 2006 6:05 PM
Thanks, John. Reader should already support properly escaped em-dashes. I notice that Engadget uses the less typographically correct double dash (--) instead of an em dash (—), both in the feed we get from them and in the display of posts on their site.
Posted by: Gregg Hartling | September 5, 2006 6:18 PM