Yes -- this is a known issue. Hoping to have it solved in the next couple of days -- the website encoding is basically getting screwed up in a non-obvious way in the scripts we use to parse out the website content (we have to scrap manually). Sorry about the trouble in the meantime -- will post here when fixed.